From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-portage/unsymlink-lib/
Date: Thu, 20 Jun 2019 09:01:18 +0000 (UTC) [thread overview]
Message-ID: <1561021237.c19f9d3cd547171a3ae2b6a8c005b451f0beb4c3.zlogene@gentoo> (raw)
commit: c19f9d3cd547171a3ae2b6a8c005b451f0beb4c3
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Thu Jun 20 09:00:37 2019 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Thu Jun 20 09:00:37 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c19f9d3c
app-portage/unsymlink-lib: amd64 stable wrt bug #688164
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
Package-Manager: Portage-2.3.66, Repoman-2.3.11
RepoMan-Options: --include-arches="amd64"
app-portage/unsymlink-lib/unsymlink-lib-16.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-portage/unsymlink-lib/unsymlink-lib-16.ebuild b/app-portage/unsymlink-lib/unsymlink-lib-16.ebuild
index 90b56e60ca4..562293f6186 100644
--- a/app-portage/unsymlink-lib/unsymlink-lib-16.ebuild
+++ b/app-portage/unsymlink-lib/unsymlink-lib-16.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://github.com/mgorny/unsymlink-lib/archive/v${PV}.tar.gz -> ${P}.t
LICENSE="BSD-2"
SLOT="0"
-KEYWORDS="~amd64"
+KEYWORDS="amd64"
IUSE=""
REQUIRED_USE="${PYTHON_REQUIRED_USE}"
next reply other threads:[~2019-06-20 9:01 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 9:01 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-10 17:34 [gentoo-commits] repo/gentoo:master commit in: app-portage/unsymlink-lib/ Mike Gilbert
2024-01-10 17:33 Mike Gilbert
2023-01-21 6:53 Sam James
2022-08-10 14:20 Michał Górny
2022-08-08 14:48 Michał Górny
2022-07-31 16:08 Jakov Smolić
2021-12-29 13:00 Michał Górny
2021-07-08 3:46 Georgy Yakovlev
2021-03-05 16:31 Michał Górny
2021-03-05 15:02 Agostino Sarubbo
2021-01-18 14:55 Michał Górny
2020-12-17 17:09 Michał Górny
2020-11-10 8:24 Michał Górny
2020-11-09 22:08 Michał Górny
2020-09-20 3:01 Georgy Yakovlev
2020-09-18 9:38 Michał Górny
2020-06-29 15:53 Michał Górny
2020-05-26 3:10 Mike Gilbert
2020-02-10 11:54 Michał Górny
2019-09-08 6:43 Michał Górny
2019-07-29 14:21 Mikle Kolyada
2019-07-28 6:41 Michał Górny
2019-06-20 7:01 Michał Górny
2019-06-16 17:35 Michał Górny
2019-06-16 17:35 Michał Górny
2019-06-09 20:24 Mikle Kolyada
2019-06-07 18:30 Michał Górny
2019-05-23 14:32 Michał Górny
2019-05-18 10:02 Michał Górny
2018-09-11 8:18 Michał Górny
2018-09-07 14:26 Mikle Kolyada
2018-05-31 20:44 Michał Górny
2018-03-21 18:12 Michał Górny
2018-02-22 9:05 Agostino Sarubbo
2018-02-05 20:45 Michał Górny
2018-01-10 14:50 Michał Górny
2018-01-10 9:31 Michał Górny
2018-01-09 17:19 Michał Górny
2018-01-09 17:19 Michał Górny
2018-01-04 17:51 Michał Górny
2017-12-29 23:34 Michał Górny
2017-12-29 23:34 Michał Górny
2017-12-29 16:04 Michał Górny
2017-12-29 16:04 Michał Górny
2017-12-20 20:58 Michał Górny
2017-12-19 17:16 Michał Górny
2017-12-18 23:14 Michał Górny
2017-12-18 23:14 Michał Górny
2017-12-18 15:36 Michał Górny
2017-12-18 15:36 Michał Górny
2017-12-09 10:01 Michał Górny
2017-12-08 18:07 Michał Górny
2017-12-07 17:01 Michał Górny
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=1561021237.c19f9d3cd547171a3ae2b6a8c005b451f0beb4c3.zlogene@gentoo \
--to=zlogene@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