Upgraded to xorg version 7. Took me a couple of days of bending Portage to get it to do it. Afterwards I did an "emerge -D world". Here I am today, a couple weeks later. Now when I do "emerge -D world", I get this: [blocks B ] x11-libs/libXft (is blocking x11-base/xorg-x11-6.8.2-r6) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-drivers/xf86-video-ati-6.5.7.3) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/fontsproto-2.0.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libXxf86misc-1.0.0-r1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/xf86miscproto-0.9.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/liblbxutil-1.0.0) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libxkbfile-1.0.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-apps/xkbcomp-1.0.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/damageproto-1.0.3) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/resourceproto-1.0.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libXres-1.0.0-r1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-base/xorg-server-1.0.2-r3) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/trapproto-3.4.3) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libXtst-1.0.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/recordproto-1.13.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/xineramaproto-1.1.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-apps/rgb-1.0.0) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/dmxproto-2.2.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-apps/iceauth-1.0.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking media-fonts/font-adobe-75dpi-1.0.0) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-apps/mkfontscale-1.0.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libfontenc-1.0.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking media-fonts/encodings-1.0.0) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking media-fonts/font-util-1.0.0) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-apps/bdftopcf-1.0.0) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libXfont-1.1.0-r1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/fontcacheproto-0.1.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-apps/mkfontdir-1.0.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking media-fonts/font-alias-1.0.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/xf86rushproto-1.1.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking media-fonts/font-misc-misc-1.0.0) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libxkbui-1.0.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking media-fonts/font-cursor-misc-1.0.0) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/evieext-1.0.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libdmx-1.0.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-apps/xauth-1.0.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-apps/xinit-1.0.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-apps/xclock-1.0.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-apps/xrdb-1.0.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-wm/twm-1.0.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/compositeproto-0.3.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/scrnsaverproto-1.1.0) [ebuild U ] sys-libs/readline-5.1_p2 [5.0-r2] [ebuild U ] sys-devel/binutils-config-1.8-r7 [1.8-r6] <... snip ...> It took another two days to figure out how to bang Portage on the head enough that it didn't try to downgrade X. The solution was to add this line to /etc/portage/package.mask: <x11-base/xorg-x11-7.0 Effectively masking out xorg-x11-6.9 that Portage wants to downgrade to. Now, this really f.... up the user experience, having to tell it this the hard way. Really obscure if you ask me. Why would it even want to start downgrading xorg, now that I specifically ask it to keep up to a certain version in /etc/portage/package.keywords: =x11-base/xorg-x11-7.0-r1 That's just beyond me - that has GOT to be a bug. Anyway, now when I hack package.mask and then do "emerge -D world", I get this: These are the packages that would be merged, in order: Calculating world dependencies | !!! All ebuilds that could satisfy "<=x11-base/xorg-x11-6.99" have been masked. !!! One of the following masked packages is required to complete your request: - x11-base/xorg-x11-6.9.0 (masked by: package.mask, package.mask) # Donnie Berkholz <spyderous@gentoo.org> # Keeping masked so ~arch/arch users move from 6.8.2 to 7.0 - x11-base/xorg-x11-6.8.2-r4 (masked by: package.mask) - x11-base/xorg-x11-6.8.2-r6 (masked by: package.mask) For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. (dependency required by "virtual/x11-6.8" [ebuild]) !!! Problem resolving dependencies for media-gfx/gimp !!! Depgraph creation failed. First it was x11-misc/xscreensaver, which I then uninstalled. Then net-wireless/gnome-bluetooth, which I also uninstalled. But I need Gimp. So, I try to find out why Gimp wants virtual/x11-6.8, which I find after some researching that it apparently doesn't. "equery g gimp | grep x11-base/xorg-x11" shows: x11-base/xorg-server-1.0.2-r3 [ X ] x11-proto/glproto-1.4.6 [ !<=x11-base/xorg-x11-6.9 ] app-crypt/gnupg-1.4.2.1 [ !<x11-base/xorg-x11-6.7.0-r2 crypt ... ] www-client/mozilla-launcher-1.45 [ !<x11-base/xorg-x11-6.7.0-r2 ... ] I assume that the last three are ok and the first is the problem. So I run "equery g gimp | grep -B 1000 x11-base/xorg-server" and get (trimmed a lot): * dependency graph for media-gfx/gimp-2.2.8-r1 `-- media-gfx/gimp-2.2.8-r1 `-- gnome-extra/gtkhtml-2.6.3 [ gtkhtml ] `-- gnome-base/gail-1.8.8 [ accessibility ] `-- dev-libs/atk-1.10.3 `-- gnome-base/libgnomecanvas-2.12.0 `-- gnome-base/libglade-2.5.1 `-- x11-base/xorg-server-1.0.2-r3 [ X ] And somehow (I assume) x11-base/xorg-server-1.0.2-r3 cause virtual/x11-6.8 to be selected (why and how is beyond me). I've checked my USE flags with 'ufed', and "accessibility" is not defined. What can I do next if I want both xorg 7 and The Gimp installed at the same time?
><... snip ...> You snipped the interesting part...
(In reply to comment #1) > ><... snip ...> > > You snipped the interesting part... > Yeah, exactly... Reopen once you find the offending ebuild.
That was the point of the whole thing - the interesting part is not there. After the snip there's just a bunch of totally unrelated packages with U and a couple of N signs next to them. What did you expect to find there? I'll post the rest when I get near the box again, but there's really nothing interesting. (Hrm, on an unrelated note, out of curiosity, why are you setting the bug to RESOLVED when it's clearly not? Are you guys, how should I put it, abusing bugzilla to make it do something specific, or?)
(In reply to comment #3) > That was the point of the whole thing - the interesting part is not there. > After the snip there's just a bunch of totally unrelated packages with U and a > couple of N signs next to them. > What did you expect to find there? The ebuild that's not ported for modular X and so pulls in monolithic xorg. > (Hrm, on an unrelated note, out of curiosity, why are you setting the bug to > RESOLVED when it's clearly not? Are you guys, how should I put it, abusing > bugzilla to make it do something specific, or?) On an unrelated note, what's so unclear about NEEDINFO? http://bugs.gentoo.org/page.cgi?id=fields.html#resolution On a related note, we are not so much interested in reading long novels about sucky experience and more interested to see the unported ebuild identified. Reopen once you've identified it.
> Why would it even want to start downgrading xorg, now that I specifically ask it > to keep up to a certain version in /etc/portage/package.keywords: > =x11-base/xorg-x11-7.0-r1 That's not how package.keywords works at all, it doesn't keep up to any version, it only says to portage which keyword are you willing to accept for a given atom. Also, post your emerge info and attach (don't paste) /etc/portage/package.keywords file.
> On an unrelated note, what's so unclear about NEEDINFO? Nobody mentioned NEEDINFO being unclear, what are you talking about? RESOLVED seems wrong, since the issue has not been resolved. > it only says to portage which keyword are > you willing to accept for a given atom. Ok, but I wasn't trying to start an argument about the precise inner workings of Portage. I was arguing that Portage is trying to downgrade a package to 6.8 when it has earlier been specifically told that I want 7.0-unstable, or any later stable version, which is what the line I mentioned effectively does. That behavior is not exactly very bright. And if Portage aims to be just a little bit bright about what it does, it would even constitute a bug :-). I'll add the rest of "emerge -D world" later (although I still can't see why it's not totally irrelevant, hmm).
(In reply to comment #6) > > On an unrelated note, what's so unclear about NEEDINFO? > > Nobody mentioned NEEDINFO being unclear, what are you talking about? > > RESOLVED seems wrong, since the issue has not been resolved. NEEDINFO is a resolution, that's how bugzilla works. > I'll add the rest of "emerge -D world" later (although I still can't see why > it's not totally irrelevant, hmm). Better make that emerge -uDpvt world.
Created attachment 84621 [details] output from 'emerge -uDvpt world' Okey dokey, here's the output of 'emerge -uDvpt world'.
You seem to be missing virtual/x11 in your package.keywords.
Ok, thanks. I was of the impression that modular X does not use virtual/x11 anymore. If you don't mind helping me out a bit more, what's the exact line I need?
Created attachment 84622 [details] FYI - package.keywords I couldn't find a way to tell Portage "Go ahead and merge xorg7 even though it's ~x86, and also go ahead and merge any ~x86 dependencies that it has", so I had to make a script to add do that. The script-generated entries are the ones listed at the end of the file.
> You seem to be missing virtual/x11 in your package.keywords. Oh, and btw, HOW on EARTH did you figure that out from the emerge -D output??!
Our modular X howto (http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml) has a nice list of packages to put into package.keywords ;) http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-packages.txt
> Our modular X howto has a nice list of packages to put into package.keywords ;) It's lame having to put all that crap in there just to tell Portage "please use version 7 of xorg". > http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml There's a bug in that too: dev-python/pycrypto is missing from the list.
Please, don't reopen this bug, there's no bug here. It's how keywords work, period.
Closed.
No no, you've misunderstood me. The bug is that dev-python/pycrypto is missing from the package list you referred to. http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml I still think there's a Portage usability bug as mentioned earlier (you haven't commented anything on it), but that part I'll take to the mailing lists.
(In reply to comment #17) > No no, you've misunderstood me. No, not really, pycrypto has zero in common with modular X. Finally, you are free to put ~x86 or whatever other arch you are using to ACCEPT_KEYWORDS in make.conf and avoid all of this.
