public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/portage/, sys-apps/portage/files/
Date: Sun, 20 Nov 2022 23:37:19 +0000 (UTC)	[thread overview]
Message-ID: <1668987432.1d184f1a99a9bbf53b1fc0f288300ed1979099f2.sam@gentoo> (raw)

commit:     1d184f1a99a9bbf53b1fc0f288300ed1979099f2
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Nov 20 23:36:46 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Nov 20 23:37:12 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1d184f1a

sys-apps/portage: make Portage less noisy on implicit func. decls for now

We will undo this again soon, but we need fewer high profiles to be
broken first, as it impacts wider testing & bug finding.

Bug: https://bugs.gentoo.org/870412
Signed-off-by: Sam James <sam <AT> gentoo.org>

 ...rtage-3.0.39-implicit-func-decls-no-fatal.patch | 34 ++++++++++++++++++++++
 ...tage-3.0.39.ebuild => portage-3.0.39-r1.ebuild} |  1 +
 2 files changed, 35 insertions(+)

diff --git a/sys-apps/portage/files/portage-3.0.39-implicit-func-decls-no-fatal.patch b/sys-apps/portage/files/portage-3.0.39-implicit-func-decls-no-fatal.patch
new file mode 100644
index 000000000000..4a4e68f2690a
--- /dev/null
+++ b/sys-apps/portage/files/portage-3.0.39-implicit-func-decls-no-fatal.patch
@@ -0,0 +1,34 @@
+https://github.com/gentoo/portage/commit/0fdbbbdb5a80e331adf701f2b2c1f096695447c4
+
+From 0fdbbbdb5a80e331adf701f2b2c1f096695447c4 Mon Sep 17 00:00:00 2001
+From: Sam James <sam@gentoo.org>
+Date: Sun, 20 Nov 2022 23:32:08 +0000
+Subject: [PATCH] install-qa-check.d/90gcc-warnings: don't make implicit func
+ decls fatal for now
+
+We need to do this at some point (as Clang 16 and GCC 14 are doing it, and
+they indicate runtime problems anyway), but there's too much breakage for now.
+
+We did find some extra bugs though. The main issue is too much high-profile
+stuff breaks rather than the total number of bugs, wrt Portage behaviour
+changing being suitable or not.
+
+Bug: https://bugs.gentoo.org/870412
+Signed-off-by: Sam James <sam@gentoo.org>
+--- a/bin/install-qa-check.d/90gcc-warnings
++++ b/bin/install-qa-check.d/90gcc-warnings
+@@ -153,9 +153,10 @@ gcc_warn_check() {
+ 			#	always_overflow=yes
+ 			#fi
+ 
+-			if [[ ${f} == *'[-Wimplicit-function-declaration]'* ]] ; then
+-				implicit_func_decl=yes
+-			fi
++			# Disabled for now because too many failures. bug #870412.
++			#if [[ ${f} == *'[-Wimplicit-function-declaration]'* ]] ; then
++			#	implicit_func_decl=yes
++			#fi
+ 
+ 			if [[ ${always_overflow} = yes || ${implicit_func_decl} = yes ]] ; then
+ 				eerror
+

diff --git a/sys-apps/portage/portage-3.0.39.ebuild b/sys-apps/portage/portage-3.0.39-r1.ebuild
similarity index 99%
rename from sys-apps/portage/portage-3.0.39.ebuild
rename to sys-apps/portage/portage-3.0.39-r1.ebuild
index 48ca5c0728ae..040a60847373 100644
--- a/sys-apps/portage/portage-3.0.39.ebuild
+++ b/sys-apps/portage/portage-3.0.39-r1.ebuild
@@ -85,6 +85,7 @@ pkg_pretend() {
 
 python_prepare_all() {
 	local PATCHES=(
+		"${FILESDIR}"/${P}-implicit-func-decls-no-fatal.patch
 	)
 
 	distutils-r1_python_prepare_all


             reply	other threads:[~2022-11-20 23:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20 23:37 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-17 13:05 [gentoo-commits] repo/gentoo:master commit in: sys-apps/portage/, sys-apps/portage/files/ Sam James
2024-05-10 18:26 Sam James
2023-12-03  8:02 Sam James
2023-10-26 15:53 Mike Gilbert
2023-07-30 13:10 Sam James
2023-07-15  3:45 Sam James
2023-02-28  3:14 Sam James
2023-01-13  3:50 Sam James
2022-11-30  7:07 Sam James
2022-11-20  2:46 Sam James
2022-10-26  0:23 Mike Gilbert
2022-10-20 15:49 Mike Gilbert
2022-04-24 16:45 WANG Xuerui
2022-04-15  8:37 Sam James
2018-01-02  2:49 Mike Gilbert
2016-09-19 14:00 Mike Gilbert
2016-05-16 16:20 Brian Dolbec

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=1668987432.1d184f1a99a9bbf53b1fc0f288300ed1979099f2.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