On Fri, Feb 14, 2014 at 08:09:56AM +0300, Cyril Brulebois wrote: > Phillip Susi <ps...@ubuntu.com> (2014-02-13): > > In preparation for the parted3 transition, this patch removes support > > for filesystem creation and checking from parted_server. The dependency > > and linker flag changes can be left out for now and it should still > > build against parted2. They can be added after parted3 has been > > uploaded to actually make the switch.
This basically looks fine, thanks, but I think I'll hold off on applying it until we've started the parted transition. I'll file a separate bug against release.d.o for that. > > --- partman-base-172/debian/control 2013-07-13 03:07:32.000000000 -0400 > > +++ partman-base-173/debian/control 2014-02-12 11:57:06.000000000 -0500 > … > > -Build-Depends: debhelper (>= 9), dh-di (>= 2), po-debconf (>= 0.5.0), > > libparted0-dev (>= 2.2) > > +Build-Depends: debhelper (>= 9), dh-di (>= 2), po-debconf (>= 0.5.0), > > libparted2-dev > > The parted3 transition is about transitioning from libparted0 to > libparted2? Anyway, why is the -dev package versioned at all? Unless > you keep several source packages in the archive for a while, there's > no use for having a versioned -dev package. Yeah, this is (to me) a historical mistake. I'm staging the parted 3.1 merge in http://anonscm.debian.org/gitweb/?p=parted/debian/parted.git;a=shortlog;h=refs/heads/v3, and I've removed the pointless -dev versioning there, so it will just be libparted-dev. On Fri, 14 Feb 2014 at 09:21:45AM -0500, Phillip Susi wrote: > I believe the reason is that for a long time, upstream did not manage > their soname versioning correctly, leaving it at zero despite breaking > ABI, and finally with parted 3.0, jumped to 2 since they removed the > filesystem apis. So debian packaged the library as -0debian1. Close but not quite; "libparted.so.0" appeared in parted 2.2 when upstream switched to libtool's versioning system, from a previous scheme along the lines of "libparted-2.1.so.0". Unfortunately there'd briefly been a SONAME version of 0 back in 2000, and as a result there were some unversioned "Conflicts: libparted0" lying around. I applied << versions to those once I noticed the problem (can probably remove them entirely at some point), but lacking a time machine I couldn't call the package libparted0 without breaking upgrades, so I renamed to libparted0debian1 as an ugly workaround. That should no longer be an issue now - I fixed the unversioned Conflicts four years ago - so the parted 3.1 packaging will just use libparted2 rather than libparted2debian1. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140711125510.ga6...@riva.ucam.org
