[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#630201: marked as done (transition: liblzma 5)

Your message dated Tue, 14 Feb 2012 22:49:41 +0000
with message-id <1329259781.939.31.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#630201: transition: liblzma 5
has caused the Debian Bug report #630201,
regarding transition: liblzma 5
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
630201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630201
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: transition

Hi,

I would like to upload liblzma5 to unstable, so liblzma in wheezy can
match the upstream ABI.

Relative to what's currently in sid, this involves a soname bump
(2 → 5), introduction of versioned symbols, and some changes to the
padding at the end of structs.  liblzma never looks at this padding
so even by simulating the worst case (liblzma2 and liblzma5 being
indirect dependencies of a single binary through different paths,
resulting in the two versions sharing a process image) I haven't been
able to make it cause any trouble for partial upgrades.  And I'm not
aware of any packages that would trigger that worst case.

You can find a liblzma5 package to test with at

 git://git.debian.org/collab-maint/xz.git experimental
 http://mentors.debian.org/debian/pool/main/x/xz-utils/xz-utils_5.1.1alpha+20110528-1~exp1.dsc

The packaging takes the latest upstream version and reverts changes
that introduced new ABI since the last stable upstream release.  It is
targetted at experimental and might be uploaded there soon.

apt-cache points me to 14 binary reverse-dependencies counting each
source package once[1], aside from xz-utils itself.  From a transition
coordination perspective, probably shogun, R, and KDE are the most
notable ones.

This is not urgent.  I just would be happy to get it done so it
doesn't have to happen later.  Thoughts of all kinds welcome, of
course.

Regards,
Jonathan

[1]
* shogun:
 shogun-r
 shogun-python-modular
 shogun-python
 shogun-octave-modular
 shogun-elwms
 shogun-cmdline
 libshogun9
 libshogunui6

* python-lzma:
 python-lzma-dbg
 python-lzma

* libarchive:
 libarchive1
 bsdtar
 bsdcpio

* miscellaneous:
 r-base-core
 libkdecore5
 libyelp0
 squashfs-tools
 mupen64plus
 gtkwave
 fusecompress
 fsarchiver
 libdw1 (DWARF parser for elfutils)
 apt-cacher-ng
 librpmio2

--- End Message ---
--- Begin Message --- 
On Wed, 2011-12-07 at 21:12 +0100, Julien Cristau wrote:
> On Tue, Nov  1, 2011 at 13:47:24 +0100, Mehdi Dogguy wrote:
> 
> > FWIW, the current list of reverse dependencies are:
> > 
> > # Broken Depends:
> > elfutils: libdw1 [kfreebsd-amd64 kfreebsd-i386]
> [...]
> 
> Now it's just this one, so we're pretty much there.

That got fixed, and liblzma2 now only exists in stable.  I think it's
safe to say this is finished.

Regards,

Adam

--- End Message ---
Reply to: