From: "Molle Bestefich" <molle.bestefich@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Portage: missing pieces
Date: Wed, 21 Jun 2006 13:29:21 +0200 [thread overview]
Message-ID: <62b0912f0606210429t3dbd40dajc38cca3e446eac68@mail.gmail.com> (raw)
I think a piece might be missing from Portage.
I'll depict my workflow as an example.
I'm preparing to upgrade:
# emerge --sync
# emerge -Dp world
[blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libXinerama-1.0.1)
[blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libXi-1.0.1)
[blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libXrandr-1.1.1)
[blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/randrproto-1.1.2)
[blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-misc/makedepend-1.0.0)
[blocks B ] <=x11-base/xorg-x11-6.9 (is blocking media-libs/mesa-6.5-r3)
[blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libdrm-2.0.1)
[blocks B ] <=x11-base/xorg-x11-6.9 (is blocking
x11-proto/xf86vidmodeproto-2.2.2)
[blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/glproto-1.4.7)
[blocks B ] <=x11-base/xorg-x11-6.9 (is blocking
x11-proto/xf86driproto-2.0.3)
... etc, lots of blockers ...
Ok, let's try and find why it wants to downgrade to xorg-x11-6.9:
# equery d xorg-x11-6.9
[ Searching for packages depending on xorg-x11-6.9... ]
<none found>
#
Ok, no reason, apparently. Maybe it's already merged then?
# emerge -C xorg-x11-6.9
--- Couldn't find 'xorg-x11-6.9' to unmerge.
Nope. Now I'm getting uncertain. Don't I have xorg-x11 at all?
# emerge -C xorg-x11
x11-base/xorg-x11
selected: 7.0-r1
protected: none
omitted: none
>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.
>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in: 5 4 3
<CTRL-C>
Exiting on signal 2
Whoops. Yep, it's there.
Ok, so status is that I have xorg-x11-7.0, I don't have 6.9, no
packages actually wants xorg-x11-6.9, but whenever I use "emerge -D
world", Portage sees it as a blocker anyway.
Is there a piece missing in this puzzle, in particular the one that
will tell me why on earth Portage thinks version 6.9 is a blocker?
Or is the piece in place but I'm not looking hard enough?
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2006-06-21 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 11:29 Molle Bestefich [this message]
2006-06-21 12:09 ` [gentoo-user] Portage: missing pieces Shaochun Wang
2006-06-21 13:07 ` Daniel da Veiga
2006-07-06 8:33 ` [gentoo-user] " Molle Bestefich
2006-07-06 8:44 ` Donnie Berkholz
2006-07-06 16:54 ` Richard Fish
2006-07-12 17:02 ` Devon Miller
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=62b0912f0606210429t3dbd40dajc38cca3e446eac68@mail.gmail.com \
--to=molle.bestefich@gmail.com \
--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