Steve Langasek <vorlon@debian.org> writes: > On Fri, Mar 02, 2007 at 08:39:47AM +0100, Josselin Mouette wrote: >> Le mercredi 28 février 2007 à 19:21 +0100, Josselin Mouette a écrit : >>> As 2.14.3-3 is now in testing, I've uploaded 2.14.3-4 to unstable with >>> the same changes as 2.16-3-2. It is currently sitting in NEW. >> It is now out of NEW - kudos to the ftpmaster who fast-tracked it - and >> built on all architectures. > >> Could you please schedule binNMUs of nautilus-cd-burner, nautilus, >> music-applet, mail-notification, link-monitor-applet and gnome-mount? > Scheduled, along with binNMUs for nautilus-python. All of these bin-NMUs were done now, so eel2 should be ready to transition to testing. There is a problem though: mail-notification | 3.0.dfsg.1-10 | testing | source, alpha, amd64, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc mail-notification | 4.0~rc2.dfsg.1-4 | unstable | source mail-notification | 4.0~rc2.dfsg.1-4+b1 | unstable | alpha, amd64, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc The mail-notification bin-NMU was done on the base of a source version not targetted at testing. So I guess the right thing now is to force in the new eel2 (together with nautilus-cd-burner, nautilus, music-applet, link-monitor-applet, gnome-mount and nautilus-python) and then schedule bin-NMUs for the then broken mail-notification in testing. Steve? Marc -- BOFH #415: Maintence window broken
Attachment:
pgpOrgmV4ZtXI.pgp
Description: PGP signature