From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-Archive_Tar/
Date: Fri, 10 Apr 2020 09:48:52 +0000 (UTC) [thread overview]
Message-ID: <1586512117.a3d0240c7a5ed690f05781b6d8f9b71c3c372ec2.slyfox@gentoo> (raw)
commit: a3d0240c7a5ed690f05781b6d8f9b71c3c372ec2
Author: Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Fri Apr 10 09:25:57 2020 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Fri Apr 10 09:48:37 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a3d0240c
dev-php/PEAR-Archive_Tar: stable 1.4.5 for hppa under ALLARCHES, bug #675576
Package-Manager: Portage-2.3.89, Repoman-2.3.20
RepoMan-Options: --include-arches="hppa"
Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
dev-php/PEAR-Archive_Tar/PEAR-Archive_Tar-1.4.5.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-php/PEAR-Archive_Tar/PEAR-Archive_Tar-1.4.5.ebuild b/dev-php/PEAR-Archive_Tar/PEAR-Archive_Tar-1.4.5.ebuild
index ef91adf2ead..b4314c0f240 100644
--- a/dev-php/PEAR-Archive_Tar/PEAR-Archive_Tar-1.4.5.ebuild
+++ b/dev-php/PEAR-Archive_Tar/PEAR-Archive_Tar-1.4.5.ebuild
@@ -11,7 +11,7 @@ HOMEPAGE="https://pear.php.net/package/Archive_Tar"
SRC_URI="https://pear.php.net/get/${MY_P}.tgz"
LICENSE="BSD"
SLOT="0"
-KEYWORDS="~alpha amd64 arm ~hppa ~ia64 ppc ppc64 ~s390 sparc x86"
+KEYWORDS="~alpha amd64 arm hppa ~ia64 ppc ppc64 ~s390 sparc x86"
IUSE=""
# bzip2 and zlib are needed for compressed tarballs, and there's one
next reply other threads:[~2020-04-10 9:49 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 9:48 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-17 6:33 [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-Archive_Tar/ Sam James
2024-06-11 19:26 Michael Orlitzky
2021-08-13 19:27 Brian Evans
2021-08-13 6:51 Agostino Sarubbo
2021-07-21 13:01 Brian Evans
2021-05-10 14:19 Brian Evans
2021-01-20 15:16 Brian Evans
2021-01-20 0:02 Sam James
2021-01-18 20:58 Brian Evans
2020-12-06 19:17 Thomas Deutschmann
2020-12-06 19:17 Thomas Deutschmann
2020-11-20 14:00 Brian Evans
2020-11-20 14:00 Brian Evans
2020-09-30 18:05 Thomas Deutschmann
2020-09-30 18:05 Thomas Deutschmann
2020-06-08 16:44 Sergei Trofimovich
2020-06-07 8:44 Agostino Sarubbo
2020-06-06 18:10 Agostino Sarubbo
2020-06-06 17:34 Agostino Sarubbo
2020-06-06 17:32 Agostino Sarubbo
2020-06-06 17:29 Agostino Sarubbo
2020-06-06 12:57 Sergei Trofimovich
2019-12-12 23:33 Aaron Bauman
2019-12-09 23:33 Thomas Deutschmann
2019-11-17 21:01 Thomas Deutschmann
2019-04-24 19:45 Brian Evans
2019-01-24 23:30 Brian Evans
2019-01-24 22:22 Thomas Deutschmann
2019-01-17 8:31 Sergei Trofimovich
2019-01-16 14:57 Brian Evans
2018-09-19 12:47 Brian Evans
2018-09-19 12:47 Brian Evans
2018-09-19 8:42 Sergei Trofimovich
2018-08-22 20:20 Brian Evans
2017-02-04 16:50 Michael Orlitzky
2017-02-04 16:50 Michael Orlitzky
2017-02-04 15:21 Agostino Sarubbo
2017-01-06 5:09 Michael Orlitzky
2016-07-28 14:45 Michael Orlitzky
2016-07-11 23:01 Michael Orlitzky
2016-02-26 1:25 Brian Evans
2015-08-16 2:20 Brian Evans
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=1586512117.a3d0240c7a5ed690f05781b6d8f9b71c3c372ec2.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