From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/perl-Math-BigRat/
Date: Tue, 27 Dec 2022 23:46:38 +0000 (UTC) [thread overview]
Message-ID: <1672184744.f185ae9442493ba789abdde9589a4b0f5138632a.sam@gentoo> (raw)
commit: f185ae9442493ba789abdde9589a4b0f5138632a
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 27 23:45:44 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Dec 27 23:45:44 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f185ae94
virtual/perl-Math-BigRat: Stabilize 0.262.100 sparc, #865895
Signed-off-by: Sam James <sam <AT> gentoo.org>
virtual/perl-Math-BigRat/perl-Math-BigRat-0.262.100.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/virtual/perl-Math-BigRat/perl-Math-BigRat-0.262.100.ebuild b/virtual/perl-Math-BigRat/perl-Math-BigRat-0.262.100.ebuild
index 135815519a29..1ed849608721 100644
--- a/virtual/perl-Math-BigRat/perl-Math-BigRat-0.262.100.ebuild
+++ b/virtual/perl-Math-BigRat/perl-Math-BigRat-0.262.100.ebuild
@@ -5,7 +5,7 @@ EAPI=8
DESCRIPTION="Virtual for ${PN#perl-}"
SLOT="0"
-KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 ~sparc x86 ~x64-cygwin ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc x86 ~x64-cygwin ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
RDEPEND="
|| ( =dev-lang/perl-5.36* ~perl-core/${PN#perl-}-${PV} )
next reply other threads:[~2022-12-27 23:46 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 23:46 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-22 13:53 [gentoo-commits] repo/gentoo:master commit in: virtual/perl-Math-BigRat/ Sam James
2024-08-31 8:04 Arthur Zamarin
2024-08-29 1:33 Sam James
2024-05-25 21:56 Andreas K. Hüttel
2024-03-15 14:57 Matt Turner
2023-09-02 15:34 Sam James
2023-09-02 8:53 Sam James
2023-09-01 19:56 Arthur Zamarin
2023-09-01 19:33 Arthur Zamarin
2023-09-01 17:24 Arthur Zamarin
2023-09-01 14:23 Sam James
2023-08-16 21:04 Andreas K. Hüttel
2023-06-03 14:19 Andreas K. Hüttel
2022-12-27 19:55 Sam James
2022-12-18 6:43 Sam James
2022-12-18 6:34 Sam James
2022-12-18 1:14 Sam James
2022-05-25 1:09 Andreas K. Hüttel
2021-05-20 1:18 Andreas K. Hüttel
2021-02-03 2:31 Sam James
2020-08-06 20:22 Andreas K. Hüttel
2019-12-07 16:55 Aaron Bauman
2019-12-06 10:00 Mikle Kolyada
2019-12-06 9:53 Mikle Kolyada
2019-12-06 9:51 Mikle Kolyada
2019-12-06 9:49 Mikle Kolyada
2019-12-06 9:46 Mikle Kolyada
2019-12-06 9:43 Mikle Kolyada
2019-12-06 9:40 Mikle Kolyada
2019-12-06 9:37 Mikle Kolyada
2019-12-06 9:34 Mikle Kolyada
2019-09-10 0:40 Matt Turner
2019-05-26 0:28 Aaron Bauman
2019-05-24 14:37 Mikle Kolyada
2019-05-24 8:12 Mikle Kolyada
2019-05-24 6:54 Mikle Kolyada
2019-05-24 6:42 Mikle Kolyada
2019-05-24 6:39 Mikle Kolyada
2019-05-24 6:35 Mikle Kolyada
2019-05-16 23:24 Andreas K. Hüttel
2019-01-08 22:01 Mart Raudsepp
2018-11-22 12:07 Kent Fredric
2018-10-25 19:03 Fabian Groffen
2018-09-01 7:20 Kent Fredric
2018-09-01 6:06 Kent Fredric
2016-05-19 18:53 Markus Meier
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=1672184744.f185ae9442493ba789abdde9589a4b0f5138632a.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