From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/libintl-perl/
Date: Sat, 4 Mar 2023 08:34:36 +0000 (UTC) [thread overview]
Message-ID: <1677918867.1c526bd2c5976b7bc85985daf27bdefba4044d8c.arthurzam@gentoo> (raw)
commit: 1c526bd2c5976b7bc85985daf27bdefba4044d8c
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 4 08:34:27 2023 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Mar 4 08:34:27 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1c526bd2
dev-perl/libintl-perl: Stabilize 1.330.0 amd64, #899500
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
dev-perl/libintl-perl/libintl-perl-1.330.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-perl/libintl-perl/libintl-perl-1.330.0.ebuild b/dev-perl/libintl-perl/libintl-perl-1.330.0.ebuild
index 21da0d96e51c..568b7851edd7 100644
--- a/dev-perl/libintl-perl/libintl-perl-1.330.0.ebuild
+++ b/dev-perl/libintl-perl/libintl-perl-1.330.0.ebuild
@@ -13,7 +13,7 @@ HOMEPAGE="http://guido-flohr.net/projects/libintl-perl https://metacpan.org/rele
LICENSE="GPL-3"
SLOT="0"
-KEYWORDS="~alpha ~amd64 arm arm64 ~hppa ~ia64 ~loong ~m68k ~mips ppc ~ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~loong ~m68k ~mips ppc ~ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~x64-solaris ~x86-solaris"
IUSE="minimal"
RDEPEND="
next reply other threads:[~2023-03-04 8:34 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 8:34 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-05 7:16 [gentoo-commits] repo/gentoo:master commit in: dev-perl/libintl-perl/ Arthur Zamarin
2023-03-04 14:06 Arthur Zamarin
2023-03-04 7:04 Arthur Zamarin
2023-03-04 6:17 Arthur Zamarin
2023-03-04 6:14 Arthur Zamarin
2023-03-04 5:58 Arthur Zamarin
2023-03-04 5:35 Arthur Zamarin
2022-12-18 6:53 Sam James
2022-12-08 7:38 WANG Xuerui
2021-11-11 18:48 Andreas K. Hüttel
2021-08-26 19:51 Sam James
2021-08-26 14:55 Sam James
2021-08-26 14:52 Sam James
2021-08-26 14:49 Sam James
2021-08-26 3:00 Sam James
2021-08-25 16:26 Sam James
2021-07-11 20:15 Andreas K. Hüttel
2021-07-11 20:15 Andreas K. Hüttel
2020-07-21 20:27 Kent Fredric
2020-03-29 9:25 Sergei Trofimovich
2019-11-17 4:02 Matt Turner
2019-11-13 11:28 Agostino Sarubbo
2019-11-08 0:24 Aaron Bauman
2019-11-01 10:26 Mikle Kolyada
2019-10-21 19:21 Sergei Trofimovich
2019-10-21 12:16 Agostino Sarubbo
2019-10-21 12:12 Agostino Sarubbo
2019-10-21 12:09 Agostino Sarubbo
2019-10-21 12:08 Agostino Sarubbo
2019-10-20 14:25 Agostino Sarubbo
2019-10-18 10:25 Agostino Sarubbo
2019-07-19 7:49 Mikle Kolyada
2019-07-15 10:32 Kent Fredric
2019-05-04 19:20 Andreas K. Hüttel
2018-12-22 10:37 Mikle Kolyada
2018-12-08 15:22 Mikle Kolyada
2018-08-20 3:41 Mikle Kolyada
2018-07-23 0:33 Mikle Kolyada
2018-07-22 9:01 Sergei Trofimovich
2018-07-21 11:50 Tobias Klausmann
2018-07-20 23:18 Sergei Trofimovich
2018-07-20 22:48 Sergei Trofimovich
2018-07-20 8:08 Sergei Trofimovich
2018-07-16 6:54 Sergei Trofimovich
2018-07-15 23:57 Mikle Kolyada
2018-07-15 10:11 Mart Raudsepp
2018-06-02 14:18 Mike Frysinger
2018-04-01 19:46 Kent Fredric
2018-03-22 8:08 Mart Raudsepp
2018-03-11 5:20 Matt Turner
2017-06-30 7:37 Sergei Trofimovich
2017-06-25 7:24 Markus Meier
2017-06-21 11:57 Agostino Sarubbo
2017-06-20 14:56 Tobias Klausmann
2017-06-15 9:54 Agostino Sarubbo
2017-06-13 10:47 Agostino Sarubbo
2017-04-12 13:26 Michael Haubenwallner
2017-01-29 16:35 Fabian Groffen
2016-08-13 8:18 Jeroen Roovers
2016-05-26 0:20 Matt Turner
2016-03-29 20:45 Markus Meier
2016-03-19 11:35 Agostino Sarubbo
2016-03-14 22:12 Agostino Sarubbo
2016-03-11 23:50 Andreas Hüttel
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=1677918867.1c526bd2c5976b7bc85985daf27bdefba4044d8c.arthurzam@gentoo \
--to=arthurzam@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