From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/catalyst:catalyst_2 commit in: targets/support/
Date: Tue, 20 Dec 2011 07:16:30 +0000 (UTC) [thread overview]
Message-ID: <900554b0b067e76d3806e520357d91adbfa4fa0c.jmbsvicetto@gentoo> (raw)
commit: 900554b0b067e76d3806e520357d91adbfa4fa0c
Author: Jorge Manuel B. S. Vicetto (jmbsvicetto) <jmbsvicetto <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 20 07:14:05 2011 +0000
Commit: Jorge Manuel B. S. Vicetto <jmbsvicetto <AT> gentoo <DOT> org>
CommitDate: Tue Dec 20 07:14:05 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=900554b0
Make sure portage updates itself at the start of stage1 - thanks to Zac for noticing the issue.
---
targets/support/chroot-functions.sh | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/targets/support/chroot-functions.sh b/targets/support/chroot-functions.sh
index 277fdc2..74a7565 100644
--- a/targets/support/chroot-functions.sh
+++ b/targets/support/chroot-functions.sh
@@ -165,8 +165,9 @@ setup_pkgmgr(){
# We need to merge our package manager with USE="build" set in case it is
# portage to avoid frying our /etc/make.conf file. Otherwise, we could
# just let emerge system could merge it.
+ # Use --update or portage won't reinstall the same version.
[ -e /etc/make.conf ] && echo 'USE="${USE} build"' >> /etc/make.conf
- run_merge --oneshot --nodeps sys-apps/portage
+ run_merge --oneshot --nodeps --update sys-apps/portage
sed -i '/USE="${USE} build"/d' /etc/make.conf
}
next reply other threads:[~2011-12-20 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 7:16 Jorge Manuel B. S. Vicetto [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-22 2:47 [gentoo-commits] proj/catalyst:catalyst_2 commit in: targets/support/ Jorge Manuel B. S. Vicetto
2011-09-01 23:22 Matt Turner
2011-07-14 0:47 Jorge Manuel B. S. Vicetto
2011-06-25 21:47 Jorge Manuel B. S. Vicetto
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=900554b0b067e76d3806e520357d91adbfa4fa0c.jmbsvicetto@gentoo \
--to=jmbsvicetto@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@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