From: "Mike Gilbert" <floppym@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: lib/portage/util/
Date: Wed, 26 Jul 2023 14:30:55 +0000 (UTC) [thread overview]
Message-ID: <1690381668.581f923b9f888efc3313b6e06ba8a3cf84641d75.floppym@gentoo> (raw)
commit: 581f923b9f888efc3313b6e06ba8a3cf84641d75
Author: Mike Gilbert <floppym <AT> gentoo <DOT> org>
AuthorDate: Wed Jul 26 14:27:48 2023 +0000
Commit: Mike Gilbert <floppym <AT> gentoo <DOT> org>
CommitDate: Wed Jul 26 14:27:48 2023 +0000
URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=581f923b
env_update: drop os.waitstatus_to_exitcode
The subprocess.run() function does this translation already.
Fixes: 3bba408e214ae27bdf924ba90ad4b0919a85f3c8
Signed-off-by: Mike Gilbert <floppym <AT> gentoo.org>
lib/portage/util/env_update.py | 1 -
1 file changed, 1 deletion(-)
diff --git a/lib/portage/util/env_update.py b/lib/portage/util/env_update.py
index 9d3b5bb25..a827963ab 100644
--- a/lib/portage/util/env_update.py
+++ b/lib/portage/util/env_update.py
@@ -381,7 +381,6 @@ def _env_update(makelinks, target_root, prev_mtimes, contents, env, writemsg_lev
cwd="/",
).returncode
- ret = os.waitstatus_to_exitcode(ret)
if ret > 0:
writemsg(f"!!! ldconfig failed with exit status {ret}\n", noiselevel=-1)
if ret < 0:
next reply other threads:[~2023-07-26 14:30 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 14:30 Mike Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-15 17:30 [gentoo-commits] proj/portage:master commit in: lib/portage/util/ Mike Gilbert
2024-05-27 20:02 Zac Medico
2024-03-07 20:42 Mike Gilbert
2024-03-01 16:20 Mike Gilbert
2024-02-09 8:22 Zac Medico
2024-02-07 2:35 Zac Medico
2023-10-02 21:40 James Le Cuirot
2023-07-26 7:58 Sam James
2023-07-26 7:58 Sam James
2023-06-29 8:19 Sam James
2023-06-06 6:52 Sam James
2022-12-31 13:33 Sam James
2022-06-07 23:48 Mike Gilbert
2022-06-07 23:48 Mike Gilbert
2022-05-21 10:12 Michał Górny
2022-04-15 2:46 Sam James
2021-05-24 6:13 Zac Medico
2021-03-07 16:04 Zac Medico
2021-03-06 20:21 Zac Medico
2021-03-03 12:20 Zac Medico
2021-02-25 10:21 Zac Medico
2021-01-19 0:50 Zac Medico
2021-01-02 1:18 Zac Medico
2020-12-31 2:17 Zac Medico
2020-12-31 2:17 Zac Medico
2020-11-22 19:41 Zac Medico
2020-11-22 6:20 Zac Medico
2020-10-06 1:35 Zac Medico
2020-09-08 0:04 Zac Medico
2020-08-04 3:09 Zac Medico
2020-08-04 1:39 Zac Medico
2020-08-03 21:42 Zac Medico
2020-08-03 19:43 Ulrich Müller
2020-08-03 19:30 Zac Medico
2020-07-18 22:56 Zac Medico
2020-03-14 23:40 Zac Medico
2019-10-19 6:03 Zac Medico
2019-08-08 22:58 Zac Medico
2019-06-10 18:20 Zac Medico
2019-05-20 4:46 Zac Medico
2019-04-15 23:04 Zac Medico
2019-02-16 17:42 Robin H. Johnson
2019-02-16 16:48 Robin H. Johnson
2019-02-06 22:45 Zac Medico
2018-12-17 7:09 Zac Medico
2018-08-04 20:27 Zac Medico
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=1690381668.581f923b9f888efc3313b6e06ba8a3cf84641d75.floppym@gentoo \
--to=floppym@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