From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/accountsservice/
Date: Fri, 18 Sep 2020 06:48:40 +0000 (UTC) [thread overview]
Message-ID: <1600411605.3b4728c7c3ff98624be7edf278cfce6fb99e41d4.slyfox@gentoo> (raw)
commit: 3b4728c7c3ff98624be7edf278cfce6fb99e41d4
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Fri Sep 18 06:46:45 2020 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Fri Sep 18 06:46:45 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3b4728c7
sys-apps/accountsservice: stable 0.6.55 for ppc
stable wrt bug #
Tested-by: ernsteiswuerfel
Package-Manager: Portage-3.0.7, Repoman-3.0.1
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
sys-apps/accountsservice/accountsservice-0.6.55.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-apps/accountsservice/accountsservice-0.6.55.ebuild b/sys-apps/accountsservice/accountsservice-0.6.55.ebuild
index 594f51a3a77..13cdbe016d6 100644
--- a/sys-apps/accountsservice/accountsservice-0.6.55.ebuild
+++ b/sys-apps/accountsservice/accountsservice-0.6.55.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://www.freedesktop.org/software/${PN}/${P}.tar.xz"
LICENSE="GPL-3+"
SLOT="0"
-KEYWORDS="~alpha amd64 arm arm64 ~ia64 ~ppc ~ppc64 ~sparc x86"
+KEYWORDS="~alpha amd64 arm arm64 ~ia64 ppc ~ppc64 ~sparc x86"
IUSE="doc consolekit elogind gtk-doc +introspection selinux systemd"
REQUIRED_USE="^^ ( consolekit elogind systemd )"
next reply other threads:[~2020-09-18 6:48 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 6:48 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-15 16:21 [gentoo-commits] repo/gentoo:master commit in: sys-apps/accountsservice/ Mike Gilbert
2023-05-03 7:04 Arthur Zamarin
2023-05-03 7:04 Arthur Zamarin
2023-05-03 7:04 Arthur Zamarin
2023-05-03 7:03 Arthur Zamarin
2023-05-03 4:45 Sam James
2023-05-02 17:35 Sam James
2023-03-28 20:50 David Seifert
2023-03-28 16:08 Matt Turner
2023-03-01 22:36 Maciej Mrozowski
2022-10-29 17:44 Matt Turner
2022-08-11 9:49 Sam James
2022-05-31 18:24 Matt Turner
2022-05-31 9:24 Jakov Smolić
2022-05-28 5:05 Sam James
2022-03-18 19:24 Matt Turner
2022-03-09 15:39 Sam James
2022-03-09 12:49 Sam James
2022-03-08 12:32 Sam James
2022-03-01 20:37 Matt Turner
2022-02-20 0:37 Sam James
2022-02-18 22:49 Matt Turner
2021-07-26 7:40 Yixun Lan
2020-10-06 19:22 Mikle Kolyada
2020-09-18 7:44 Sergei Trofimovich
2020-06-29 15:42 Mikle Kolyada
2020-06-28 20:30 Agostino Sarubbo
2020-06-28 14:19 Thomas Deutschmann
2020-06-26 21:16 Mart Raudsepp
2020-06-13 15:27 Pacho Ramos
2019-05-28 2:35 Aaron Bauman
2019-04-21 18:24 Andreas Sturmlechner
2019-03-04 20:45 Mart Raudsepp
2019-03-04 19:52 Dennis Lamm
2018-11-18 11:50 Mikle Kolyada
2018-10-14 9:14 Sergei Trofimovich
2018-10-14 8:59 Sergei Trofimovich
2018-10-05 8:53 Mikle Kolyada
2018-08-22 5:00 Markus Meier
2018-08-21 0:13 Sergei Trofimovich
2018-08-19 1:40 Mikle Kolyada
2018-08-18 22:31 Sergei Trofimovich
2018-08-17 0:12 Mart Raudsepp
2017-12-27 13:02 Mart Raudsepp
2017-12-27 8:35 Markus Meier
2017-12-19 19:14 Thomas Deutschmann
2017-12-16 14:04 Tobias Klausmann
2017-11-18 13:20 Sergei Trofimovich
2017-10-30 17:06 Mart Raudsepp
2017-10-30 8:42 Sergei Trofimovich
2017-10-24 21:45 Sergei Trofimovich
2017-09-23 21:13 Thomas Deutschmann
2017-08-20 10:14 Gilles Dartiguelongue
2017-07-20 4:42 Markus Meier
2017-07-15 11:04 Tobias Klausmann
2017-02-24 23:04 Mart Raudsepp
2017-02-24 21:29 Michael Weber
2017-02-24 14:07 Agostino Sarubbo
2017-02-11 18:31 Pacho Ramos
2017-01-26 10:56 Mart Raudsepp
2016-12-06 20:47 Markus Meier
2016-12-05 13:52 Pacho Ramos
2016-06-28 20:30 Pacho Ramos
2016-06-28 20:30 Pacho Ramos
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=1600411605.3b4728c7c3ff98624be7edf278cfce6fb99e41d4.slyfox@gentoo \
--to=slyfox@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