[pkg-bacula-devel] Summary for 9.4.0

[Sven Hartge]

On 22.12.18 15:04, Carsten Leonhardt wrote:
> Sven Hartge <sven at svenhartge.de> writes:
> 
>> There is nothing we can do here, only maybe file "Serious" bug on
>> src:mariadb10.3 to provide the header packages.
> 
> Looks like this has already been filed as bug #917075.

The situation is not as easy as it looks.

I was stumped by the fact my local pbuilder could not compile the bacula
packages whereas the build runs fine in the GitLab CI runners.

The difference here is my "special" build-dep resolver I implemented to
get stretch-backports working, which uses aptitude instead of apt.

See, the normal direct dependency chain is this:

default-libmysqlclient-dev
-> libmariadbclient-dev-compat
 -> libmariadbclient-dev
  -> libmariadbclient18 (= 1:10.1.37-3)
   *kaboom*

But!:

Package: libmariadb-dev-compat
Provides: libmariadb-client-lgpl-dev-compat,
libmariadbclient-dev-compat, libmysqlclient-dev
Depends: libmariadb-dev (= 1:10.3.11-1)

If the dependency resolver is smart enough, like the one from aptitude
is, then it will pick up libmariadb-dev-compat and now everything looks
like this:

default-libmysqlclient-dev
-> libmariadb-dev-compat
 -> libmariadb-dev (= 1:10.3.11-1)
  -> libmariadb3 (= 1:10.3.11-1)

And everything works. And this is exactly what happens in our special
build environment, but not in reprotest, which uses the "apt-get
build-dep" variant of installing things.

Grüße,
Sven

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-bacula-devel/attachments/20181222/0f8822e1/attachment-0001.sig>