From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-admin/keepass/
Date: Sat, 18 Feb 2017 13:29:01 +0000 (UTC) [thread overview]
Message-ID: <1487424527.57b2dfe3c622a9c4d88283f1c0baa4f72b5c45bb.ago@gentoo> (raw)
commit: 57b2dfe3c622a9c4d88283f1c0baa4f72b5c45bb
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Sat Feb 18 13:28:47 2017 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Sat Feb 18 13:28:47 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=57b2dfe3
app-admin/keepass: amd64 stable wrt bug #609634
Package-Manager: portage-2.3.3
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
app-admin/keepass/keepass-2.35-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-admin/keepass/keepass-2.35-r1.ebuild b/app-admin/keepass/keepass-2.35-r1.ebuild
index 3fbf36b7ad..5b0a5a9743 100644
--- a/app-admin/keepass/keepass-2.35-r1.ebuild
+++ b/app-admin/keepass/keepass-2.35-r1.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://sourceforge/${PN}/${MY_PN}-${PV}-Source.zip"
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
IUSE="aot"
COMMON_DEPEND="dev-lang/mono"
next reply other threads:[~2017-02-18 13:29 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 13:29 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-01 6:13 [gentoo-commits] repo/gentoo:master commit in: app-admin/keepass/ Joonas Niilola
2024-09-01 6:13 Joonas Niilola
2024-07-01 8:17 Matt Jolly
2024-03-01 0:20 Yixun Lan
2023-09-28 4:35 Sam James
2023-09-27 13:29 Arthur Zamarin
2023-07-16 18:46 Sam James
2023-05-27 10:51 Arthur Zamarin
2022-07-24 1:00 Matt Turner
2021-12-02 6:46 Michael Palimaka
2021-12-02 6:46 Michael Palimaka
2021-11-04 0:42 Jakov Smolić
2021-10-28 6:22 Sam James
2021-09-20 8:48 Michael Palimaka
2021-09-20 8:48 Michael Palimaka
2021-05-27 8:35 Michael Palimaka
2021-04-20 11:49 Michael Palimaka
2021-02-24 7:28 Michael Palimaka
2020-11-17 10:29 Michael Palimaka
2020-11-12 12:28 Sam James
2020-10-30 22:32 Thomas Deutschmann
2020-09-18 9:38 Michael Palimaka
2020-06-28 20:56 Thomas Deutschmann
2020-05-11 11:24 Michael Palimaka
2020-03-28 3:06 Michael Palimaka
2020-03-27 16:31 Agostino Sarubbo
2020-03-22 8:46 Mikle Kolyada
2020-02-10 11:12 Michael Palimaka
2020-02-10 11:01 Michael Palimaka
2020-01-21 10:42 Agostino Sarubbo
2020-01-20 13:04 Agostino Sarubbo
2019-11-05 6:21 Michael Palimaka
2019-09-23 8:46 Michael Palimaka
2019-08-06 11:27 Michael Palimaka
2019-08-06 10:40 Agostino Sarubbo
2019-08-06 9:39 Agostino Sarubbo
2019-05-08 11:03 Michael Palimaka
2019-02-28 12:45 Michael Palimaka
2019-02-28 12:45 Michael Palimaka
2019-01-10 11:18 Manuel Rüger
2018-11-17 7:24 Michael Palimaka
2018-11-17 7:24 Michael Palimaka
2018-11-08 13:22 Michael Palimaka
2018-10-06 10:32 Michael Palimaka
2018-09-16 14:34 Manuel Rüger
2018-05-26 1:10 Manuel Rüger
2018-02-25 6:55 Michael Palimaka
2018-02-25 6:55 Michael Palimaka
2018-01-12 9:17 Michael Palimaka
2018-01-11 7:30 Michael Palimaka
2017-12-16 12:08 Michael Palimaka
2017-12-16 12:08 Michael Palimaka
2017-10-14 2:42 Michael Palimaka
2017-09-04 16:01 Jonathan Vasquez
2017-07-23 2:08 Michael Palimaka
2017-06-11 15:14 Jonathan Vasquez
2017-02-18 14:33 Agostino Sarubbo
2017-01-10 5:49 Jonathan Vasquez
2016-12-18 1:04 Matt Thode
2016-07-17 19:16 Michael Palimaka
2016-07-09 17:46 Agostino Sarubbo
2016-06-11 18:09 Michael Palimaka
2016-05-13 22:06 Manuel Rüger
2016-05-13 8:41 Agostino Sarubbo
2016-04-04 9:00 Ian Delaney
2016-03-10 22:37 Manuel Rüger
2016-01-18 11:14 Michael Palimaka
2016-01-17 15:35 Manuel Rüger
2015-12-03 12:06 Michael Palimaka
2015-12-03 10:41 Agostino Sarubbo
2015-11-19 10:44 Agostino Sarubbo
2015-08-19 10:52 Michael Palimaka
2015-08-19 10:52 Michael Palimaka
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=1487424527.57b2dfe3c622a9c4d88283f1c0baa4f72b5c45bb.ago@gentoo \
--to=ago@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