public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libmcrypt/
Date: Wed,  3 Aug 2016 04:06:19 +0000 (UTC)	[thread overview]
Message-ID: <1470194867.460f03f90149fe973551d6fb3b1b072c22908757.jer@gentoo> (raw)

commit:     460f03f90149fe973551d6fb3b1b072c22908757
Author:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Wed Aug  3 03:27:47 2016 +0000
Commit:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Wed Aug  3 03:27:47 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=460f03f9

dev-libs/libmcrypt: Stable for HPPA (bug #587336).

Package-Manager: portage-2.3.0
RepoMan-Options: --ignore-arches

 dev-libs/libmcrypt/libmcrypt-2.5.8-r3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-libs/libmcrypt/libmcrypt-2.5.8-r3.ebuild b/dev-libs/libmcrypt/libmcrypt-2.5.8-r3.ebuild
index e30cd6f..5c84992 100644
--- a/dev-libs/libmcrypt/libmcrypt-2.5.8-r3.ebuild
+++ b/dev-libs/libmcrypt/libmcrypt-2.5.8-r3.ebuild
@@ -12,7 +12,7 @@ SRC_URI="mirror://sourceforge/mcrypt/${P}.tar.gz"
 
 LICENSE="GPL-2 LGPL-2.1"
 SLOT="0"
-KEYWORDS="alpha ~amd64 arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~amd64-fbsd ~x86-fbsd ~x86-interix ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~x86-solaris"
+KEYWORDS="alpha ~amd64 arm ~arm64 hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~amd64-fbsd ~x86-fbsd ~x86-interix ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~x86-solaris"
 IUSE=""
 
 DEPEND=""


             reply	other threads:[~2016-08-03  4:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03  4:06 Jeroen Roovers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-27 20:34 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libmcrypt/ Andreas K. Hüttel
2024-08-25 15:24 Andreas K. Hüttel
2024-03-14  7:48 Arthur Zamarin
2024-03-14  6:43 Joonas Niilola
2024-03-14  5:21 Sam James
2024-03-14  4:54 Sam James
2024-03-14  4:54 Sam James
2024-03-14  4:54 Sam James
2024-03-14  4:54 Sam James
2024-03-14  4:54 Sam James
2024-02-28 16:07 Sam James
2023-04-20 22:30 Sam James
2022-12-13 17:35 Sam James
2022-12-13 17:35 Sam James
2022-12-13 17:35 Sam James
2022-11-24 18:14 Conrad Kostecki
2019-05-22  5:49 Aaron Bauman
2018-09-27 23:55 Alon Bar-Lev
2017-03-25 21:46 Alon Bar-Lev
2017-03-15  6:27 Alon Bar-Lev
2017-03-15  6:00 Jeroen Roovers
2017-03-07 19:12 Michael Weber
2017-03-04 13:46 Agostino Sarubbo
2017-03-04 13:38 Agostino Sarubbo
2017-03-03 19:14 Tobias Klausmann
2017-01-29 16:19 Fabian Groffen
2017-01-18 14:52 Alon Bar-Lev
2017-01-13 23:32 Alon Bar-Lev
2016-07-18 17:14 Markus Meier
2016-06-30 16:10 Tobias Klausmann

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=1470194867.460f03f90149fe973551d6fb3b1b072c22908757.jer@gentoo \
    --to=jer@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