From: Richard Freeman <rich0@verizon.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Messed up virtual/glibc?
Date: Sun, 10 Jul 2005 20:49:07 -0400 [thread overview]
Message-ID: <42D1C203.3050609@verizon.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
For some reason after upgrading glibc yesterday many packages cannot be
emerged:
emerge -puD world
These are the packages that I would merge, in order:
Calculating world dependencies /
emerge: there are no ebuilds to satisfy "virtual/glibc".
!!! Problem with ebuild media-gfx/gimp-print-4.2.7
!!! Possibly a DEPEND/*DEPEND problem.
!!! Depgraph creation failed.
I do have sys-libs/glibc-2.3.5 installed, and I'm running
portage-2.0.51.22-r1.
This isn't just one package - if I mask the one that is complaining I'll
end up getting a complaint about another package.
revdep-rebuild didn't help either.
I've tried reinstalling glibc several times, and I've checked that
CHOST=CTARGET=CBUILD in emerge info.
Taking a quick look at glibc I see that it provides virtual/libc. Why
are other packages looking for virtual/glibc? It seems to be more than
one. Also - gimp-print does not contain any reference to virtual/glibc.
Does anybody have any ideas why portage is looking for virtual/glibc?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFC0cIDg2bN8aFizRkRAnFLAJ4/vQo7hq6IOtyPRbXPN8eNdgWf7ACdFwtG
KRRR6NeKtcPdxAGlfwIqM2A=
=lqFt
-----END PGP SIGNATURE-----
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3999 bytes --]
next reply other threads:[~2005-07-11 0:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 0:49 Richard Freeman [this message]
2005-07-11 9:17 ` [gentoo-amd64] Messed up virtual/glibc? Simon Stelling
2005-07-11 11:24 ` Richard Freeman
2005-07-11 13:48 ` Allan Wang
2005-07-11 22:25 ` Richard Freeman
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=42D1C203.3050609@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