From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-editors/pluma-plugins/
Date: Thu, 6 Jun 2024 00:45:41 +0000 (UTC) [thread overview]
Message-ID: <1717634687.d0a1a621733dcbecb51b75c9418afda80583611c.sam@gentoo> (raw)
commit: d0a1a621733dcbecb51b75c9418afda80583611c
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Wed Jun 5 03:04:50 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jun 6 00:44:47 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d0a1a621
app-editors/pluma-plugins: fix impossible dependency on gedit instead of pluma
Most likely this was copy-pasted from app-editors/gedit-plugins. In its
current state, there isn't even a good explanation for how this ever
built on anyone's machine, or passed stabilization checks, except that
stabilization of pluma-plugins plainly occurred in a batch alongside,
but after, pluma itself, leading to silently available undeclared
dependencies.
And yes, not only does this package check in configure for an installed
pluma -- it builds C code that includes headers named "pluma".
Most likely, anyone using the package doesn't suffer this confusion,
because they already have pluma installed; still, this metadata problem
is rather bad. Revbump via `mv`, drop old + immediate to stable, because
we want to get the metadata fix out ASAP.
Bug: https://github.com/gentoo/gentoo/pull/28508
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
...luma-plugins-1.26.0-r1.ebuild => pluma-plugins-1.26.0-r2.ebuild} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/app-editors/pluma-plugins/pluma-plugins-1.26.0-r1.ebuild b/app-editors/pluma-plugins/pluma-plugins-1.26.0-r2.ebuild
similarity index 92%
rename from app-editors/pluma-plugins/pluma-plugins-1.26.0-r1.ebuild
rename to app-editors/pluma-plugins/pluma-plugins-1.26.0-r2.ebuild
index 1969a87f5e98..bdfab472e753 100644
--- a/app-editors/pluma-plugins/pluma-plugins-1.26.0-r1.ebuild
+++ b/app-editors/pluma-plugins/pluma-plugins-1.26.0-r2.ebuild
@@ -1,4 +1,4 @@
-# Copyright 2021-2023 Gentoo Authors
+# Copyright 2021-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=7
@@ -29,7 +29,7 @@ REQUIRED_USE="
RDEPEND="
>=dev-libs/libpeas-1.14.1:0[gtk]
- >=app-editors/gedit-40.0
+ >=app-editors/pluma-1.25.3
>=dev-libs/glib-2.32:2
>=x11-libs/gtk+-3.9:3
@@ -38,7 +38,7 @@ RDEPEND="
python? (
${PYTHON_DEPS}
$(python_gen_cond_dep '
- app-editors/gedit[python,${PYTHON_SINGLE_USEDEP}]
+ app-editors/pluma[${PYTHON_SINGLE_USEDEP}]
dev-libs/libpeas:0[python,${PYTHON_SINGLE_USEDEP}]
>=dev-python/dbus-python-0.82[${PYTHON_USEDEP}]
dev-python/pycairo[${PYTHON_USEDEP}]
next reply other threads:[~2024-06-06 0:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 0:45 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-26 3:17 [gentoo-commits] repo/gentoo:master commit in: app-editors/pluma-plugins/ Sam James
2024-09-17 17:50 Andreas Sturmlechner
2024-08-01 0:27 Jakov Smolić
2024-08-01 0:27 Jakov Smolić
2024-06-16 6:06 Joonas Niilola
2024-06-16 6:06 Joonas Niilola
2024-06-06 0:45 Sam James
2024-06-06 0:45 Sam James
2024-06-06 0:45 Sam James
2023-10-29 22:23 Mart Raudsepp
2022-12-03 1:04 Sam James
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=1717634687.d0a1a621733dcbecb51b75c9418afda80583611c.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