[pkg-bacula-devel] Bug#923444: bacula: autopkgtest regressed in buster
sven at svenhartge.de
Thu Mar 7 19:55:34 GMT 2019
On 07.03.19 20:37, Paul Gevers wrote:
> 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?
Bareos has run into this problem before, btw:
If I had time right now, I'd use codesearch to find packages listing
postgresql in their debian/tests/control and then check if they
currently fail in the same manner as Bacula and Bareos.
>>>> 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?
The people running ci.debian.net and filing bugs on behalf of failing
tests, for example: you :)
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the pkg-bacula-devel