From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: profiles/arch/powerpc/ppc64/64le/
Date: Wed, 26 Jun 2024 05:29:57 +0000 (UTC) [thread overview]
Message-ID: <1719379722.47799fa3e19e23e1821440e1729adafd6af08923.sam@gentoo> (raw)
commit: 47799fa3e19e23e1821440e1729adafd6af08923
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Jun 26 05:28:32 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Jun 26 05:28:42 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=47799fa3
profiles/arch/powerpc/ppc64/64le: add warning about FPs with UnmatchedProfilePackageUnmask
Bug: https://github.com/pkgcore/pkgcheck/issues/685
Signed-off-by: Sam James <sam <AT> gentoo.org>
profiles/arch/powerpc/ppc64/64le/package.mask | 3 +++
1 file changed, 3 insertions(+)
diff --git a/profiles/arch/powerpc/ppc64/64le/package.mask b/profiles/arch/powerpc/ppc64/64le/package.mask
index c28d945aaa1c..aa4f7d7393b0 100644
--- a/profiles/arch/powerpc/ppc64/64le/package.mask
+++ b/profiles/arch/powerpc/ppc64/64le/package.mask
@@ -1,6 +1,9 @@
# Copyright 1999-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
+# WARNING: UnmatchedProfilePackageUnmask has a bug with false positives here
+# https://github.com/pkgcore/pkgcheck/issues/685
+
# matoro <matoro_gentoo@matoro.tk> (2024-06-10)
# Unmask for ppc64le, #892183
-dev-python/sympy
next reply other threads:[~2024-06-26 5:30 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 5:29 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-26 5:25 [gentoo-commits] repo/gentoo:master commit in: profiles/arch/powerpc/ppc64/64le/ Sam James
2024-06-22 21:33 Sam James
2024-06-22 17:15 Sam James
2024-06-08 9:31 James Le Cuirot
2024-04-26 22:07 James Le Cuirot
2024-04-24 11:39 Michał Górny
2024-03-27 3:02 Zac Medico
2024-02-02 17:26 Jakov Smolić
2023-10-02 15:05 Sam James
2023-01-11 21:28 Georgy Yakovlev
2022-11-10 8:12 Joonas Niilola
2022-05-04 1:21 Sam James
2022-01-22 22:54 Georgy Yakovlev
2022-01-20 11:41 Georgy Yakovlev
2022-01-20 9:25 Georgy Yakovlev
2022-01-20 9:22 Georgy Yakovlev
2022-01-20 9:09 Georgy Yakovlev
2021-12-23 23:59 Sam James
2021-11-14 7:51 Georgy Yakovlev
2021-10-08 15:02 Georgy Yakovlev
2021-07-20 0:51 Georgy Yakovlev
2021-07-20 0:47 Georgy Yakovlev
2021-07-07 3:00 Georgy Yakovlev
2021-06-10 4:17 Georgy Yakovlev
2021-06-03 6:21 Georgy Yakovlev
2021-05-16 18:33 Georgy Yakovlev
2021-05-16 18:33 Georgy Yakovlev
2021-05-16 18:33 Georgy Yakovlev
2021-05-16 18:33 Georgy Yakovlev
2021-05-16 18:33 Georgy Yakovlev
2021-05-16 17:12 Georgy Yakovlev
2020-10-18 2:19 Georgy Yakovlev
2020-10-18 0:48 Georgy Yakovlev
2020-10-16 17:46 Georgy Yakovlev
2020-10-16 17:46 Georgy Yakovlev
2020-10-06 1:17 Georgy Yakovlev
2020-09-22 20:25 Georgy Yakovlev
2020-09-20 2:48 Georgy Yakovlev
2020-09-06 4:24 Georgy Yakovlev
2020-08-28 18:05 Georgy Yakovlev
2020-02-27 20:15 Georgy Yakovlev
2020-02-27 16:12 Ben Kohler
2020-02-27 6:11 Georgy Yakovlev
2020-02-27 4:06 Georgy Yakovlev
2020-01-25 10:32 Georgy Yakovlev
2020-01-22 9:33 Georgy Yakovlev
2020-01-22 9:33 Georgy Yakovlev
2020-01-22 8:37 Georgy Yakovlev
2020-01-22 5:41 Georgy Yakovlev
2020-01-22 5:41 Georgy Yakovlev
2020-01-22 5:41 Georgy Yakovlev
2020-01-22 5:41 Georgy Yakovlev
2019-08-30 2:14 Georgy Yakovlev
2019-08-30 2:10 Georgy Yakovlev
2019-08-16 6:45 Georgy Yakovlev
2019-08-16 6:45 Georgy Yakovlev
2019-08-16 6:45 Georgy Yakovlev
2019-08-16 6:45 Georgy Yakovlev
2019-08-16 0:16 Georgy Yakovlev
2019-08-15 21:38 Georgy Yakovlev
2019-08-15 6:54 Georgy Yakovlev
2019-08-15 6:54 Georgy Yakovlev
2019-08-15 6:54 Georgy Yakovlev
2019-02-04 19:45 Georgy Yakovlev
2018-11-08 23:11 James Le Cuirot
2018-04-11 21:20 Sergei Trofimovich
2018-04-11 20:55 Sergei Trofimovich
2017-03-20 23:02 Mike Frysinger
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=1719379722.47799fa3e19e23e1821440e1729adafd6af08923.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