Hi Pirate, On Sat, Oct 20, 2018 at 10:39 AM Pirate Praveen <prav...@onenetbeyond.org> wrote: > On Mon, 15 Oct 2018 16:26:23 +0300 Adrian Bunk <b...@debian.org> wrote: > > When it has been observed that ending up with both libprotobuf10 and > > libprotobuf17 in a binary will not work, then this should be expressed > > through the package dependencies. ... of the binaries that need to be compiled with the same ProtoBuf version.
> Are you planning to upload this fix? Testing migration is currently > blocked by this rc bug and there is a delay caused by autopkgtest failure. Let's break it to parts. 1) Can libprotobuf10 and libprotobuf17 installed together and independent packages working correctly with these libraries? Yes, these are possible. I don't see the need to break the old libprotobuf10 package. 2) Packages that depend on each other, need to be compiled with the same ProtoBuf version. This should be expressed in those package dependencies. 3) Self-tests need fixing, this is clear. > > That would avoid a couple of potential problems in situations like > > stretch->buster upgrades or for testing users. Breaking libprotobuf10 would cause more problems. All ProtoBuf related packages would need to migrate once and together. Cause problem with any local compiled program for libprotobuf10. > > It should also fix the autopkgtest failures that are currently > > preventing protobuf from entering testing this month. > > I added Breaks and ran autopkgtests again, but it still failed. Indeed, breaks in ProtoBuf is not the solution. This needs investigating, maybe updating the tests. > I think the examples are not updated for new api. New jar file does not > have this class. [...] > protobuf 3.6.1 autopkgtest is failing with this error, can you help > fixing this? I'll also check these, but help might be needed. My Java knowledge is very rusty. Regards, Laszlo/GCS
