From: "Rick Farina" <zerochaos@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-wireless/wireless-regdb/
Date: Wed, 23 Aug 2023 20:27:24 +0000 (UTC) [thread overview]
Message-ID: <1692822429.3035a26ee25ad314947f303fce416fc519d68bf2.zerochaos@gentoo> (raw)
commit: 3035a26ee25ad314947f303fce416fc519d68bf2
Author: Rick Farina <zerochaos <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 23 20:24:46 2023 +0000
Commit: Rick Farina <zerochaos <AT> gentoo <DOT> org>
CommitDate: Wed Aug 23 20:27:09 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3035a26e
net-wireless/wireless-regdb: adjust deps
When crda tests it needs wireless-regdb[crda] which causes a circular
dep issue. Resolve the circular dep using PDEPEND
Bug: https://bugs.gentoo.org/912865
Signed-off-by: Rick Farina <zerochaos <AT> gentoo.org>
...less-regdb-20230503-r1.ebuild => wireless-regdb-20230503-r2.ebuild} | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net-wireless/wireless-regdb/wireless-regdb-20230503-r1.ebuild b/net-wireless/wireless-regdb/wireless-regdb-20230503-r2.ebuild
similarity index 96%
rename from net-wireless/wireless-regdb/wireless-regdb-20230503-r1.ebuild
rename to net-wireless/wireless-regdb/wireless-regdb-20230503-r2.ebuild
index d2b51aad6229..4bf9984598e8 100644
--- a/net-wireless/wireless-regdb/wireless-regdb-20230503-r1.ebuild
+++ b/net-wireless/wireless-regdb/wireless-regdb-20230503-r2.ebuild
@@ -16,7 +16,8 @@ SLOT="0"
KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~ia64 ~loong ~mips ~ppc ~ppc64 ~riscv ~sparc ~x86"
IUSE="crda"
-RDEPEND="crda? ( net-wireless/crda )"
+#PDEPEND is required here or crda test dep causes circular deps
+PDEPEND="crda? ( net-wireless/crda )"
REQUIRED_USE="kernel_linux"
next reply other threads:[~2023-08-23 20:27 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 20:27 Rick Farina [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-01 12:42 [gentoo-commits] repo/gentoo:master commit in: net-wireless/wireless-regdb/ Sam James
2024-12-01 11:51 Sam James
2024-10-02 20:52 Sam James
2024-05-09 0:38 Rick Farina
2024-01-21 9:42 David Seifert
2023-08-19 20:58 Rick Farina
2023-08-19 16:52 Rick Farina
2023-08-19 16:52 Rick Farina
2023-08-19 16:52 Rick Farina
2023-08-19 16:52 Rick Farina
2023-06-17 15:13 Sam James
2023-03-19 23:10 Sam James
2022-06-06 16:56 Rick Farina
2022-06-06 16:56 Rick Farina
2022-05-05 23:48 WANG Xuerui
2022-04-08 16:48 Rick Farina
2022-04-04 14:56 Rick Farina
2022-04-04 14:56 Rick Farina
2021-10-04 20:40 Sam James
2021-05-18 15:52 Rick Farina
2021-05-18 15:52 Rick Farina
2021-05-18 15:52 Rick Farina
2021-02-27 3:56 Sam James
2021-02-26 15:56 Rick Farina
2021-02-12 10:33 Sam James
2021-02-03 9:56 Tony Vroon
2020-08-14 18:19 Rick Farina
2019-06-04 2:14 Rick Farina
2019-05-23 6:39 Aaron Bauman
2019-03-01 22:07 Rick Farina
2018-10-25 3:39 Richard Farina
2018-09-07 19:20 Richard Farina
2018-05-31 15:19 Richard Farina
2018-05-10 16:42 Richard Farina
2018-01-29 9:55 Tony Vroon
2018-01-26 18:05 Richard Farina
2017-03-08 22:46 Richard Farina
2016-06-10 15:46 Richard Farina
2016-05-02 22:18 Richard Farina
2016-02-08 22:47 Richard Farina
2015-10-22 17:00 Richard Farina
2015-09-30 17:30 Richard Farina
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=1692822429.3035a26ee25ad314947f303fce416fc519d68bf2.zerochaos@gentoo \
--to=zerochaos@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