[EMAIL PROTECTED] wrote: > I'm currently (almost done) updating cgiirc packages, I intend to adopt >or NMU this, closing this and many other bugs.
I would like to remind you of the following statement which I made with the first of these "easy kick-out-of-etch" messages: >These all have RC bugs and are 'leaf' packages in etch. >(As such, they will all get back in easily if the RC bugs are fixed.) I am *not* proposing kicking any of these packages out of unstable (if I were proposing that, the messages would go to debian-qa). If cgiirc is removed from etch right now (as I suggest) -- then ten days after you upload the new versions of the packages, the new versions will enter etch. Just as they would if cgiirc wasn't removed from etch now. In other words, this (new, fixed package coming soon) is *not* a reason to postpone the removal of the old package from etch. -- Nathanael Nerode <[EMAIL PROTECTED]> "(Instead, we front-load the flamewars and grudges in the interest of efficiency.)" --Steve Lanagasek, http://lists.debian.org/debian-devel/2005/09/msg01056.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
