From: Cyprien Nicolas <gentoo@fulax.fr>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] RFC: Graveyard project
Date: Fri, 15 Feb 2013 13:48:34 +0100 [thread overview]
Message-ID: <20130215124834.GC23998@kubera> (raw)
In-Reply-To: <CAG2jQ8h5H3CDjOQh-LP7yONbH2ACZJBSqLx--eeBokc_ausCUw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
On Fri, Feb 15, 2013 at 09:39:34AM +0000, Markos Chandras wrote:
> On 15 February 2013 00:19, Diego Elio Pettenò <flameeyes@flameeyes.eu> wrote:
> > The problem is when you have to triple-check that the user hasn't
> > enabled some random fucked up overlay and you have to guess whether that
> > might be the cause of the problem. Yes it happens, not so rarely.
> >
>
> That's not a good argument. You can't stop people from using whatever
> external sources they want. But you can easily
> spot what they use from a simple eix -e <broken-package> or emerge
> --info and close the bug as INVALID in the blink of an eye
Not really, this works when the bug is opened against a given package
from an overlay. Diego's raised issue is about some *DEPEND installed
from an overlay, but the failing package is from the tree.
emerge --info will not report from which overlays the *DEPEND has been
installed. I don't know of a simple command to list installed reverse
dependencies; qdepends -Q does not show repo_name info.
--
Cyprien Nicolas (Fulax)
Gentoo Lisp project contrib
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-02-15 12:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB9SyzSBQcgL6rxDHcoo-O+3=K_b1iG15i2P3esj=WPjOLxivQ@mail.gmail.com>
2013-02-14 21:55 ` [gentoo-dev] Re: [gentoo-dev-announce] RFC: Graveyard project Rick "Zero_Chaos" Farina
2013-02-14 22:17 ` Ian Stakenvicius
2013-02-14 22:21 ` Jeff Horelick
2013-02-14 22:47 ` Florian Philipp
2013-02-15 0:06 ` Diego Elio Pettenò
2013-02-15 0:15 ` Rich Freeman
2013-02-15 0:19 ` Diego Elio Pettenò
2013-02-15 1:18 ` Rich Freeman
2013-02-15 1:39 ` Diego Elio Pettenò
2013-02-15 1:56 ` Peter Stuge
2013-02-15 2:20 ` Diego Elio Pettenò
2013-02-15 2:44 ` Peter Stuge
2013-02-15 8:15 ` Florian Philipp
2013-02-15 9:39 ` Markos Chandras
2013-02-15 12:48 ` Cyprien Nicolas [this message]
2013-02-15 13:10 ` Cyprien Nicolas
2013-02-15 13:48 ` Ian Stakenvicius
2013-02-15 14:33 ` Ben Kohler
2013-02-15 9:44 ` Alec Warner
2013-02-15 14:34 ` Diego Elio Pettenò
2013-02-16 4:53 ` Ben de Groot
2013-02-15 10:33 ` Alexander Berntsen
2013-02-15 12:58 ` Diego Elio Pettenò
2013-02-15 13:08 ` Alexander Berntsen
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=20130215124834.GC23998@kubera \
--to=gentoo@fulax.fr \
--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