On 2014-01-05 13:48, Andreas Metzler wrote: >[...] > Hello, > Hi,
Sorry, I seem to have lost track of this. > I would rather not introduce new binary packages now (going through > NEW) but can keep it in mind for the next soname bump, not that I > expect one soonish. > Okay. > [...] >>> 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. > >> That might be worth considering (at least the dev package). > > See attached proposed patch. > Looks reasonable at first glance; it will hijack the existing binaries from the libtasn1-3 source. >> 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)? > > The new -bin package is already unversioned (libtasn1-bin instead of > libtasn1-6-bin). > > cu Andreas > Great; assuming I haven't messed something, I think we are ready to start. ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
