From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-arch/lzlib/
Date: Tue, 17 Aug 2021 01:42:35 +0000 (UTC) [thread overview]
Message-ID: <1629164531.0418f09ef7e55a1f5e5cd3c0a60c059c1c47f1e4.sam@gentoo> (raw)
commit: 0418f09ef7e55a1f5e5cd3c0a60c059c1c47f1e4
Author: Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Mon Aug 16 18:29:50 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Aug 17 01:42:11 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0418f09e
app-arch/lzlib: keyworded 1.12 for hppa, bug #807361
Package-Manager: Portage-3.0.20, Repoman-3.0.3
RepoMan-Options: --include-arches="hppa"
Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-arch/lzlib/lzlib-1.12.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-arch/lzlib/lzlib-1.12.ebuild b/app-arch/lzlib/lzlib-1.12.ebuild
index 8e1e156784e..332557d77ff 100644
--- a/app-arch/lzlib/lzlib-1.12.ebuild
+++ b/app-arch/lzlib/lzlib-1.12.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://download.savannah.gnu.org/releases/lzip/${PN}/${P}.tar.gz"
LICENSE="libstdc++" # fancy form of GPL-2+ with library exception
SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~ppc ~ppc64 ~x86"
+KEYWORDS="~amd64 ~arm64 ~hppa ~ppc ~ppc64 ~x86"
IUSE=""
src_configure() {
next reply other threads:[~2021-08-17 1:42 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 1:42 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-24 8:49 [gentoo-commits] repo/gentoo:master commit in: app-arch/lzlib/ Michał Górny
2024-02-24 2:44 Ionen Wolkens
2024-02-09 1:04 Sam James
2024-02-08 15:28 Michał Górny
2024-02-08 15:28 Michał Górny
2024-02-08 15:28 Michał Górny
2024-02-08 14:43 Michał Górny
2024-02-08 14:43 Michał Górny
2024-02-08 14:43 Michał Górny
2024-01-25 11:37 Michał Górny
2024-01-25 5:48 Sam James
2024-01-25 3:14 Sam James
2024-01-25 0:42 Sam James
2024-01-24 19:21 Michał Górny
2024-01-24 19:21 Michał Górny
2024-01-24 19:05 Michał Górny
2024-01-24 19:05 Michał Górny
2024-01-24 18:59 Michał Górny
2024-01-23 18:13 Michał Górny
2024-01-07 0:20 Conrad Kostecki
2023-06-18 1:07 Sam James
2023-03-19 17:36 Arthur Zamarin
2023-01-13 6:18 Sam James
2023-01-13 5:40 Sam James
2023-01-12 4:41 Sam James
2022-12-31 10:49 Arthur Zamarin
2022-12-27 14:23 Arthur Zamarin
2022-12-27 13:13 Michał Górny
2022-06-08 12:34 Yixun Lan
2022-05-05 23:48 WANG Xuerui
2022-05-05 20:43 Michał Górny
2022-05-05 20:28 Sam James
2022-05-05 17:35 Arthur Zamarin
2022-05-05 16:48 Jakov Smolić
2022-05-05 10:25 Jakov Smolić
2022-05-05 9:54 Jakov Smolić
2022-05-05 5:38 Arthur Zamarin
2022-05-04 13:16 Agostino Sarubbo
2022-05-03 17:37 Arthur Zamarin
2022-05-01 18:22 Agostino Sarubbo
2022-05-01 12:20 Jakov Smolić
2022-04-29 8:27 Sam James
2022-04-06 23:34 Sam James
2022-04-06 23:34 Sam James
2022-01-29 18:13 Michał Górny
2021-09-15 2:32 Sam James
2021-08-11 23:07 Sam James
2021-01-07 0:43 Michał Górny
2020-08-21 3:17 Georgy Yakovlev
2019-12-26 12:01 Georgy Yakovlev
2019-12-26 10:53 Michał Górny
2019-12-26 10:53 Michał Górny
2019-10-04 16:09 Michał Górny
2017-06-30 11:19 Michał Górny
2017-06-30 11:19 Michał Górny
2016-06-01 16:47 Michał Górny
2016-01-27 14:49 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=1629164531.0418f09ef7e55a1f5e5cd3c0a60c059c1c47f1e4.sam@gentoo \
--to=sam@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