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: mate-base/mate-settings-daemon/
Date: Sun,  6 Oct 2024 07:17:37 +0000 (UTC)	[thread overview]
Message-ID: <1728199003.6fcd244dbad69d4f068a3489e4d1f344eba826c7.sam@gentoo> (raw)

commit:     6fcd244dbad69d4f068a3489e4d1f344eba826c7
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Oct  6 07:13:38 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Oct  6 07:16:43 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6fcd244d

mate-base/mate-settings-daemon: depend on min mate-desktop matching ${PV}

Depend on >=mate-desktop-$(ver_cut 1-2) to avoid build failures for now
as a quick workaround.

The maintainers should check whether each package really needs it and
also consider a possible QA check in the eclass given some of them
seem to have a pattern in configure.ac for this, but given the bug has
been open for a whlie, I'd rather have some of the deps be unnecessarily
tight (not that it's even that tight) than as-it-was.

Note that couldn't use ${MATE_BRANCH} as it says:
> # Major and minor numbers of the version number, unless live.
> # If live ebuild, will be set to '9999'.
which made me wonder if it's actually meant to be 1-2 or 1-3 in ver_cut
or what.

Anyway, in summary:
* Apply a fix which makes things better, even if it's slightly overkill;
* Someone needs to audit these to find the actual minimum versions
  (some truly do need this, some need just something older, although
  unclear if upstream carefully update these or ont);
* A QA check may be wise.

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

 mate-base/mate-settings-daemon/mate-settings-daemon-1.28.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mate-base/mate-settings-daemon/mate-settings-daemon-1.28.0.ebuild b/mate-base/mate-settings-daemon/mate-settings-daemon-1.28.0.ebuild
index 0b485fee7b6b..0033a6281c89 100644
--- a/mate-base/mate-settings-daemon/mate-settings-daemon-1.28.0.ebuild
+++ b/mate-base/mate-settings-daemon/mate-settings-daemon-1.28.0.ebuild
@@ -24,7 +24,7 @@ COMMON_DEPEND=">=dev-util/gdbus-codegen-2.76.4
 	>=dev-libs/glib-2.50:2
 	>=gnome-base/dconf-0.13.4
 	>=mate-base/libmatekbd-1.17.0
-	>=mate-base/mate-desktop-1.27.1
+	>=mate-base/mate-desktop-$(ver_cut 1-2)
 	media-libs/fontconfig:1.0
 	x11-libs/cairo
 	x11-libs/gdk-pixbuf:2


             reply	other threads:[~2024-10-06  7:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-06  7:17 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-04 18:39 [gentoo-commits] repo/gentoo:master commit in: mate-base/mate-settings-daemon/ Andreas Sturmlechner
2024-09-17 17:50 Andreas Sturmlechner
2024-07-08 21:33 Pacho Ramos
2024-03-19  8:23 Joonas Niilola
2024-03-19  8:23 Joonas Niilola
2023-12-22  6:46 Sam James
2023-10-09 18:57 Sam James
2023-10-09 18:00 Sam James
2023-06-10 22:56 Andreas Sturmlechner
2022-12-21 10:00 Andreas Sturmlechner
2022-06-28  6:08 Sam James
2022-06-28  2:03 WANG Xuerui
2022-01-09 15:48 Andreas Sturmlechner
2021-12-10 20:10 Jakov Smolić
2021-12-10 11:35 Jakov Smolić
2021-06-30 22:43 Adam Feldman
2020-09-25 21:29 Adam Feldman
2020-09-02  6:02 Adam Feldman
2019-05-12 21:04 Göktürk Yüksek
2019-04-14 21:24 Mikle Kolyada
2019-04-14 16:24 Mikle Kolyada
2019-04-14 15:27 Mikle Kolyada
2018-10-06 20:24 Mart Raudsepp
2018-09-09 23:53 Thomas Deutschmann
2018-02-11 15:03 Ettore Di Giacinto
2018-01-14 17:18 Ettore Di Giacinto
2016-08-06  2:12 NP Hardass
2016-03-26  2:37 NP Hardass
2016-03-15 17:53 Agostino Sarubbo
2016-03-06  8:09 Mikle Kolyada
2016-01-26 20:09 NP Hardass

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=1728199003.6fcd244dbad69d4f068a3489e4d1f344eba826c7.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