On Sat, Feb 17, 2007 at 01:57:22PM +0100, Christian Hammers wrote: > > > Now some packages like libdbd-mysql-perl crash with strange error > > > messages as they receive communication packages from MySQL that are > > > slightly longer than they expect and thus overwrites unrelated > > > variables :-(
> > This, OTOH, sounds like an incompatible ABI break that should have had a > > *package* name change when it happened, not a shlibs bump. > The ABI was broken and then reverted i.e. fixed shortly after. In such cases > no package name changes are needed, or? In that case, probably not, yes. > > I'm sure it's far too entrenched now to be worth trying to change the > > library name, but we do need info about what packages will need binNMUed. > > Is it just any binaries in the archive, depending on libmysqlclient15off, > > that were uploaded before 5.0.27-1 was available (7 Nov 2006)? > Precisely only the ones built between 5.0.26-1 (Oct 2006) and 5.0.27-1 but > to be sure and if it's automated, better upload everything built before > 7 Nov 2006. Given that the ABI before 5.0.26-1 is supposed to have been the same as the ABI after 5.0.27-1, I'm only going to schedule binNMUs for the packages built in between. That's a total of 7 packages: cacti-cactid_0.8.6i-1 qt4-x11_4.2.1-2 pdns_2.9.20-7 gnade_1.6.1-1 bacula_1.38.11-7 motion_3.2.3-2 sqlxx_2.3.2-5 I notice that libdbd-mysql-perl isn't in this list. Are there still broken binaries in the archive for this package that were built against 5.0.26? If so, then these were uploaded well *after* 5.0.27 was uploaded, and we would potentially need to binNMU /all/ newer packages. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
