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: app-emulation/vice/
Date: Tue, 22 Sep 2015 08:57:30 +0000 (UTC)	[thread overview]
Message-ID: <1442912239.8e90127fb27bf9764bbb69e5df9acb20c3dbc337.ago@gentoo> (raw)

commit:     8e90127fb27bf9764bbb69e5df9acb20c3dbc337
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Tue Sep 22 08:55:57 2015 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Tue Sep 22 08:57:19 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8e90127f

app-emulation/vice: ppc stable wrt bug #560226

Package-Manager: portage-2.2.20.1
RepoMan-Options: --include-arches="ppc"

 app-emulation/vice/vice-2.4.20.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-emulation/vice/vice-2.4.20.ebuild b/app-emulation/vice/vice-2.4.20.ebuild
index 5f68ece..7bf5976 100644
--- a/app-emulation/vice/vice-2.4.20.ebuild
+++ b/app-emulation/vice/vice-2.4.20.ebuild
@@ -11,7 +11,7 @@ SRC_URI="mirror://sourceforge/vice-emu/releases/${P}.tar.gz"
 
 LICENSE="GPL-2+"
 SLOT="0"
-KEYWORDS="amd64 ~ppc ~sparc x86"
+KEYWORDS="amd64 ppc ~sparc x86"
 IUSE="Xaw3d alsa ethernet ffmpeg fullscreen +gtk2 ipv6 lame nls oss png pulseaudio sdl +sdlsound threads vte zlib"
 
 # upstream says gtk3 and sdl2 shouldn't be exposed yet.


             reply	other threads:[~2015-09-22  8:57 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22  8:57 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-08 17:47 [gentoo-commits] repo/gentoo:master commit in: app-emulation/vice/ Ionen Wolkens
2024-01-28 20:00 Arthur Zamarin
2024-01-23 16:40 Sam James
2024-01-05 10:25 Ionen Wolkens
2023-12-26 14:39 Ionen Wolkens
2023-06-11 10:44 Andreas Sturmlechner
2023-01-30 19:11 Ionen Wolkens
2023-01-26 15:13 Ionen Wolkens
2022-12-29 20:29 Ionen Wolkens
2022-12-28 12:17 Ionen Wolkens
2022-12-26 13:33 Ionen Wolkens
2022-10-29 19:43 Sam James
2022-07-29 17:52 Arthur Zamarin
2022-07-26  1:39 Ionen Wolkens
2022-02-28 11:28 Ionen Wolkens
2022-02-05 23:39 Ionen Wolkens
2022-02-03 11:31 Ionen Wolkens
2022-01-26  3:32 Ionen Wolkens
2022-01-26  1:09 Ionen Wolkens
2021-12-26 23:40 Ionen Wolkens
2021-10-11 18:21 Ionen Wolkens
2021-10-03 11:19 Ionen Wolkens
2021-06-22  5:43 Ionen Wolkens
2021-01-09  3:09 Sam James
2021-01-07 16:28 James Le Cuirot
2021-01-07 11:33 Sam James
2021-01-07  5:09 Sam James
2021-01-07  0:58 Sam James
2020-09-26 17:33 James Le Cuirot
2020-09-18 20:44 James Le Cuirot
2020-06-14 19:42 James Le Cuirot
2020-04-25 17:30 Mikle Kolyada
2020-04-14 12:32 Agostino Sarubbo
2020-04-08 10:57 Agostino Sarubbo
2020-02-22 22:21 David Seifert
2020-02-22 22:10 James Le Cuirot
2018-11-29 22:04 Andreas Sturmlechner
2018-03-28 18:36 Pacho Ramos
2018-01-21 10:20 David Seifert
2017-12-10  9:27 Ulrich Müller
2017-01-26 22:48 David Seifert
2017-01-19  1:11 Austin English
2016-10-14 17:49 Austin English
2016-10-14 17:49 Austin English
2016-07-01 18:41 Austin English
2015-12-29  7:41 Michael Sterrett
2015-12-14 14:12 Agostino Sarubbo
2015-11-12  6:51 Michael Sterrett
2015-09-19 13:30 Agostino Sarubbo

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=1442912239.8e90127fb27bf9764bbb69e5df9acb20c3dbc337.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