public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joshua Kinard" <kumba@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: scripts/
Date: Mon,  2 Oct 2023 03:25:15 +0000 (UTC)	[thread overview]
Message-ID: <1696216717.67495c6078f95162d424d1c0942ad55c33a02149.kumba@gentoo> (raw)

commit:     67495c6078f95162d424d1c0942ad55c33a02149
Author:     Joshua Kinard <kumba <AT> gentoo <DOT> org>
AuthorDate: Mon Oct  2 03:18:37 2023 +0000
Commit:     Joshua Kinard <kumba <AT> gentoo <DOT> org>
CommitDate: Mon Oct  2 03:18:37 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=67495c60

scripts/bootstrap.sh: Don't bail if 'emerge --prune' returns 1

If 'emerge --prune' doesn't find any older gcc's to prune, it
will return '1', which causes bootstrap.sh to run the cleanup
method, and this results in catalyst aborting at the end of a
stage2 build.  Removing the all to cleanup prevents this.
Issue was added due to resolution of Bug #851750.

Closes: https://bugs.gentoo.org/881839
Signed-off-by: Joshua Kinard <kumba <AT> gentoo.org>

 scripts/bootstrap.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/bootstrap.sh b/scripts/bootstrap.sh
index 1e998075691a..48ed539e8186 100755
--- a/scripts/bootstrap.sh
+++ b/scripts/bootstrap.sh
@@ -351,7 +351,7 @@ if [[ -n ${STRAP_RUN} ]] ; then
 		fi
 		if [[ "${output}" = *'All selected packages:'* ]] ; then
 			# Make sure we get the old gcc unmerged ...
-			${V_ECHO} emerge ${STRAP_EMERGE_OPTS} --prune sys-devel/gcc || cleanup 1
+			${V_ECHO} emerge ${STRAP_EMERGE_OPTS} --prune sys-devel/gcc
 			# Make sure the profile and /lib/cpp and /usr/bin/cc are valid ...
 			${GCC_CONFIG} "$(${GCC_CONFIG} --get-current-profile)" &>/dev/null
 		fi


             reply	other threads:[~2023-10-02  3:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02  3:25 Joshua Kinard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-12 11:08 [gentoo-commits] repo/gentoo:master commit in: scripts/ Sam James
2024-01-12 11:08 Sam James
2024-01-12 11:08 Sam James
2023-02-22 16:21 Sam James
2022-04-19 21:17 Mike Gilbert
2022-04-19 21:12 Mike Gilbert
2021-09-02 10:58 Ulrich Müller
2020-06-07 13:15 Ulrich Müller
2020-03-30  1:37 Matt Turner
2020-03-29 17:45 Matt Turner
2020-03-29 17:45 Matt Turner
2020-03-29 17:45 Matt Turner
2020-03-29 17:45 Matt Turner
2020-01-19  5:08 Zac Medico
2020-01-19  4:39 Zac Medico
2017-03-04 18:11 Jorge Manuel B. S. Vicetto
2017-03-04 18:11 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=1696216717.67495c6078f95162d424d1c0942ad55c33a02149.kumba@gentoo \
    --to=kumba@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