From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-power/nut/
Date: Tue, 6 Feb 2024 06:47:37 +0000 (UTC) [thread overview]
Message-ID: <1707202030.c6fbcbcb1d594f0c74f0781bd5473167dfd4a976.sam@gentoo> (raw)
commit: c6fbcbcb1d594f0c74f0781bd5473167dfd4a976
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Feb 6 06:47:10 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Feb 6 06:47:10 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c6fbcbcb
sys-power/nut: Stabilize 2.8.0-r3 ppc64, #923861
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-power/nut/nut-2.8.0-r3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-power/nut/nut-2.8.0-r3.ebuild b/sys-power/nut/nut-2.8.0-r3.ebuild
index 651720bb40ac..e715c0a515da 100644
--- a/sys-power/nut/nut-2.8.0-r3.ebuild
+++ b/sys-power/nut/nut-2.8.0-r3.ebuild
@@ -16,7 +16,7 @@ if [[ ${PV} == *9999 ]] ; then
inherit git-r3
else
SRC_URI="https://networkupstools.org/source/${PV%.*}/${MY_P}.tar.gz"
- KEYWORDS="amd64 ~arm ~arm64 ~ppc ~ppc64 ~riscv x86"
+ KEYWORDS="amd64 ~arm ~arm64 ~ppc ppc64 ~riscv x86"
fi
S="${WORKDIR}/${MY_P}"
next reply other threads:[~2024-02-06 6:47 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 6:47 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-12 11:22 [gentoo-commits] repo/gentoo:master commit in: sys-power/nut/ Michał Górny
2024-10-12 10:08 Michał Górny
2024-10-12 7:52 Michał Górny
2024-05-29 18:27 Robin H. Johnson
2024-05-27 21:08 Robin H. Johnson
2024-05-27 21:08 Robin H. Johnson
2024-02-06 6:54 Sam James
2024-02-06 6:25 Sam James
2024-02-06 6:25 Sam James
2024-01-17 2:46 Ionen Wolkens
2024-01-01 0:12 Sam James
2023-12-18 13:36 Joonas Niilola
2023-12-18 1:09 Sam James
2023-12-18 0:11 Sam James
2023-12-11 13:04 Joonas Niilola
2023-08-09 3:34 Sam James
2023-06-24 1:18 Sam James
2023-06-17 17:11 Arthur Zamarin
2023-06-17 17:11 Arthur Zamarin
2023-06-17 15:48 Arthur Zamarin
2023-06-17 10:33 Yixun Lan
2023-06-17 3:56 Sam James
2023-06-17 3:55 Sam James
2023-06-17 3:19 Sam James
2022-06-21 18:21 Arthur Zamarin
2021-09-21 21:57 Marek Szuba
2021-08-18 14:28 Sam James
2021-08-04 19:37 Sam James
2021-07-09 22:36 Conrad Kostecki
2021-07-09 22:36 Conrad Kostecki
2020-08-30 1:17 Sam James
2020-08-22 15:51 Michał Górny
2020-08-11 18:46 Sam James
2020-08-10 14:33 Agostino Sarubbo
2020-08-07 18:51 Sam James
2020-02-19 18:24 Robin H. Johnson
2020-02-09 16:42 Michał Górny
2020-01-08 22:27 David Seifert
2020-01-08 22:27 David Seifert
2019-08-20 11:47 Louis Sautier
2019-08-13 12:10 Michał Górny
2019-07-29 10:45 Mikle Kolyada
2019-07-02 8:28 Sergei Trofimovich
2019-07-02 8:24 Sergei Trofimovich
2019-06-29 13:03 Agostino Sarubbo
2019-06-28 15:21 Agostino Sarubbo
2018-11-18 15:27 Thomas Deutschmann
2018-11-14 18:23 Robin H. Johnson
2018-10-27 19:02 Andreas Sturmlechner
2018-03-15 16:13 Mikle Kolyada
2018-01-15 19:03 Tobias Klausmann
2018-01-08 22:50 Thomas Deutschmann
2018-01-08 22:24 Sergei Trofimovich
2017-12-08 22:34 Matt Thode
2017-11-26 23:26 David Seifert
2017-03-21 12:57 Michael Weber
2016-12-20 18:21 Thomas Deutschmann
2016-12-20 17:31 Tobias Klausmann
2016-10-02 12:37 Pacho Ramos
2016-03-18 19:11 Michał Górny
2015-09-03 4:53 Matt Thode
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=1707202030.c6fbcbcb1d594f0c74f0781bd5473167dfd4a976.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