From: Patrick Lauer <patrick@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] app-admin/mbr.. what to do...
Date: Thu, 16 Jun 2005 10:53:13 +0200 [thread overview]
Message-ID: <1118911993.7951.23.camel@localhost> (raw)
In-Reply-To: <20050617014143.5ef36ceb@localhost>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
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.
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, ...)
> 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.
Patrick
--
Stand still, and let the rest of the universe move
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2005-06-16 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 16:41 [gentoo-dev] app-admin/mbr.. what to do Chris White
2005-06-16 8:53 ` Patrick Lauer [this message]
2005-06-16 9:13 ` Diego 'Flameeyes' Pettenò
2005-06-16 9:28 ` Patrick Lauer
2005-06-16 17:07 ` [gentoo-dev] app-admin/mbr.. what to do... Bag somebody else with it! Drake Wyrm
2005-06-16 14:10 ` [gentoo-dev] app-admin/mbr.. what to do Chris Gianelloni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1118911993.7951.23.camel@localhost \
--to=patrick@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox