public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] app-shells/gentoo-bashcomp needs some portage expert lovin'
Date: Tue, 11 Sep 2012 14:33:51 +0000 (UTC)	[thread overview]
Message-ID: <pan.2012.09.11.14.33.51@cox.net> (raw)

Could a number of folks familiar with both portage AND bash completion
help out the shell-tools herd (no specific maintainer specified in
metadata) with app-shell/gentoo-bashcomp bugs?

It seems to have accumulated quite a number (13) of portage-completion
(and gentoolkit-completion) related bugs, including bug #424777 filed on
July 4th by jer, mentioning that it it breaks with make.conf in /etc/
portage, which is kinda critical right about now. =:^(

https://bugs.gentoo.org/show_bug.cgi?id=424777

And here's the list of all open bugs for it.  As you can see if you look,
all or nearly all of the currently 13 open bugs are portage or gentoolkit
related, and it really looks like the package could use some help from
those who know those tools.

https://bugs.gentoo.org/buglist.cgi?quicksearch=app-shells%2Fgentoo-bashcomp

(I said on the devlist thread I'd report bugs, but this one's been open
for over two months and is directly related to the make.conf move, so it's
a big one, simple fix proposed, but no actual fixes in-tree yet, plus
seeing all those others related to portage and gentoolkit, thus the
request here.)





-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



             reply	other threads:[~2012-09-11 15:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-11 14:33 Duncan [this message]
2012-09-13  0:27 ` [gentoo-portage-dev] Re: app-shells/gentoo-bashcomp needs some portage expert lovin' Ryan Hill

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=pan.2012.09.11.14.33.51@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-portage-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