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-cdr/cdrdao/
Date: Sun, 21 May 2017 08:09:18 +0000 (UTC)	[thread overview]
Message-ID: <1495354093.9f6014289a9f408bc3d6f8034b8fdaa9a02ab558.ago@gentoo> (raw)

commit:     9f6014289a9f408bc3d6f8034b8fdaa9a02ab558
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Sun May 21 08:08:13 2017 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Sun May 21 08:08:13 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9f601428

app-cdr/cdrdao: amd64 stable wrt bug #608946

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

 app-cdr/cdrdao/cdrdao-1.2.3-r4.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-cdr/cdrdao/cdrdao-1.2.3-r4.ebuild b/app-cdr/cdrdao/cdrdao-1.2.3-r4.ebuild
index 05220d4a518..9b944dbec92 100644
--- a/app-cdr/cdrdao/cdrdao-1.2.3-r4.ebuild
+++ b/app-cdr/cdrdao/cdrdao-1.2.3-r4.ebuild
@@ -16,7 +16,7 @@ fi
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sh ~sparc ~x86 ~x86-fbsd"
+KEYWORDS="~alpha amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sh ~sparc ~x86 ~x86-fbsd"
 IUSE="encode mad vorbis"
 
 RDEPEND="virtual/cdrtools


             reply	other threads:[~2017-05-21  8:09 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-21  8:09 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-16 11:21 [gentoo-commits] repo/gentoo:master commit in: app-cdr/cdrdao/ Sam James
2023-12-16 10:59 Arthur Zamarin
2023-05-27  9:43 Sam James
2023-05-27  9:43 Sam James
2023-05-23  0:10 Sam James
2023-05-18 19:42 Sam James
2023-05-18 19:42 Sam James
2023-05-18 19:17 Arthur Zamarin
2023-03-04 10:15 Arthur Zamarin
2023-03-04  6:34 Arthur Zamarin
2023-03-03 18:50 Arthur Zamarin
2023-03-03 17:25 Arthur Zamarin
2022-12-04 15:59 WANG Xuerui
2022-07-28  8:28 Sam James
2022-07-28  8:28 Sam James
2022-06-21  7:38 Agostino Sarubbo
2022-06-21  7:37 Agostino Sarubbo
2022-06-21  7:36 Agostino Sarubbo
2022-06-20 18:49 Arthur Zamarin
2022-06-20  6:04 Joonas Niilola
2022-06-20  6:04 Joonas Niilola
2022-02-15  7:00 Joonas Niilola
2021-09-24  1:37 Yixun Lan
2020-12-18  9:00 Michał Górny
2018-11-28 12:15 Tobias Klausmann
2018-11-06 23:56 Sergei Trofimovich
2018-11-06 21:31 Mikle Kolyada
2018-11-05  7:51 Sergei Trofimovich
2018-11-05  7:51 Sergei Trofimovich
2018-11-01 19:07 Sergei Trofimovich
2018-10-31 23:35 Sergei Trofimovich
2018-10-31  1:04 Thomas Deutschmann
2018-04-15 18:48 Patrice Clement
2018-02-28 20:11 Andreas Sturmlechner
2018-02-27 21:56 Sergei Trofimovich
2018-02-11 10:01 Michał Górny
2017-12-10  0:32 Sergei Trofimovich
2017-12-02 23:51 Sergei Trofimovich
2017-11-30 20:19 Tobias Klausmann
2017-11-29 20:28 Sergei Trofimovich
2017-05-22  9:25 Agostino Sarubbo
2017-02-11 12:50 Pacho Ramos
2016-05-03 20:56 Markus Meier
2016-04-13  0:59 Sam Jorna
2016-04-07 10:17 Jeroen Roovers
2016-03-06 20:52 Mikle Kolyada
2016-02-21 23:44 Pacho Ramos
2016-01-11  2:33 Mike Frysinger
2015-12-23 10:59 Pacho Ramos

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=1495354093.9f6014289a9f408bc3d6f8034b8fdaa9a02ab558.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