From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is this a genlop bug?
Date: Tue, 02 Oct 2018 09:25:16 +0100 [thread overview]
Message-ID: <2199252.0uFp1bq9u2@peak> (raw)
In-Reply-To: <CAJjrzcUByWEHhLOmRHWqrQTtrsg3k1-Gy=vjQ8C-s=bgfqa0dg@mail.gmail.com>
On Monday, 1 October 2018 13:22:42 BST Arve Barsnes wrote:
> On Mon, 1 Oct 2018 at 14:03, Andrew Udvare <audvare@gmail.com> wrote:
> > > On 2018-10-01, at 05:25, Peter Humphrey <peter@prh.myzen.co.uk> wrote:
> > > This looks like a bug to me.
> >
> > It is not a bug. The manpage says it takes name or category/name. In the
> > former case it has to match anything named rust. There are two packages
> > named exactly 'rust': dev-lang/rust and virtual/rust.
> The '-c' parameter doesn't (need to) take either name or category/name
> so I don't see how this isn't a bug. Getting an ETA average for more
> than one package and comparing it against the currently merging
> package makes no sense.
https://bugs.gentoo.org/667534 submitted.
--
Regards,
Peter.
prev parent reply other threads:[~2018-10-02 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 9:25 [gentoo-user] Is this a genlop bug? Peter Humphrey
2018-10-01 12:02 ` Andrew Udvare
2018-10-01 12:22 ` Arve Barsnes
2018-10-02 8:25 ` Peter Humphrey [this message]
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=2199252.0uFp1bq9u2@peak \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@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