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

Re: libnewt transition from 0.51 to 0.52

On Sun, Mar 19, 2006 at 08:01:54PM +0000, Alastair McKinstry wrote:

> You are receiving this mail because you maintain a package that depends 
> on libnewt0.51.

> This has now moved to 0.52 in upstream, and the versioned symbols patch 
> from Debian was applied
> with the 0.52 tag, requiring that all packages depending on libnewt0.51 
> be rebuilt
> to depend on libnewt0.52 instead.

> It would be appreciated if you could rebuild your package accordingly.

> Maintainers with packages depending on libnewt0.51, according to whodepends:

> John Lines <john@paladin.demon.co.uk> (plptools)
> Alastair McKinstry <mckinstry@debian.org> (libnewt-dev libnewt0.52 
> newt-tcl python-newt whiptail)
> Debian Install System Team <debian-boot@lists.debian.org> (cdebconf)
> Andree Leidenfrost <aleidenf@bigpond.net.au> (mindi-partimagehack mondo)
> Michael Biebl <biebl@teco.edu> (partimage partimage-server)
> Chris Lawrence <lawrencc@debian.org> (lokkit)
> Noèl Köthe <noel@debian.org> (kudzu)
> Marek Habersack <grendel@debian.org> (pike7.2-pexts-newt 
> pike7.4-pexts-newt pike7.6-pexts-newt)
> Debian QA Group <packages@qa.debian.org> (libnewt-perl)
> Debian VoIP Team <pkg-voip-maintainers@lists.alioth.debian.org> 
> (asterisk-bristuff asterisk-classic zaptel)

With the exception of gnome-lokkit (previous binNMU using the old ".0.1"
version numbering scheme), all of these packages should be binNMUable for
the transition.  I've just scheduled binNMUs across all architectures on the
autobuilders for them, so no maintainer action should be required except for
Chris. :)

Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply to: