public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-auth/fprintd/
Date: Wed,  5 Jun 2019 18:14:12 +0000 (UTC)	[thread overview]
Message-ID: <1559758441.7aa6e7312206ccd2429414951bcbb37d33dee23c.slyfox@gentoo> (raw)

commit:     7aa6e7312206ccd2429414951bcbb37d33dee23c
Author:     Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Wed Jun  5 17:48:38 2019 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Wed Jun  5 18:14:01 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7aa6e731

sys-auth/fprintd: stable 0.8.1 for sparc, bug #684570

Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
Package-Manager: Portage-2.3.66, Repoman-2.3.11
RepoMan-Options: --include-arches="sparc"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>

 sys-auth/fprintd/fprintd-0.8.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-auth/fprintd/fprintd-0.8.1.ebuild b/sys-auth/fprintd/fprintd-0.8.1.ebuild
index 3fd50169aab..fd503fe138a 100644
--- a/sys-auth/fprintd/fprintd-0.8.1.ebuild
+++ b/sys-auth/fprintd/fprintd-0.8.1.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://cgit.freedesktop.org/libfprint/${PN}/snapshot/${MY_PV}.tar.bz2
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~ia64 ~ppc ~ppc64 ~sparc x86"
+KEYWORDS="~alpha ~amd64 ~arm ~ia64 ~ppc ~ppc64 sparc x86"
 IUSE="doc pam static-libs"
 
 RDEPEND="


             reply	other threads:[~2019-06-05 18:14 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05 18:14 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-03  5:53 [gentoo-commits] repo/gentoo:master commit in: sys-auth/fprintd/ Sam James
2023-07-27  5:11 WANG Xuerui
2023-06-28  7:37 Sam James
2023-02-24 16:29 Arthur Zamarin
2023-02-24 16:29 Arthur Zamarin
2023-02-24 16:29 Arthur Zamarin
2023-02-24 16:29 Arthur Zamarin
2023-02-24 16:29 Arthur Zamarin
2023-02-24 16:29 Arthur Zamarin
2023-02-24 16:29 Arthur Zamarin
2022-12-28  0:56 Sam James
2022-12-27 23:37 Sam James
2022-12-27 23:37 Sam James
2022-11-18 19:42 Arthur Zamarin
2022-11-18 19:24 Arthur Zamarin
2022-09-22  7:46 Michał Górny
2022-07-30 19:57 Arthur Zamarin
2022-04-29 10:21 Sam James
2022-04-17 19:17 Sam James
2022-04-17 18:36 Arthur Zamarin
2022-04-17 18:36 Arthur Zamarin
2022-04-17 18:36 Arthur Zamarin
2022-04-11 21:05 Jakov Smolić
2022-04-06  6:32 Agostino Sarubbo
2022-04-06  6:32 Agostino Sarubbo
2022-01-04 15:33 Marek Szuba
2021-12-10  1:24 Sam James
2021-12-02  8:29 Agostino Sarubbo
2021-12-02  8:24 Agostino Sarubbo
2021-11-19 20:01 Arthur Zamarin
2021-11-04 17:07 Sam James
2021-10-20  9:46 Sam James
2021-10-20  9:46 Sam James
2021-10-20  3:26 Sam James
2021-08-27 15:19 Yixun Lan
2021-07-25  1:10 Sam James
2021-07-24 15:22 Sam James
2021-04-02  9:23 Sergei Trofimovich
2021-03-26  7:45 Agostino Sarubbo
2021-03-25 18:12 Agostino Sarubbo
2021-03-25 13:02 Joonas Niilola
2021-03-25 13:02 Joonas Niilola
2021-03-25 13:02 Joonas Niilola
2021-03-15 18:06 Sergei Trofimovich
2021-03-15  6:32 Sam James
2021-03-14 22:11 Sam James
2021-03-14 22:11 Sam James
2021-03-13 11:37 Sam James
2021-03-13 11:35 Sam James
2021-03-04  0:23 Sam James
2021-02-11  7:36 Sergei Trofimovich
2021-01-05 22:00 Matt Turner
2019-08-04 19:36 Maxim Koltsov
2019-08-04 19:36 Maxim Koltsov
2019-08-03 11:19 Aaron Bauman
2019-07-29 14:53 Mikle Kolyada
2019-07-29 14:53 Mikle Kolyada
2019-06-20  9:23 Mikle Kolyada
2019-06-09 19:25 Sergei Trofimovich
2019-06-06 21:31 Sergei Trofimovich
2019-06-06 21:24 Sergei Trofimovich
2019-01-18 18:01 Mikle Kolyada
2019-01-08 14:07 Maxim Koltsov
2018-05-21 16:25 Mikle Kolyada
2015-08-09 22:33 Michael Weber
2015-08-09 22:16 Michael Weber

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=1559758441.7aa6e7312206ccd2429414951bcbb37d33dee23c.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