On 17/11/2018 11:54, Emilio Pozuelo Monfort wrote: > Control: tags -1 confirmed > > On 15/11/2018 21:37, Gilles Filippini wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian....@packages.debian.org >> Usertags: transition >> >> Hi Release Team, >> >> I hereby request a transition slot for hdf5 1.10.4 currently in experimental. >> >> Ben file: >> >> title = "hdf5"; >> is_affected = .depends ~ /libhdf5/ | .build-depends ~ /hdf5/; >> is_good = .depends ~ /libhdf5-103|libhdf5-openmpi-103|libhdf5-mpich-103/; >> is_bad = .depends ~ /libhdf5-100|libhdf5-openmpi-100|libhdf5-mpich-100/; >> >> I've checked the build of all the reverse dependencies against this release, >> and from the 110+ of them, only those - which are not in testing - aren't >> binnmu ready: > > Go ahead.
gnudatelanguage's autopkgtests fail with the new hdf5/netcdf, which block netcdf's testing migration. Can you take a look? https://ci.debian.net/packages/g/gnudatalanguage/testing/amd64/ BTW the conflicts between the new libhdf package and the old one is causing lots of trouble for the transition, because the two packages are not co-installable and means all or most of the rdeps need to migrate at the same time. I noticed that upstream bumped the SOVERSION for only one shared lib but not the others, and since you ship them all in the same package, that's forcing the need for the Conflicts. Once this transition is over, can you either split the shared libs in separate packages if upstream is not going to keep them in sync, or ask upstream to keep the SOVERSIONs in sync? The latter would be easier. Cheers, Emilio
