On Thursday 08 February 2007 00:59:49 Daevid Vincent wrote:
> > 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
>
> Thanks, but I don't have a bug to solve here. Just the feature request.

It would make it easier to explain why bug #157361 is a dupe of #1343 though. 
Assuming that still isn't clear to you?

> > 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.
>
> Yes, but then I have to manually, one at a time search eix and compare to
> the output of 'emerge world'. I use eix. That's actually why I suspect that
> the feature could be implemented fairly easily. Portage has all the info it
> needs.

You do know that eix is not related to portage in any way? Anyway, can you 
explain to me how this feature would help you at all. I really don't 
understand the use case for it.

> > I think reopening the same bug 3 times is a terrible idea. It
> > clearly doesn't help anyone.
>
> Nor does just blindly closing it without really comprehending what the
> request is for.

Jakub is handling a lot of bugs so obviously he does make mistakes 
occasionally. I don't think he makes that many of them but arguably he should 
have reassigned #165709 to dev-portage@ and let them handle it. Do note that 
Jakub is a bug-wrangler not a maintainer.

> > 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), [...].
[SNIP]
> Actually, I'll just concede defeat.  :(

That's your decision then.

-- 
Bo Andresen

Attachment: pgpTjSEr9HKpr.pgp
Description: PGP signature

Reply via email to