From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Use and removal of binary packages
Date: Wed, 14 Jun 2006 07:42:43 -0700 [thread overview]
Message-ID: <9acccfe50606140742j4f7adfb2pa339dc16afa06689@mail.gmail.com> (raw)
In-Reply-To: <7573e9640606132226j36c6af28v342b0c72e9f8d3ba@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]
On 6/13/06, Richard Fish <bigfish@asmallpond.org> wrote:
>
> On 6/13/06, Kevin O'Gorman <kogorman@gmail.com> wrote:
> > Something about this is just not clicking with me. I restored my backup
> to
> > an empty directory, chrooted to that directory, ran quickpkg on some of
> the
> > packages I've been trying to re-emerge, and was feeling good. But...
> >
> > I got out of chroot, copied these to $PKGDIR (/usr/portage/packages)
> like
> > the other packages there, and tried to emerge. No joy. Examples of
> > what I tried:
> > > treat Backups # emerge -v --usepkgonly =glib-1.2.10-r5
> > > Calculating dependencies
> > > !!! There are no packages available to satisfy: "=glib-1.2.10-r5"
> > > !!! Either add a suitable binary package or compile from an ebuild.
>
> Did you copy the entire PKGDIR heirarchy? It normally looks something
> like:
>
> $PKGDIR/All/glib-1.2.10-r5.tbz2
> ...
> $PKGDIR/dev-libs/glib-1.2.10-r5.tbz2 -> ../All/glib-1.2.10-r5.tbz2
>
> If you just copied the 'All' directory, without the symlinks, this
> could account for the behavior you are seeing.
>
> -Richard
Okay, that helped. But not as much as I had hoped.
Now I get:
> treat dev-libs # emerge -avk =glib-1.2.10-r5
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies -
> emerge: there are no ebuilds to satisfy "virtual/glibc".
> (dependency required by "dev-libs/glib-1.2.10-r5" [binary])
>
> treat dev-libs #
So it sees that it has the glib package, but is still unwilling to emerge it
because of something else I need to do. But I don't know how to find
out what to do about this virtual. In /var/cache/edb/virtuals, I have
> virtual/glibc sys-libs/glibc
>
and I have 2.3.6-r3 installed:
> sys-libs/glibc
> Available versions: [P]2.2.5-r10 [P]2.3.2-r12 2.3.3.20040420-r2~2.3.4.20040619-r2
> 2.3.4.20040808-r1 2.3.4.20041102-r1 *2.3.4.20041102-r2 ~2.3.4.20050125-r1
> 2.3.5 2.3.5-r1 2.3.5-r2 2.3.5-r3 *2.3.6 *2.3.6-r1 ~2.3.6-r2 2.3.6-r3~2.3.6-r4 ~2.4-r1 ~2.4-r2 ~2.4-r3
> Installed: 2.3.6-r3
> Homepage: http://www.gnu.org/software/libc/libc.html
> Description: GNU libc6 (also called glibc2) C library
>
>
++ kevin
--
Kevin O'Gorman, PhD
[-- Attachment #2: Type: text/html, Size: 3521 bytes --]
next prev parent reply other threads:[~2006-06-14 14:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 16:40 [gentoo-user] Use and removal of binary packages Kevin O'Gorman
2006-06-13 17:10 ` Neil Bothwick
2006-06-13 20:08 ` Kevin O'Gorman
2006-06-13 20:58 ` Neil Bothwick
2006-06-13 22:01 ` [gentoo-user] Raid and Gentoo Rafael Fernández López
2006-06-13 22:35 ` Barny M
2006-06-14 4:46 ` [gentoo-user] Use and removal of binary packages Kevin O'Gorman
2006-06-14 5:26 ` Richard Fish
2006-06-14 14:42 ` Kevin O'Gorman [this message]
2006-06-14 16:07 ` Neil Bothwick
2006-06-14 16:38 ` 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=9acccfe50606140742j4f7adfb2pa339dc16afa06689@mail.gmail.com \
--to=kogorman@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