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-ml/camlp4/
Date: Sun,  1 Nov 2015 11:12:11 +0000 (UTC)	[thread overview]
Message-ID: <1446375503.9b10821d4a903ec0be6a663879588364ac245368.jer@gentoo> (raw)

commit:     9b10821d4a903ec0be6a663879588364ac245368
Author:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Sun Nov  1 10:58:23 2015 +0000
Commit:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Sun Nov  1 10:58:23 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9b10821d

dev-ml/camlp4: Stable for HPPA (bug #463018).

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

 dev-ml/camlp4/camlp4-4.02.1_p3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-ml/camlp4/camlp4-4.02.1_p3.ebuild b/dev-ml/camlp4/camlp4-4.02.1_p3.ebuild
index f48edb7..850c546 100644
--- a/dev-ml/camlp4/camlp4-4.02.1_p3.ebuild
+++ b/dev-ml/camlp4/camlp4-4.02.1_p3.ebuild
@@ -13,7 +13,7 @@ SRC_URI="https://github.com/ocaml/camlp4/archive/${MY_PV}.tar.gz -> ${P}.tar.gz"
 
 LICENSE="LGPL-2-with-linking-exception"
 SLOT="0/${PV}"
-KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sparc ~x86 ~amd64-fbsd ~amd64-linux ~x86-fbsd ~x86-linux"
+KEYWORDS="~alpha ~amd64 ~arm hppa ~ia64 ~mips ~ppc ~ppc64 ~sparc ~x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux"
 IUSE="+ocamlopt"
 
 DEPEND=">=dev-lang/ocaml-4.02:=[ocamlopt?]"


             reply	other threads:[~2015-11-01 11:12 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-01 11:12 Jeroen Roovers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-11-03  4:14 [gentoo-commits] repo/gentoo:master commit in: dev-ml/camlp4/ Jeroen Roovers
2015-11-10 12:01 Agostino Sarubbo
2015-11-11  9:54 Agostino Sarubbo
2015-11-12 11:21 Agostino Sarubbo
2015-11-21 14:24 Markus Meier
2016-02-04 17:24 Tobias Klausmann
2016-03-01 18:47 Alexis Ballier
2016-03-01 19:17 Alexis Ballier
2016-11-29 15:05 Alexis Ballier
2017-01-14 17:14 Mikle Kolyada
2017-01-25 14:29 Agostino Sarubbo
2017-01-25 15:35 Agostino Sarubbo
2017-01-25 15:52 Agostino Sarubbo
2017-01-25 19:21 Tobias Klausmann
2017-01-26 10:22 Agostino Sarubbo
2017-01-26 11:00 Agostino Sarubbo
2017-01-26 15:28 Agostino Sarubbo
2017-01-29 23:02 Jeroen Roovers
2017-02-12 19:58 Markus Meier
2017-02-14  9:31 Alexis Ballier
2017-03-03 11:28 Alexis Ballier
2017-03-03 11:28 Alexis Ballier
2017-06-19 18:12 Alexis Ballier
2017-10-14 11:13 Alexis Ballier
2020-02-09 22:26 Miroslav Šulc
2020-05-05  8:47 Joonas Niilola
2020-07-20  9:01 Joonas Niilola
2020-09-01  0:04 Sam James
2020-09-07  8:47 Sergei Trofimovich
2020-09-25 19:00 Sam James
2020-10-09  8:40 Agostino Sarubbo
2020-10-14 11:34 Mark Wright
2020-10-25 20:27 Sam James
2020-11-28 18:37 Aaron Bauman
2020-12-28 11:49 Sam James
2021-01-26 17:59 Alfredo Tupone
2021-01-28 20:11 Alfredo Tupone
2021-05-04 22:17 Sam James
2021-06-09 21:45 Sam James
2021-06-09 21:45 Sam James
2021-06-09 21:45 Sam James
2021-06-09 21:45 Sam James
2021-06-09 21:45 Sam James
2021-06-10 10:22 Alfredo Tupone
2021-10-06  1:02 Sam James
2021-10-07  1:45 Sam James
2021-10-07  1:46 Sam James
2021-10-13  5:54 Agostino Sarubbo
2021-10-13  6:02 Agostino Sarubbo
2021-10-15  3:04 Sam James
2021-10-17  0:13 Sam James
2021-10-17 19:09 Sam James
2022-01-13 18:59 Alfredo Tupone
2022-05-31  9:11 Sam James
2023-01-30 23:45 Maciej Barć
2023-02-11  9:48 Alfredo Tupone
2023-02-11 11:05 Alfredo Tupone
2023-02-15 18:38 Matt Turner
2023-03-17 10:17 Arthur Zamarin
2023-03-26  7:52 Alfredo Tupone
2023-04-29  8:27 Arthur Zamarin
2023-04-29  8:43 Arthur Zamarin
2023-04-29  8:59 Sam James
2023-04-29 16:16 Arthur Zamarin
2023-10-28  0:24 Sam James
2024-06-01 21:39 Alfredo Tupone
2024-06-09 11:39 Alfredo Tupone
2024-08-25 12:04 Andreas K. Hüttel

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=1446375503.9b10821d4a903ec0be6a663879588364ac245368.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