On 2014-01-05 12:11, Andreas Metzler wrote: > On 2014-01-05 Niels Thykier <ni...@thykier.net> wrote: >> On 2013-11-30 11:59, Andreas Metzler wrote: >>> Package: release.debian.org >>> Severity: normal >>> User: release.debian....@packages.debian.org >>> Usertags: transition > >>> I would like to finally (now that libimobiledevice builds again) get >>> rid of libtasn1-3. > >>> This should a small painless transition, it will require sourceful uploads >>> of 3 source packages which are up to date in testing. >>> * gnutls26 >>> * gcr >>> * libimobiledevice > >>> All of these three can be built against libtasn1-6. > [...] > >> Sorry for the late responds. > >> Why will it require a sourceful upload of these packages (rather than a >> binNMU) > > Hello, > > It is because we have > libtasn1-3/libtasn1-3-dev/libtasn1-3-dbg/libtasn1-3-bin > libtasn1-6/libtasn1-6-dev/libtasn1-6-dbg/libtasn1-bin (where the > versioned -dev packages conflict) and the three abovementioned > packages have dependencies in the generated binary packages on > libtasn1-3-dev: > > ametzler@argenau:~/TIN/TASN$ grep-dctrl -FDepends libtasn1-3- -sPackage > /chroots/sid/var/lib/apt/lists/ftp.at.debian.org_debian_dists_sid_main_binary-i386_Packages > Package: libgcr-3-dev > Package: libgnutls-dev > Package: libimobiledevice-dev > > Once libgnutls-dev moves to libtasn1-6 it stops being co-installable > with the other two mentioned packages. > > The reason why we have versioned conflicting -dev packages is that I > needed to have both available in sid for an extended period of time. - > libtasn1-6 has minor API breakage and the respective changes to > gnutls26 were not eligible for wheezy freeze. >
Okay, would it be possible to use an unversioned -dev package from now on, so a future transition can be done with binNMUs (where API changes does not cause issues). > What I did not mention before is that shishi will also need a > sourceful upload, as it b-d on libtasn1-3-dev, but that can be done in > a second step, as the binary package is stil installable after > libgnutls-dev has switched to tasn1-6. > Ok. > ametzler@argenau:~/TIN/TASN$ grep-dctrl -FBuild-Depends libtasn1-3- -sPackage > /chroots/sid/var/lib/apt/lists/ftp.at.debian.org_debian_dists_sid_main_source_Sources > Package: gcr > Package: gnome-keyring > Package: gnutls26 > Package: libimobiledevice > Package: shishi > >> and are the maintainers of the reverse dependencies ready to >> upload their packages? > > I am ready for gnutls. The other two packages have outstanding > bug-reports > - libimobiledevice 2013-12-08 <http://bugs.debian.org/731707> > - gcr 2013-07-08 <http://bugs.debian.org/715354> > sadly both without maintainer feedback yet. All three packages are up > to date in testing. > > If you want me to I can obviously make libtasn1-3-dev/libtasn1-3-bin > empty transitional packages built from libtasn1-6 which would limit > the actual transition to binNMUs. > > cu Andreas > That might be worth considering (at least the dev package). Is there any reason why the -bin package is also versioned? Are the libtasn1-X-bin binaries compatible with programs compiled against libtasn1-Y (or will mixing them explode)? ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
