From: "Matt Turner" <mattst88@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/catalyst:wip/mattst88 commit in: targets/stage1/
Date: Sun, 20 Nov 2022 00:21:27 +0000 (UTC) [thread overview]
Message-ID: <1665677830.2aceab45a9352f126ce5b7f8b04687fe1c28409d.mattst88@gentoo> (raw)
Message-ID: <20221120002127.RjSAyzi9Kq2nueyUNWaE0l1UILLzn5zOhw-HuEirM4Y@z> (raw)
commit: 2aceab45a9352f126ce5b7f8b04687fe1c28409d
Author: Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
AuthorDate: Mon Sep 26 16:30:25 2022 +0000
Commit: Matt Turner <mattst88 <AT> gentoo <DOT> org>
CommitDate: Thu Oct 13 16:17:10 2022 +0000
URL: https://gitweb.gentoo.org/proj/catalyst.git/commit/?id=2aceab45
targets: build initial baselayout with USE=build
current flow is the following:
update seed
install baselayout with USE=-build (for reasons unknown)
install @system with USE=build
this leads to a problem on usrmerged systems, because
baselayout with USE=-build that's installed initially does not create
usrmerge symlinks at all, so /bin /sbin are missing.
anything that installs files to those locations will be lost.
after installing baselayout initially with USE=-build --nodeps
we install the following
bzip2
gzip
tar
xz-utils
baselayout[build]
so everything installed before line above ^ loses / files completely.
This commit will change initial baselayout to USE=build
Closes: https://github.com/gentoo/catalyst/pull/10
Thanks-to: Mike Gilbert <floppym <AT> gentoo.org>
Signed-off-by: Georgy Yakovlev <gyakovlev <AT> gentoo.org>
Signed-off-by: Matt Turner <mattst88 <AT> gentoo.org>
targets/stage1/chroot.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/targets/stage1/chroot.sh b/targets/stage1/chroot.sh
index 08b9da46..e0587b59 100755
--- a/targets/stage1/chroot.sh
+++ b/targets/stage1/chroot.sh
@@ -61,9 +61,9 @@ mkdir -p "$ROOT"
## START BUILD
# First, we drop in a known-good baselayout
-[ -e ${clst_make_conf} ] && echo "USE=\"${USE} -build\"" >> ${clst_make_conf}
+[ -e ${clst_make_conf} ] && echo "USE=\"${USE} build\"" >> ${clst_make_conf}
run_merge --oneshot --nodeps sys-apps/baselayout
-sed -i "/USE=\"${USE} -build\"/d" ${clst_make_conf}
+sed -i "/USE=\"${USE} build\"/d" ${clst_make_conf}
echo "$locales" > /etc/locale.gen
for etc in /etc "$ROOT"/etc; do
next reply other threads:[~2022-11-20 0:21 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 16:17 Matt Turner [this message]
2022-11-20 0:21 ` [gentoo-commits] proj/catalyst:wip/mattst88 commit in: targets/stage1/ Matt Turner
-- strict thread matches above, loose matches on Subject: below --
2024-10-10 1:07 [gentoo-commits] proj/catalyst:master " Ben Kohler
2021-01-28 1:54 [gentoo-commits] proj/catalyst:pending/mattst88 " Matt Turner
2021-01-23 16:22 ` [gentoo-commits] proj/catalyst:master " Matt Turner
2021-01-28 1:54 [gentoo-commits] proj/catalyst:pending/mattst88 " Matt Turner
2021-01-23 16:22 ` [gentoo-commits] proj/catalyst:master " Matt Turner
2021-01-18 19:53 [gentoo-commits] proj/catalyst:pending/mattst88 " Matt Turner
2020-12-16 16:00 ` [gentoo-commits] proj/catalyst:master " Matt Turner
2021-01-18 19:53 [gentoo-commits] proj/catalyst:pending/mattst88 " Matt Turner
2020-12-16 16:00 ` [gentoo-commits] proj/catalyst:master " Matt Turner
2020-12-27 23:15 Matt Turner
2020-12-19 19:56 [gentoo-commits] proj/catalyst:wip/mattst88 " Matt Turner
2020-12-16 16:00 ` [gentoo-commits] proj/catalyst:master " Matt Turner
2020-12-19 19:56 [gentoo-commits] proj/catalyst:wip/mattst88 " Matt Turner
2020-12-16 16:00 ` [gentoo-commits] proj/catalyst:master " Matt Turner
2020-12-16 16:00 Matt Turner
2020-05-16 6:43 Matt Turner
2020-04-10 21:04 Matt Turner
2020-04-10 21:04 Matt Turner
2020-04-08 0:25 Matt Turner
2020-04-08 0:25 Matt Turner
2017-11-29 17:20 Brian Dolbec
2016-09-15 0:57 Richard Farina
2016-09-15 0:57 Richard Farina
2016-09-14 22:12 [gentoo-commits] proj/catalyst:fix_stage1 " Richard Farina
2016-09-15 0:57 ` [gentoo-commits] proj/catalyst:master " Richard Farina
2015-09-08 2:58 Richard Farina
2015-09-03 1:51 Richard Farina
2015-08-30 19:28 Jorge Manuel B. S. Vicetto
2015-08-30 4:32 Jorge Manuel B. S. Vicetto
2015-08-30 3:51 Jorge Manuel B. S. Vicetto
2015-08-30 3:14 Jorge Manuel B. S. Vicetto
2015-05-21 23:53 [gentoo-commits] proj/catalyst:pending " Brian Dolbec
2015-05-24 0:08 ` [gentoo-commits] proj/catalyst:master " Brian Dolbec
2014-09-02 5:54 [gentoo-commits] proj/catalyst:pending " Brian Dolbec
2014-09-11 3:26 ` [gentoo-commits] proj/catalyst:master " Brian Dolbec
2014-01-22 15:52 [gentoo-commits] proj/catalyst:pending " Brian Dolbec
2014-02-07 23:24 ` [gentoo-commits] proj/catalyst:master " Brian Dolbec
2014-01-22 15:52 [gentoo-commits] proj/catalyst:pending " Brian Dolbec
2014-02-07 23:24 ` [gentoo-commits] proj/catalyst:master " Brian Dolbec
2013-01-31 4:00 Richard Farina
2013-01-25 2:46 Matt Turner
2012-12-07 1:49 Jorge Manuel B. S. Vicetto
2012-11-21 5:20 Matt Turner
2012-10-23 17:18 Richard Farina
2012-10-22 1:20 Richard Farina
2012-09-03 3:09 Jorge Manuel B. S. Vicetto
2012-08-31 1:57 Jorge Manuel B. S. Vicetto
2012-08-29 3:18 Jorge Manuel B. S. Vicetto
2012-08-23 5:55 Jorge Manuel B. S. Vicetto
2012-08-23 5:55 Jorge Manuel B. S. Vicetto
2011-11-19 19:43 Jorge Manuel B. S. Vicetto
2011-11-16 4:05 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=1665677830.2aceab45a9352f126ce5b7f8b04687fe1c28409d.mattst88@gentoo \
--to=mattst88@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