[pkg-bacula-devel] Bug#923444: bacula: autopkgtest regressed in buster
elbrus at debian.org
Thu Mar 7 19:37:44 GMT 2019
On 03-03-2019 18:31, Carsten Leonhardt wrote:
> Paul Gevers <elbrus at debian.org> writes:
>> On 02-03-2019 15:34, Carsten Leonhardt wrote:
>>> maybe using a trigger can help us:
>> This sounds like an idea we should try to implement in dbconfig-common,
>> to enable other packages to benefit from it as well. If done, this is
>> for after buster release though.
> I already found that we're not the first to run into this problem.
Where did you find that? I.e. which other packages are suffering?
>>> An simple but stupid and unelegant alternative would be to generate meta
>>> packages "bacula-director-local-psql/mysql" that _depend_ on the database
>>> server packages.
>> I rather propose that we accept the current regression of the bacula
>> autopkgtest and we fix the situation properly (in autopkgtest and/or
>> dbconfig-common) after the buster release. Can you live with that?
> Yes, we can live with that as long as the CI-people can, as Sven
> already said.
Who do you mean by CI-people?
> Would you like me to file a wishlist bug against dbconfig-common?
Yes please. Although, the remark of Sven in his last response did
resonate a bit:
> Or are we trying to fix a problem at the whole wrong level?
I am not sure about the answer. If anybody has the time and energy,
maybe they can check with the dpkg maintainers if they are aware of the
situation and if that is intentional. Maybe they consider this issue
something they can (and should) fix.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: OpenPGP digital signature
More information about the pkg-bacula-devel