On Sun, Dec 03, 2006 at 02:45:37PM +0000, Adam D. Barratt wrote: > On Sat, 2006-12-02 at 22:45 -0800, Russ Allbery wrote: > > Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
> > > It would be better to have a halfway modern lilypond on 32-bit archs and > > > nothing at all on 64-bit archs, than to have a medieval lilypond of > > > them. > > So, if that's the case, wouldn't the next step be to file a bug with > > ftpmaster requesting the removal of the 64-bit builds of the old version > > of lilypond from testing, after which the new lilypond would propagate to > > testing automatically since it would no longer be breaking those > > architectures? > s/file a bug with ftpmaster/mail debian-release/ :) No, absolutely not. The release team does not remove individual binary packages, this is the domain of the ftp team. Nor is removing binaries from testing the issue -- the issue is that the old binaries would need to be removed from *unstable* in order to allow the new version of lilypond to propogate *from* unstable into testing. -- 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]
