From: "Alfredo Tupone" <tupone@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ml/lablgtk/
Date: Tue, 6 Dec 2022 21:27:35 +0000 (UTC) [thread overview]
Message-ID: <1670362033.7f73d0abc5523b8cfffc10c82d2fd6c273bc3726.tupone@gentoo> (raw)
commit: 7f73d0abc5523b8cfffc10c82d2fd6c273bc3726
Author: Petr Vaněk <arkamar <AT> atlas <DOT> cz>
AuthorDate: Tue Dec 6 21:13:13 2022 +0000
Commit: Alfredo Tupone <tupone <AT> gentoo <DOT> org>
CommitDate: Tue Dec 6 21:27:13 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7f73d0ab
dev-ml/lablgtk: fix typo in restriction
This fixes accidental typo in flag restriction from previous commit.
Fixes: 32aeb34cdae5 ("dev-ml/lablgtk: Improve use flag metadata section")
Signed-off-by: Petr Vaněk <arkamar <AT> atlas.cz>
Closes: https://github.com/gentoo/gentoo/pull/28576
Signed-off-by: Alfredo Tupone <tupone <AT> gentoo.org>
dev-ml/lablgtk/metadata.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-ml/lablgtk/metadata.xml b/dev-ml/lablgtk/metadata.xml
index 4d3ab587ee41..437ccb8ea1e5 100644
--- a/dev-ml/lablgtk/metadata.xml
+++ b/dev-ml/lablgtk/metadata.xml
@@ -10,10 +10,10 @@
<name>Mark Wright</name>
</maintainer>
<use>
- <flag name="glade" restrict="<dev-ml/lablgtki-3">
+ <flag name="glade" restrict="<dev-ml/lablgtk-3">
Enable <pkg>gnome-base/libglade</pkg> bindings compilation
</flag>
- <flag name="gnomecanvas" restrict="<dev-ml/lablgtki-3">
+ <flag name="gnomecanvas" restrict="<dev-ml/lablgtk-3">
Enable <pkg>gnome-base/libgnomecanvas</pkg> bindings compilation
</flag>
<flag name="sourceview">
next reply other threads:[~2022-12-06 21:27 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 21:27 Alfredo Tupone [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-16 12:07 [gentoo-commits] repo/gentoo:master commit in: dev-ml/lablgtk/ Alfredo Tupone
2024-11-12 9:18 Alfredo Tupone
2024-10-15 15:25 Arthur Zamarin
2024-06-26 19:22 Alfredo Tupone
2024-06-26 8:31 Alfredo Tupone
2024-06-06 19:24 Alfredo Tupone
2023-04-09 13:08 Arthur Zamarin
2023-04-09 12:47 Arthur Zamarin
2023-04-09 12:41 Arthur Zamarin
2023-04-01 19:52 Sam James
2023-03-17 16:51 Arthur Zamarin
2023-03-17 10:03 Arthur Zamarin
2023-03-16 23:16 Sam James
2023-03-16 23:16 Sam James
2023-02-15 18:38 Matt Turner
2023-01-27 22:00 Alfredo Tupone
2023-01-20 20:12 Alfredo Tupone
2022-12-06 9:25 Sam James
2022-12-05 13:28 Alfredo Tupone
2022-09-05 22:09 Maciej Barć
2021-03-14 0:48 Sam James
2021-02-21 10:17 Andreas Sturmlechner
2021-02-21 10:17 Andreas Sturmlechner
2021-02-19 21:13 Alfredo Tupone
2021-01-27 19:30 Alfredo Tupone
2021-01-14 6:42 Alfredo Tupone
2020-11-01 11:38 Sam James
2020-10-28 3:36 Sam James
2020-10-24 0:38 Sam James
2020-10-22 13:59 Sam James
2020-10-22 13:59 Sam James
2020-10-22 12:13 Sam James
2020-09-20 20:21 Agostino Sarubbo
2020-09-09 18:35 Alfredo Tupone
2020-09-07 8:47 Sergei Trofimovich
2020-06-21 20:31 Thomas Deutschmann
2020-03-23 17:41 Alfredo Tupone
2020-03-20 20:06 David Seifert
2020-02-17 20:26 Alfredo Tupone
2020-02-17 20:26 Alfredo Tupone
2020-01-31 13:05 Joonas Niilola
2020-01-31 13:05 Joonas Niilola
2020-01-07 21:01 Jason A. Donenfeld
2017-11-04 9:53 Alexis Ballier
2017-11-04 9:53 Alexis Ballier
2017-04-05 17:50 Markus Meier
2017-01-22 17:54 Alexis Ballier
2017-01-22 16:36 Tobias Klausmann
2017-01-14 17:57 Mikle Kolyada
2017-01-08 10:50 Aaron Bauman
2016-12-27 1:16 Aaron Bauman
2016-08-12 12:53 Alexis Ballier
2016-07-05 9:43 Tobias Klausmann
2016-06-29 21:14 Michał Górny
2016-06-24 9:57 Alexis Ballier
2016-04-30 14:18 Alexis Ballier
2016-04-30 14:18 Alexis Ballier
2016-01-11 9:07 Agostino Sarubbo
2016-01-09 6:43 Agostino Sarubbo
2015-12-07 11:40 Agostino Sarubbo
2015-12-03 13:28 Agostino Sarubbo
2015-11-25 8:54 Agostino Sarubbo
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=1670362033.7f73d0abc5523b8cfffc10c82d2fd6c273bc3726.tupone@gentoo \
--to=tupone@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