Re: RC bugs in lenny, sorted by maintainer
> > Wouldn't it make sense to only send [TU] bugs as these are the bugs we have to
> > fix for the release? [T] normaly means fix just waiting for migration, isn't
> > it?
> No: in some cases, the maintainer forgot to send an unblock request to
> -release@, or the fix was inappropriate, and the bug will have to be
> fixed through a testing-proposed-updates upload.
Okay, makes sense.
> The release team isn't proactively tracking those AFAIK, it's still the
> maintainer's responsibility to take care of this.
> > > Michael Meskes <firstname.lastname@example.org>
> > > [TU] watchdog #503080 watchdog.postinst: line 18: /sbin/MAKEDEV: No s
> > > [T] (U) acpid #487815 acpid: dies on any given Sunday
> > > [T] (U) acpid #491058 acpid exits
> > > [T] (U) acpid #495686 acpid not starting after (re)boot
> > Using my bugs as an example. All four of them are fixed in unstable, so neither
> > needs work. Watchdog was reported and uploaded yesterday, so no surprise it's
> > still listed as [TU].
> ... and watchdog also needs an unblock.
I know. Usually I wait some days to see whether other bugs come up from the new
upload before sending out that email.
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: email@example.com
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!