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

Re: Release update: kde3.3, upload targets, infrastructure

On Mon, Dec 20, 2004 at 12:55:00PM +0100, Andreas Barth wrote:
> Hello, world.
> After almost three weeks since the last update, the status of the
> release is as follows.  We would have liked to present sarge as a
> Christmas present, but regrettably that didn't work out.  We still hope
> that those of you who celebrate Christmas have a Merry Christmas, and we
> wish you all a Happy New Year.
> Blocker number 1 is still that testing-security is not available. Please
> see the last release update for details of what needs to be done to make
> it available.  Since then, a raw patch for the most urgent changes in
> katie (the archive maintenance software) has been produced.  This patch
> is currently being refined, and some more testing needs to take place.
> Once this change is done, the most urgent blocker for bringing up
> testing-security will be solved.  Testing-proposed-updates will be fully
> usable at about the same time as testing-security.
> The most recent kernel security fixes inadvertently introduced a kernel
> ABI change, with implications for the sarge installer.  The kernel and
> installer teams are still in the process of working through this issue;
> we expect there will be a minor update to d-i RC2 before sarge's release
> to incorporate these kernel security fixes once they are finalized.
> This installer update will also include other small fixes for bugs found
> in RC2, but should not require a complete d-i development cycle as
> previous installer releases did.

This is a problem that effected both 2.4. and 2.6.  After speaking with
the d-i team the kernel-team has decided to keep the ABI change
(actually in the 2.4 case there is a second change for an updated
version of the ldisc/tty patch which caused the change int the first
place) and push the SONAME up to 2. We are looking at uploading updated
packages as soon as some minor (unrelated) problems are ironed out.

This is being tracked as Bug#284356 in the BTS.


Reply to: