public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Johansson <Dan.Johansson@dmj.nu>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Problems after reemerging xorg-x11
Date: Thu, 14 Sep 2006 18:46:55 +0200	[thread overview]
Message-ID: <200609141847.07033.Dan.Johansson@dmj.nu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2275 bytes --]

Today I did the "mistake" of re-emerging 
(emerge --update --deep --verbose --newuse world --pretend
) x11-base/xorg-x11-6.8.2-r8 as a result of a changed USE-flag 
(GAPING_SECURITY_HOLE). Now when I try to do a new 
emerge --update --deep --verbose --newuse world --pretend
 I am getting a lot of blocked packages and emerge also wants to pull in a lot 
of new packages. Here is a part of the output of the emerge....:

[blocks B     ] <=x11-base/xorg-x11-6.9 (is blocking
x11-proto/kbproto-1.0.3)
[blocks B     ] <=x11-base/xorg-x11-6.9 (is blocking
x11-misc/util-macros-1.1.0)
[blocks B     ] <=x11-base/xorg-x11-6.9 (is blocking
x11-libs/libX11-1.0.3)
[blocks B     ] <=x11-base/xorg-x11-6.9 (is blocking
x11-proto/xextproto-7.0.2)
[blocks B     ] <=x11-base/xorg-x11-6.9 (is blocking
x11-proto/xf86bigfontproto-1.1.2)
<...SNIP...>
[blocks B     ] x11-libs/libxkbui (is blocking
x11-base/xorg-x11-6.8.2-r8)
[blocks B     ] x11-libs/libXp (is blocking x11-base/xorg-x11-6.8.2-r8)
[blocks B     ] x11-misc/xorg-cf-files (is blocking
x11-base/xorg-x11-6.8.2-r8)
[blocks B     ] x11-misc/imake (is blocking x11-base/xorg-x11-6.8.2-r8)
[blocks B     ] <=x11-base/xorg-x11-6.9 (is blocking
x11-libs/libXxf86dga-1.0.1)
[ebuild  N    ] x11-misc/util-macros-1.1.0  USE="-debug" 42 kB
[ebuild  N    ] x11-proto/kbproto-1.0.3  USE="-debug" 56 kB
[ebuild  N    ] x11-proto/xextproto-7.0.2  USE="-debug" 66 kB
[ebuild  N    ] x11-proto/xf86bigfontproto-1.1.2  USE="-debug" 36 kB
[ebuild  N    ] x11-proto/inputproto-1.3.2  USE="-debug" 45 kB
<...SNIP...>
[ebuild  N    ] x11-misc/xorg-cf-files-1.0.2  USE="-debug" 258 kB
[ebuild  N    ] x11-misc/imake-1.0.2  USE="-debug" 110 kB
[ebuild  N    ] x11-libs/libXScrnSaver-1.1.0  USE="-debug" 221 kB
[ebuild  N    ] app-text/rman-3.2  77 kB
[ebuild  N    ] x11-libs/libXxf86dga-1.0.1  USE="-debug" 226 kB

I have ">x11-base/xorg-x11-6.8.2-r8" in /etc/portage/package.mask
as I could not make my Laptop, with an ATI-videocard, work with the new 
modular X.

Any suggestions on how to solve this?
-- 
Dan Johansson, <http://www.dmj.nu>
***************************************************
This message is printed on 100% recycled electrons!
***************************************************

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2006-09-14 16:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14 16:46 Dan Johansson [this message]
2006-09-15  9:23 ` [gentoo-user] Problems after reemerging xorg-x11 Bo Ørsted Andresen
     [not found]   ` <9acccfe50609160952x19d14fb6l6765aa801a47a62d@mail.gmail.com>
2006-09-17 11:40     ` Bo Ørsted Andresen
2006-09-17 14:53       ` Kevin O'Gorman
2006-09-17 15:26         ` Mick
2006-09-17 18:23           ` Kevin O'Gorman
2006-09-18  2:30             ` Walter Dnes
2006-09-17 23:16         ` Ryan Tandy
2006-09-18  0:46           ` Kevin O'Gorman

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=200609141847.07033.Dan.Johansson@dmj.nu \
    --to=dan.johansson@dmj.nu \
    --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