From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: lib/portage/package/ebuild/
Date: Wed, 20 Dec 2023 14:04:24 +0000 (UTC) [thread overview]
Message-ID: <1703081052.b39e1edca0ee73f29b5513ab30f00da14d1291bc.sam@gentoo> (raw)
commit: b39e1edca0ee73f29b5513ab30f00da14d1291bc
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Wed Dec 20 06:36:38 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Dec 20 14:04:12 2023 +0000
URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=b39e1edc
ebuild: command not found QA: don't skip QA warnings that come from ./configure
Down through the twisting trail of history, we find a 2008 bug report
and commit 930bbbf31c10265b27825426f1eff6d7f17395e6, which disabled
detecting "command not found" in ./configure scripts with the following
rationale:
> This is actually a false positive. I'll fix it to filter out the ones that are generated by configure scripts.
As far as I can tell it wasn't a false positive though. Looking up the
source code for that old project reveals no indication that it can
misfire in "expected" ways. More generally, this obscures real issues in
configure scripts -- why should configure scripts be special here? --
which have *zero* guarantee of resulting in failure. Anecdotally, they
usually do not.
Whatever the underlying issue is, it's *definitely* an upstream bug and
*almost certainly* indicates that there may be situations where the
project miscompiles against expectations.
Bug: https://bugs.gentoo.org/245716
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Closes: https://github.com/gentoo/portage/pull/1210
Signed-off-by: Sam James <sam <AT> gentoo.org>
lib/portage/package/ebuild/doebuild.py | 11 ++---------
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/lib/portage/package/ebuild/doebuild.py b/lib/portage/package/ebuild/doebuild.py
index e651f28d06..b10bbaf30d 100644
--- a/lib/portage/package/ebuild/doebuild.py
+++ b/lib/portage/package/ebuild/doebuild.py
@@ -2275,7 +2275,6 @@ def _check_build_log(mysettings, out=None):
r"(.*): line (\d*): (.*): command not found$"
)
dash_command_not_found_re = re.compile(r"(.*): (\d+): (.*): not found$")
- command_not_found_exclude_re = re.compile(r"/configure: line ")
helper_missing_file = []
helper_missing_file_re = re.compile(r"^!!! (do|new).*: .* does not exist$")
@@ -2379,16 +2378,10 @@ def _check_build_log(mysettings, out=None):
):
am_maintainer_mode.append(line.rstrip("\n"))
- if (
- bash_command_not_found_re.match(line) is not None
- and command_not_found_exclude_re.search(line) is None
- ):
+ if bash_command_not_found_re.match(line) is not None:
command_not_found.append(line.rstrip("\n"))
- if (
- dash_command_not_found_re.match(line) is not None
- and command_not_found_exclude_re.search(line) is None
- ):
+ if dash_command_not_found_re.match(line) is not None:
command_not_found.append(line.rstrip("\n"))
if helper_missing_file_re.match(line) is not None:
next reply other threads:[~2023-12-20 14:04 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 14:04 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-07 14:39 [gentoo-commits] proj/portage:master commit in: lib/portage/package/ebuild/ Zac Medico
2024-07-19 5:41 Sam James
2024-06-17 0:25 Sam James
2024-06-17 0:20 Sam James
2024-03-24 22:20 Zac Medico
2023-12-20 14:04 Sam James
2023-12-20 14:04 Sam James
2023-12-10 22:01 Sam James
2023-10-22 22:46 Zac Medico
2023-10-16 5:15 Zac Medico
2023-10-13 10:33 Sam James
2023-10-13 10:19 Sam James
2023-10-13 10:19 Sam James
2023-08-19 15:05 Sam James
2023-06-14 19:23 Mike Gilbert
2023-06-14 19:23 Mike Gilbert
2023-02-17 0:53 Sam James
2023-01-27 8:38 Ulrich Müller
2023-01-02 20:45 Mike Gilbert
2022-07-12 23:33 Sam James
2022-06-12 18:25 Sam James
2021-12-11 2:54 Sam James
2021-12-11 2:54 Sam James
2021-11-15 8:34 Michał Górny
2021-11-08 22:37 Zac Medico
2021-10-28 5:00 Sam James
2021-10-28 4:52 Sam James
2021-10-03 19:31 Zac Medico
2021-09-28 11:25 Michał Górny
2021-09-28 11:19 Michał Górny
2021-09-28 7:21 Zac Medico
2021-09-27 20:51 Michał Górny
2021-09-08 10:17 Michał Górny
2021-08-05 8:47 Michał Górny
2021-06-20 18:54 Zac Medico
2021-06-05 18:08 Zac Medico
2021-06-05 18:08 Zac Medico
2021-05-31 19:54 Michał Górny
2021-05-24 5:25 Zac Medico
2021-02-25 9:33 Zac Medico
2021-02-24 15:14 Zac Medico
2021-02-22 5:32 Zac Medico
2021-01-17 13:15 Zac Medico
2021-01-10 3:24 Zac Medico
2020-11-02 1:34 Zac Medico
2020-09-14 7:23 Zac Medico
2020-08-03 21:42 Zac Medico
2020-08-03 21:42 Zac Medico
2020-08-03 19:30 Zac Medico
2020-08-03 19:30 Zac Medico
2020-08-03 19:30 Zac Medico
2020-05-31 23:58 Mike Gilbert
2020-05-31 21:17 Mike Gilbert
2020-05-31 20:34 Mike Gilbert
2020-05-18 19:23 Michał Górny
2020-05-06 6:37 Michał Górny
2020-03-23 1:49 Zac Medico
2020-03-23 1:40 Zac Medico
2020-03-15 1:24 Zac Medico
2020-03-02 16:53 Zac Medico
2020-03-02 4:48 Zac Medico
2020-02-15 20:44 Zac Medico
2020-02-15 20:28 Zac Medico
2019-12-09 7:03 Zac Medico
2019-10-29 1:17 Zac Medico
2019-10-24 19:31 Zac Medico
2019-10-21 17:49 Zac Medico
2019-10-20 9:26 Michał Górny
2019-10-19 23:52 Zac Medico
2019-10-14 20:45 Zac Medico
2019-10-14 20:35 Zac Medico
2019-10-14 20:13 Zac Medico
2019-10-13 19:50 Michał Górny
2019-09-03 15:36 Zac Medico
2019-09-02 20:13 Zac Medico
2019-08-20 23:43 Zac Medico
2019-08-14 1:40 Zac Medico
2019-07-30 7:09 Ulrich Müller
2019-06-18 17:14 Zac Medico
2019-06-10 19:01 Zac Medico
2019-01-21 22:20 Zac Medico
2019-01-01 20:58 Zac Medico
2018-12-20 4:29 Zac Medico
2018-12-07 0:41 Zac Medico
2018-11-19 6:43 Zac Medico
2018-11-09 3:22 Zac Medico
2018-10-10 7:58 Zac Medico
2018-10-08 21:41 Zac Medico
2018-08-20 23:11 Zac Medico
2018-08-17 22:35 Zac Medico
2018-08-12 2:31 Zac Medico
2018-08-11 21:06 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=1703081052.b39e1edca0ee73f29b5513ab30f00da14d1291bc.sam@gentoo \
--to=sam@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