public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Bruno Lustosa" <bruno.lists@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] X.org is b0rked - BadIdChoice
Date: Mon, 3 Jul 2006 17:25:25 -0300	[thread overview]
Message-ID: <b9e0c3fe0607031325v136d5988jc0f529db673b7a7a@mail.gmail.com> (raw)
In-Reply-To: <44A97910.2000600@gentoo.org>

On 7/3/06, Donnie Berkholz <spyderous@gentoo.org> wrote:
> It's ~arch, you shouldn't get it unless you're running an ~arch system
> or specifically added it to package.keywords.

I am.
My system is all ~x86, except for gcc, glibc and binutils, because I
had an awful experience with those in the past, which left the system
completely unusable. glibc problems aren't something we want to have
to deal with (even python didn't run, so no portage to help).

> I don't think it should be tied into having anything else upgraded, with
> the exception of xproto 7.0.7, so I'm a bit surprised you're hitting
> these bugs. Good job tracking it down, though.

Yes, perhaps instead of masking individual package versions, I should
leave some of those packages tied to x86, that would still allow some
updates.
Anyway, I have the habit of looking at package.* and recheck if things
still need to be there. For example, I still have the unmasks for
gnome-2.14, which I think aren't needed anymore, so I'll remove them.

-- 
Bruno Lustosa <bruno@lustosa.net>
ZCE - Zend Certified Engineer - PHP!
http://www.lustosa.net/
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-07-03 20:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03 17:31 [gentoo-user] X.org is b0rked - BadIdChoice Bruno Lustosa
2006-07-03 19:38 ` Donnie Berkholz
2006-07-03 19:47   ` Bruno Lustosa
2006-07-03 20:07     ` Donnie Berkholz
2006-07-03 20:25       ` Bruno Lustosa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-03 18:20 Bruno Lustosa

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=b9e0c3fe0607031325v136d5988jc0f529db673b7a7a@mail.gmail.com \
    --to=bruno.lists@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