On Sat, Mar 31, 2007 at 12:40:48AM +0200, Samuel Thibault wrote: > Samuel Thibault, le Tue 27 Mar 2007 20:01:56 +0200, a écrit : > > Is there a reason for delaying an upload fixing brltty #411426, #414068 > > and #411671 bugs?
> Actually, only 411426 really needs to be fixed for Etch. Do you have > time for doing the upload, or could it be NMUed? Um, I don't see that this is a bug that needs to be fixed for etch, and I'm generally not in favor of significantly reorganizing binary packages at the last minute before release. Could you please elaborate why you've marked this as 'serious'? It's normally not RC for a package to ship in a stable release with the kind of bug described here, it just becomes RC to fail to deal with it correctly in the next stable release. (Hmm, I see that currently, policy 8.2 says "must not" about including support programs in a shared lib package; I have no idea when that was changed, but anyway it's not something being treated as RC for etch.) Thanks, -- 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/
