From: Michael George <george@mutualdata.com>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] quickpkg problems
Date: Tue, 2 Jan 2007 22:03:10 -0500 [thread overview]
Message-ID: <20070103030310.GA3184@brego.pewamo.office> (raw)
I'm updating my system with my normal CHROOT method where I update all
teh packages in a CHROOT and then make packages of them for my real
system.
For the first time, I am doing this to my amd64 system rather than my
x86 system, and I've had a couple glitches.
Because /lib and /usr/lib are symlinked to /lib64 and /usr/lib64, the
packages I made in my CHROOT won't extract correctly. It will get to
extracting /lib (or /usr/lib), which is a symlink, and it cannot create
the next level of directories within it because the referenced directory
doesn't exist where the package is being extracted.
Am I doing something wrong in creating the packages, or in extracting
them?
Thanks!
--
-M
There are 10 kinds of people in this world:
Those who can count in binary and those who cannot.
--
gentoo-amd64@gentoo.org mailing list
next reply other threads:[~2007-01-03 3:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 3:03 Michael George [this message]
2007-01-04 7:31 ` [gentoo-amd64] Re: quickpkg problems Duncan
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=20070103030310.GA3184@brego.pewamo.office \
--to=george@mutualdata.com \
--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