On Wednesday 07 February 2007 23:19:53 Daevid Vincent wrote:
> Honestly, I really don't see how they're even remotely related. So either
> I'm just dense, or the maintainer is not understanding my request... It's
> extremely frustrating.
>
> [Bug 165709] When viewing "emerge -avu world" show which packages are
> stable (or ~x86)
>
> http://bugs.gentoo.org/show_bug.cgi?id=165709 is my original one
>
> http://bugs.gentoo.org/show_bug.cgi?id=157361 is what they claim is a
> duplicate
> And
> http://bugs.gentoo.org/show_bug.cgi?id=1343

Bug #157361 clearly is a dupe of bug #1343. There's no question about that. If 
you upgrade to Portage 2.1.2 (which will go stable soon) you'll find that it 
will detect that two versions of mozilla-firefox within the same slot 
(firefox only has one slot) are being pulled in and hence it will die up 
front while telling you about the problem. It still won't be able to solve it 
without your help though.

So... it will be a lot easier for me to tell you what your options are wrt. 
working around this bug if you post the output of:

# emerge -Dup world --tree --verbose

Wrt. bug #165709 I'd probably have pointed you towards app-portage/eix and 
resolved it as WONTFIX or even INVALID as I really don't see the point in 
that feature request. There are a lot of tools including eix that are a lot 
more suitable for queries about what is stable and what isn't. I do 
understand jakubs reasoning for thinking it's triggered by bug #157361 and 
hence marking it a dupe of that though.

I think reopening the same bug 3 times is a terrible idea. It clearly doesn't 
help anyone. The most obvious options after the first time are to CC the 
[EMAIL PROTECTED] alias on the bug to make the portage devs aware of it 
(while commenting about why you do that), or to post a mail here, on the 
gentoo-dev-portage@ mailing list (this is a feature request for portage after 
all) or log onto irc and talk to the portage devs in #gentoo-portage on 
freenode.

-- 
Bo Andresen

Attachment: pgp0G8aJCzB9v.pgp
Description: PGP signature

Reply via email to