public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Freeman <rich0@verizon.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Messed up virtual/glibc?
Date: Mon, 11 Jul 2005 18:25:21 -0400	[thread overview]
Message-ID: <42D2F1D1.7080208@verizon.net> (raw)
In-Reply-To: <1121089729.30416.1.camel@localhost>

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Allan Wang wrote:
> 
> Try: grep -r 'virtual/glibc' /usr/portage
> 
> That might help find the broken ebuild/metadata. You might want to try
> it in your overlays too.
> 

I had thought of doing the grep on /usr/portage, but you had a good
point in checking the overlay.  I discovered I had a glibc package
hidden in there, and after I nuked it the problem went away.  I'm not
quite sure why - it wasn't the version I was actually running.

In any case, I don't have nearly as much need for the overlay these days
- - I used to need it to unmask individual packages before the invention
of /etc/portage.

Thanks for the ideas!


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFC0vHRg2bN8aFizRkRAtoXAJ9lp8c5JaV9mOlv1+CNk2tx8v+dugCbBH7u
lOtwiLNe+op2Vlk5RZl6OI0=
=v3Np
-----END PGP SIGNATURE-----

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3999 bytes --]

  reply	other threads:[~2005-07-11 22:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-11  0:49 [gentoo-amd64] Messed up virtual/glibc? Richard Freeman
2005-07-11  9:17 ` Simon Stelling
2005-07-11 11:24   ` Richard Freeman
2005-07-11 13:48     ` Allan Wang
2005-07-11 22:25       ` Richard Freeman [this message]
2005-07-12  9:15         ` [gentoo-amd64] " Duncan
2005-07-11 11:54 ` [gentoo-amd64] " Zac Medico
2005-07-11 13:47   ` Richard Freeman
2005-07-11 14:16     ` Zac Medico

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=42D2F1D1.7080208@verizon.net \
    --to=rich0@verizon.net \
    --cc=gentoo-amd64@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