public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "James Le Cuirot" <chewi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/libdisplay-info/
Date: Tue, 12 Nov 2024 09:20:20 +0000 (UTC)	[thread overview]
Message-ID: <1731403206.9cc28f1d1f1f13da5537fe125931bd4b1fef97cf.chewi@gentoo> (raw)

commit:     9cc28f1d1f1f13da5537fe125931bd4b1fef97cf
Author:     James Le Cuirot <chewi <AT> gentoo <DOT> org>
AuthorDate: Tue Nov 12 09:18:39 2024 +0000
Commit:     James Le Cuirot <chewi <AT> gentoo <DOT> org>
CommitDate: Tue Nov 12 09:20:06 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9cc28f1d

media-libs/libdisplay-info: Fix dependencies following braindead change

Closes: https://bugs.gentoo.org/943304
Signed-off-by: James Le Cuirot <chewi <AT> gentoo.org>

 media-libs/libdisplay-info/libdisplay-info-0.1.1-r1.ebuild | 4 +---
 media-libs/libdisplay-info/libdisplay-info-0.2.0-r1.ebuild | 4 +---
 2 files changed, 2 insertions(+), 6 deletions(-)

diff --git a/media-libs/libdisplay-info/libdisplay-info-0.1.1-r1.ebuild b/media-libs/libdisplay-info/libdisplay-info-0.1.1-r1.ebuild
index 34f64507e0df..b00b441195f8 100644
--- a/media-libs/libdisplay-info/libdisplay-info-0.1.1-r1.ebuild
+++ b/media-libs/libdisplay-info/libdisplay-info-0.1.1-r1.ebuild
@@ -17,11 +17,9 @@ KEYWORDS="amd64 arm arm64 ~loong ppc64 ~riscv x86"
 IUSE="test"
 RESTRICT="!test? ( test )"
 
-BDEPEND="sys-apps/hwdata"
-DEPEND="${RDEPEND}"
-
 BDEPEND="
 	${PYTHON_DEPS}
+	sys-apps/hwdata
 	virtual/pkgconfig
 	test? ( >=sys-apps/edid-decode-0_pre20230131 )
 "

diff --git a/media-libs/libdisplay-info/libdisplay-info-0.2.0-r1.ebuild b/media-libs/libdisplay-info/libdisplay-info-0.2.0-r1.ebuild
index 685e3af49566..42cc136a58ff 100644
--- a/media-libs/libdisplay-info/libdisplay-info-0.2.0-r1.ebuild
+++ b/media-libs/libdisplay-info/libdisplay-info-0.2.0-r1.ebuild
@@ -15,10 +15,8 @@ LICENSE="MIT"
 SLOT="0/2"
 KEYWORDS="~amd64 ~arm ~arm64 ~loong ~ppc ~ppc64 ~riscv ~x86"
 
-BDEPEND="sys-apps/hwdata"
-DEPEND="${RDEPEND}"
-
 BDEPEND="
 	${PYTHON_DEPS}
+	sys-apps/hwdata
 	virtual/pkgconfig
 "


             reply	other threads:[~2024-11-12  9:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12  9:20 James Le Cuirot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-13  0:29 [gentoo-commits] repo/gentoo:master commit in: media-libs/libdisplay-info/ Sam James
2025-03-12 23:02 Sam James
2024-12-28 13:26 Arthur Zamarin
2024-12-28 10:49 Arthur Zamarin
2024-11-11 16:53 James Le Cuirot
2024-11-05  6:16 Arthur Zamarin
2024-08-31  2:42 Ionen Wolkens
2024-07-01 13:43 James Le Cuirot
2024-06-30 18:26 Michał Górny
2024-06-14 18:05 Sam James
2024-04-22 10:58 Michał Górny
2024-04-22 10:58 Michał Górny
2024-03-03 19:03 Michał Górny
2024-03-03 19:03 Michał Górny
2024-03-03 19:03 Michał Górny
2024-03-03 14:21 James Le Cuirot
2024-01-18 21:21 James Le Cuirot
2023-12-09 13:20 Michał Górny
2023-12-09 13:18 Sam James
2023-11-11 11:23 Yixun Lan
2023-02-17 23:21 James Le Cuirot
2023-02-17 23:21 James Le Cuirot
2023-02-14 23:11 James Le Cuirot
2023-02-12  9:53 James Le Cuirot

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=1731403206.9cc28f1d1f1f13da5537fe125931bd4b1fef97cf.chewi@gentoo \
    --to=chewi@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