From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-news/liferea/
Date: Wed, 3 May 2023 10:18:00 +0000 (UTC) [thread overview]
Message-ID: <1683109061.b898e984767b04f306a84179b04c9a3fede76589.arthurzam@gentoo> (raw)
commit: b898e984767b04f306a84179b04c9a3fede76589
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Wed May 3 10:17:41 2023 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Wed May 3 10:17:41 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b898e984
net-news/liferea: Stabilize 1.12.10-r1 amd64, #905617
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
net-news/liferea/liferea-1.12.10-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-news/liferea/liferea-1.12.10-r1.ebuild b/net-news/liferea/liferea-1.12.10-r1.ebuild
index 2c852f85327e..515dc67f6044 100644
--- a/net-news/liferea/liferea-1.12.10-r1.ebuild
+++ b/net-news/liferea/liferea-1.12.10-r1.ebuild
@@ -13,7 +13,7 @@ SRC_URI="https://github.com/lwindolf/${PN}/releases/download/v${PV}/${P}.tar.bz2
LICENSE="GPL-2+"
SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~ppc64 x86"
+KEYWORDS="amd64 ~arm ~arm64 ~ppc64 x86"
IUSE=""
REQUIRED_USE="${PYTHON_REQUIRED_USE}"
next reply other threads:[~2023-05-03 10:27 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 10:18 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-05 22:56 [gentoo-commits] repo/gentoo:master commit in: net-news/liferea/ James Le Cuirot
2024-10-05 22:56 James Le Cuirot
2024-03-18 20:00 Conrad Kostecki
2024-03-18 20:00 Conrad Kostecki
2024-02-02 9:13 Joonas Niilola
2024-02-02 9:13 Joonas Niilola
2024-01-30 19:29 Sam James
2024-01-20 12:23 Sam James
2024-01-20 12:23 Sam James
2023-12-16 9:46 Pacho Ramos
2023-12-16 9:46 Pacho Ramos
2023-12-16 9:46 Pacho Ramos
2023-12-16 9:46 Pacho Ramos
2023-10-29 22:23 Mart Raudsepp
2023-09-16 14:10 Matt Turner
2023-07-11 8:00 Joonas Niilola
2023-07-11 8:00 Joonas Niilola
2023-05-03 6:33 Arthur Zamarin
2023-04-26 4:03 Sam James
2023-04-19 4:26 John Helmert III
2023-04-14 1:06 Sam James
2023-04-14 1:06 Sam James
2023-04-05 20:54 Georgy Yakovlev
2023-04-05 20:54 Georgy Yakovlev
2023-03-17 9:02 Arthur Zamarin
2023-03-15 13:50 Arthur Zamarin
2023-03-15 5:00 Sam James
2023-03-15 5:00 Sam James
2023-02-05 8:30 Joonas Niilola
2023-02-05 8:30 Joonas Niilola
2022-11-14 14:31 Joonas Niilola
2022-11-14 14:31 Joonas Niilola
2022-11-14 14:31 Joonas Niilola
2022-04-25 11:56 Joonas Niilola
2022-04-25 11:56 Joonas Niilola
2022-01-13 2:00 Georgy Yakovlev
2021-10-31 2:48 Sam James
2021-08-15 21:06 Andreas Sturmlechner
2021-06-04 2:14 Georgy Yakovlev
2021-04-20 7:37 Michał Górny
2021-02-27 16:48 Sam James
2021-02-25 13:54 Agostino Sarubbo
2020-09-30 7:54 Joonas Niilola
2020-09-30 7:54 Joonas Niilola
2020-09-30 7:54 Joonas Niilola
2020-07-01 6:39 Joonas Niilola
2020-07-01 6:39 Joonas Niilola
2020-07-01 6:39 Joonas Niilola
2020-03-16 9:16 Michał Górny
2020-02-09 16:34 Michał Górny
2020-01-13 8:50 Agostino Sarubbo
2020-01-11 14:15 Agostino Sarubbo
2020-01-06 14:04 Michał Górny
2020-01-06 14:04 Michał Górny
2019-08-09 18:05 Joonas Niilola
2019-02-03 22:57 Andreas Sturmlechner
2018-11-06 8:56 Michał Górny
2018-07-24 12:45 Michał Górny
2018-06-24 13:09 Jason Zaman
2018-05-12 19:22 Michał Górny
2018-03-23 22:58 Michał Górny
2018-01-25 22:52 Patrice Clement
2017-06-02 8:47 Pacho Ramos
2017-04-27 10:36 Agostino Sarubbo
2017-04-23 21:23 Agostino Sarubbo
2017-04-23 21:01 David Seifert
2017-04-17 16:49 David Seifert
2017-04-07 23:05 Göktürk Yüksek
2017-02-06 14:55 Agostino Sarubbo
2016-12-29 1:45 Sam Jorna
2016-12-22 19:31 Göktürk Yüksek
2016-11-20 16:56 Göktürk Yüksek
2016-10-09 12:02 Pacho Ramos
2016-08-07 6:31 Pacho Ramos
2016-01-03 3:34 Victor Ostorga
2015-12-12 14:21 Victor Ostorga
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=1683109061.b898e984767b04f306a84179b04c9a3fede76589.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