Bug#963247: ignition-fuel-tools FTBFS with Protobuf 3.12.3

[jspricke at debian.org]

Hi Sebastian,

* Sebastian Ramacher <sramacher at debian.org> [2020-07-11 16:54]:
>While the rebuilds succeeded, the autopkgtests triggered by protobuf for
>the version of ignition-fuel-tools, ignition-msgs and ignition-transport
>now fail due to the same error.

I guess you refer to:

https://ci.debian.net/data/autopkgtest/testing/amd64/i/ignition-fuel-tools/6226307/log.gz

/usr/bin/ld: warning: libprotobuf.so.22, needed by /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libignition-fuel_tools4.so, may conflict with libprotobuf.so.23

https://ci.debian.net/data/autopkgtest/testing/amd64/i/ignition-msgs/6226308/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/i/ignition-transport/6226309/log.gz

/usr/include/ignition/msgs5/ignition/msgs/actor.pb.h:18:2: error: #error incompatible with your Protocol Buffer headers.

So it should work if all migrate at the same time, right?

>This could be avoided if
>libignition-msgs-dev which contains the protobuf-generated header files
>would have a stricter dependency on libprotobuf-dev. Since these files
>are only compatible with the same protobuf upstream version, it would
>need to depend on the protobuf upstream version it was built with.

There was a similar discussion in #900429 and also #910964 but no real 
solution was proposed. It would be great if the protobuf package would 
provide some tooling to encode the ABI information to the packages at 
compile time.
What would be the way forward here? Open a bug with protobuf?

Cheers Jochen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20200711/a0fa7009/attachment.sig>