From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Petteri Räty" <betelgeuse@gentoo.org>
Subject: [gentoo-dev] Packages maintained by betelgeuse need a co-maintainer
Date: Sun, 29 Jan 2012 10:57:56 +0100 [thread overview]
Message-ID: <1327831076.23451.4.camel@belkin4> (raw)
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
Due lack of time, betelgeuse's packages need a co-maintainer as talked
with him:
net-misc/goog-sitemapgen
Other packages maintained by him already have a backup herd but, sadly,
looks like that herds usually don't take over that packages (probably
because they think betelgeuse is their primary maintainer):
app-admin/longrun
app-mobilephone/obex-data-server
dev-db/sqlite
dev-java/japitools
dev-java/java-dep-check
dev-libs/antlr-c
dev-vcs/cvs2svn
net-wireless/bluez-firmware
net-wireless/bluez-hcidump
net-wireless/linux-wlan-ng-firmware
net-wireless/linux-wlan-ng-modules
net-wireless/linux-wlan-ng-utils
net-wireless/linux-wlan-ng
sys-auth/pam_usb
Maybe this could be "solved" adding a note to their metadatas to ask bug
wranglers to CC betelgeuse to their bugs and assign to the herds. Also,
probably herds like "mobile" and "pda" need a bit of help :-/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2012-01-29 9:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1327831076.23451.4.camel@belkin4 \
--to=pacho@gentoo.org \
--cc=betelgeuse@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