On Tue, 22 May 2012 13:29:35 -0400 Andrew Bradford <andrew@bradfordembedded.com> wrote: > On Tue, 10 Apr 2012 16:39:54 +0100 > Neil Williams <codehelp@debian.org> wrote: > > > Someone needs to take a hard look at the buildd.emdebian.org bugs and > > close quite a few of them. Many were filed as part of the work on Crush > > and the underlying systems have changed quite a lot since then. The > > issues described are out of date, the solutions proposed may well be > > unworkable or need revision. > > http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=buildd.emdebian.org > > There's quite a few busybox / Crush / Lenny bugs listed there. Is it > reasonable to just close those without much discussion? Most of these > are from 2008 time frame, so even reproducing them will probably be > difficult or not very worthwhile. Where the bugs relate to packages which are still part of Emdebian Crush, then we need to keep those bugs around. Where the bugs seek changes in packages in Debian then those need review. i.e. if the bug complains that bits of Emdebian Crush don't work, keep those because Crush is still stuck on Lenny. Busybox is also a bit different as the long options will still cause problems with any future version of Crush which seeks to use busybox instead of coreutils. > What's the recommended way of handling this? Is a reply to each of > these really old bugs asking for any reasons to keep it open, waiting a > reasonable time (few weeks?) and if no objection, closing? If the bug was filed by me, there's no need to ping. > I'm rather new to Debian development / bug tracking and don't want > to step on toes, but I'd like to help. Cleaning up really old bugs > seems like a reasonable way for me to start. It just needs someone else to look through the bugs. Some may need to be turned into TODO documents on the debian Wiki (wiki.debian.org) under CategoryEmdebian. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
Attachment:
pgpP4KogyZL_f.pgp
Description: PGP signature