From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "Multiple package instances ....". Help me understand this emerge error, please.
Date: Sun, 23 Feb 2014 16:13:49 +0000 [thread overview]
Message-ID: <20140223161349.GE3191@acm.acm> (raw)
In-Reply-To: <530A1227.1080300@gmail.com>
Hello, Alan.
On Sun, Feb 23, 2014 at 05:22:15PM +0200, Alan McKinnon wrote:
> On 23/02/2014 14:13, Alan Mackenzie wrote:
> >> - are you sure that's an emerge failure and not just a convoluted info
> >> > message? Perhaps post the entire emerge output.
> > I tried it again without the -p, and got the same output.
> > I think this is a portage bug. At the very least, it's poor
> > documentation. I've reported the situation to bugs.gentoo.org, bug
> > #502236.
> > Thanks for the help.
> I don't think you have a portage bug as such (other than the sloppy
> bizarre output messages that are going into recent versions). I think we
> have bug in an ebuild, probably a maintainer that doesn't quite know how
> to navigate these new subslots waters,
OK. This is a bit philosophical. The way I see it is even if the main
bug is in the libpng ebuild, portage should have a way of protecting
itself against whatever is in the ebuild. Currently it's wedged.
> One of the other replies suggested to unmerge libpng, emerge it back,
> and continue with emerge world, @preserved-rebuild, revdep-rebuild.
I'll wait a few days on the response to the bug report, just in case
somebody wants me to probe the current state.
> Chances are this will work around the issue and let you update
> everything. There *is* a chance some package(s) won't work with or won't
> compile with libpng[1] and you'll have to unwind things again. If this
> happens that will be valuable info to add the entry at bgo
> [1] This happened to me at least once before, I had to package.mask the
> latest version of the library until the tree sorted itself out. IIRC, it
> was libpng then too!
Surely package management shouldn't be this difficult?
> --
> Alan McKinnon
> alan.mckinnon@gmail.com
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2014-02-23 16:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 21:15 [gentoo-user] "Multiple package instances ....". Help me understand this emerge error, please Alan Mackenzie
2014-02-22 22:06 ` Alan McKinnon
2014-02-22 23:32 ` Mick
2014-02-23 12:15 ` Alan Mackenzie
2014-02-23 17:25 ` Tanstaafl
2014-02-23 17:42 ` Mick
2014-02-23 17:50 ` Tanstaafl
2014-02-23 12:13 ` Alan Mackenzie
2014-02-23 15:22 ` Alan McKinnon
2014-02-23 16:13 ` Alan Mackenzie [this message]
2014-02-23 16:59 ` Alan McKinnon
2014-02-23 22:59 ` Neil Bothwick
2014-02-23 18:45 ` Kerem Gülver
2014-02-23 21:48 ` [gentoo-user] " Jonathan Callen
2014-02-23 0:32 ` [gentoo-user] " wabenbau
2014-02-23 11:54 ` Alan Mackenzie
2014-03-21 13:53 ` Tom Wijsman
2014-03-21 13:50 ` Tom Wijsman
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=20140223161349.GE3191@acm.acm \
--to=acm@muc.de \
--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