public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-libs/fltk/
Date: Thu, 12 Mar 2020 16:24:27 +0000 (UTC)	[thread overview]
Message-ID: <1584030264.d96d3f4765ec5e8ec703fc53419185af8ca0622b.ago@gentoo> (raw)

commit:     d96d3f4765ec5e8ec703fc53419185af8ca0622b
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 12 16:24:24 2020 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Thu Mar 12 16:24:24 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d96d3f47

x11-libs/fltk: ppc64 stable wrt bug #712216

Package-Manager: Portage-2.3.89, Repoman-2.3.20
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 x11-libs/fltk/fltk-1.3.5-r4.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/x11-libs/fltk/fltk-1.3.5-r4.ebuild b/x11-libs/fltk/fltk-1.3.5-r4.ebuild
index 30a605f73a3..8e148e6db5a 100644
--- a/x11-libs/fltk/fltk-1.3.5-r4.ebuild
+++ b/x11-libs/fltk/fltk-1.3.5-r4.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://www.fltk.org/pub/${PN}/${PV}/${P}-source.tar.gz"
 
 SLOT="1"
 LICENSE="FLTK LGPL-2"
-KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ia64 ~mips ppc ~ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux ~x86-macos"
+KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ia64 ~mips ppc ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux ~x86-macos"
 IUSE="cairo debug doc examples games +opengl static-libs +threads +xft +xinerama"
 
 RDEPEND="


             reply	other threads:[~2020-03-12 16:24 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12 16:24 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-18  5:31 [gentoo-commits] repo/gentoo:master commit in: x11-libs/fltk/ Sam James
2024-03-18  5:31 Sam James
2023-10-06 17:00 Joonas Niilola
2022-08-14  3:19 WANG Xuerui
2021-03-28  0:34 Jonas Stein
2020-11-06 15:23 Sam James
2020-03-13  8:15 Jeroen Roovers
2020-03-12 16:26 Agostino Sarubbo
2020-03-12 16:25 Agostino Sarubbo
2020-03-12 16:23 Agostino Sarubbo
2020-03-12 16:23 Agostino Sarubbo
2020-03-12 16:22 Agostino Sarubbo
2020-03-12 16:21 Agostino Sarubbo
2020-02-15 10:03 David Seifert
2019-11-23  2:08 Aaron Bauman
2019-11-15 10:05 Jeroen Roovers
2019-11-15 10:05 Jeroen Roovers
2019-11-15 10:05 Jeroen Roovers
2019-04-30 14:11 Jeroen Roovers
2019-04-30 14:02 Jeroen Roovers
2019-04-30 11:28 Jeroen Roovers
2019-04-30 11:22 Jeroen Roovers
2019-04-30 11:22 Jeroen Roovers
2019-04-30 11:12 Jeroen Roovers
2019-04-08 19:23 Jeroen Roovers
2019-04-08 19:23 Jeroen Roovers
2018-05-08  6:28 Lars Wendler
2018-03-31 19:01 Mart Raudsepp
2017-05-21 22:34 Jeroen Roovers
2016-10-06  9:34 Alexis Ballier
2016-08-24 10:18 Jeroen Roovers
2015-12-22 16:48 Manuel Rüger
2015-11-23  9:25 Agostino Sarubbo
2015-11-08 18:55 Mikle Kolyada
2015-11-05 11:20 Agostino Sarubbo
2015-10-30 10:15 Agostino Sarubbo
2015-10-25 19:11 Markus Meier
2015-10-25 12:56 Mikle Kolyada
2015-10-09  5:21 Jeroen Roovers
2015-10-07  4:56 Jeroen Roovers
2015-10-02 17:19 Chí-Thanh Christopher Nguyễn

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=1584030264.d96d3f4765ec5e8ec703fc53419185af8ca0622b.ago@gentoo \
    --to=ago@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