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

[László Böszörményi (GCS)]

Hi,

On Sat, Jul 11, 2020 at 5:53 PM <jspricke at debian.org> wrote:
> * Sebastian Ramacher <sramacher at debian.org> [2020-07-11 16:54]:
> So it should work if all migrate at the same time, right?
 It would work if all packages migrate at the same time. It will not
do that automatically however, as auto testing will constantly fail.
It tests with the testing version of ignition-fuel-tools and with the
unstable version of protobuf - being incompatible with each other.
I don't think a break of older protobuf libraries would help either,
but might help against partial upgrades of protobuf related packages.

> >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.
 That would prevent setting up the transition testing chroot, but I
don't know how our tools handle such things. I think preventing the
automatic protobuf transition to testing.

> 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?
 Without too much thinking I've prepared an update which embeds an ABI
version to the library package (see attached diff) that you can depend
on, but I don't think that would help. It will be the same as
depending on the named library.

Regards,
Laszlo/GCS
-------------- next part --------------
A non-text attachment was scrubbed...
Name: protobuf-abi.patch
Type: text/x-patch
Size: 1617 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20200711/67b0bbec/attachment.bin>