From: Christian Heim <phreak@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge: xorg-x11 requires gentoo-sources
Date: Mon, 12 Jun 2006 18:49:35 +0000 [thread overview]
Message-ID: <200606121849.44968.phreak@gentoo.org> (raw)
In-Reply-To: <20060612163815.58107.qmail@web81507.mail.mud.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
On Monday 12 June 2006 16:38, Richard Ruth wrote:
>On one of two gentoo (x86_64 AMD Opteron) systems I just emerged the new
> portage-2.1 on, emerge is requiring gentoo-sources as a dependency required
> by "x11-base/xorg-x11-6.8.2-r7". Why?
>
>The 2nd system with an identical 2.6.16.20 vanilla-sources kernel does not
> have this problem.
>
>I tried removing the /usr/portage/x11-base directory and then running
> "emerge --sync". Which works buth then:
>
>============
>
># emerge -pv -u --deep world
> [snip]
>
>Yes, I do use /etc/portage/package.mask to mask out gentoo-sources, but I
> have done that for years. (Also, my 2nd system has the same package.mask
> and doesn't have a problem with xorg-x11.)
>
>Any suggestions on how to fix this dependencies issue? I suspect a portage
> cache issue that 'emerge --sync' is not fixing.
It's probably because something in xorg-x11 is requiring virtual/linux-sources
and for all normal default-linux/{amd64,x86} thats gentoo-sources. So just
emerge sys-kernel/vanilla-sources and it should be fine (since
vanilla-sources also provides virtual/linux-sources).
--
Christian Heim <phreak@gentoo.org>
Gentoo Linux Developer - vserver/openvz
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-06-12 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 16:38 [gentoo-user] emerge: xorg-x11 requires gentoo-sources Richard Ruth
2006-06-12 18:49 ` Christian Heim [this message]
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=200606121849.44968.phreak@gentoo.org \
--to=phreak@gentoo.org \
--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