On Thu, 2005-06-16 at 10:53 +0200, Patrick Lauer wrote: > On Fri, 2005-06-17 at 01:41 +0900, Chris White wrote: > > I just saw a bug report flow by for app-admin/mbr and looked for > > maintainers. I found this: > > ChangeLog: 1 manson, 1 woodchip > > from jeeves. Now, I think those people are retired, or I need to get out > > more (or both). So what to do with said package. It looks pretty old and > > this user wants it bumped so... I'd do it but I have no solid test method > > and I really don't like putting out packages without one.
Ehh... the user that filed the bug could test it for you. > I think this problem is not limited to this package. > Maybe someone with some scripting skillz could create a list of all > "orphaned" packages? > (no metadata.xml, no active maintainer, ...) Yes, it would be nice to get a list of these packages, but *not* for removing them. In many cases these packages "work" and have no bugs filed against them, so what is gained by removing them? > > If anyone is interested, the bug number is here: > > http://bugs.gentoo.org/show_bug.cgi?id=96254 > > Otherwise we should do something about the fate of this package. > Either drop it or find a maintainer I guess. > Always a drag to see packages getting dropped, but if noone maintains > them there's not much that can be done. How about leave it alone? I can understand if there is no maintainer and there are a ton of bugs filed against it (or even just one critical one), but for a package where the only "bug" is a version bump request? Just ask the user to test the ebuild, then commit it. -- Chris Gianelloni Release Engineering - Strategic Lead/QA Manager Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part