public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-sound/rhythmbox/
Date: Sat, 17 Mar 2018 18:14:19 +0000 (UTC)	[thread overview]
Message-ID: <1521310430.63ba7e3f740a30678075e085b9e35519dd5e98d3.zlogene@gentoo> (raw)

commit:     63ba7e3f740a30678075e085b9e35519dd5e98d3
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 17 18:13:50 2018 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sat Mar 17 18:13:50 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=63ba7e3f

media-sound/rhythmbox: amd64 stable wrt bug #650540

Package-Manager: Portage-2.3.24, Repoman-2.3.6

 media-sound/rhythmbox/rhythmbox-3.4.2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-sound/rhythmbox/rhythmbox-3.4.2.ebuild b/media-sound/rhythmbox/rhythmbox-3.4.2.ebuild
index 951da542ba5..3fc2aa573a9 100644
--- a/media-sound/rhythmbox/rhythmbox-3.4.2.ebuild
+++ b/media-sound/rhythmbox/rhythmbox-3.4.2.ebuild
@@ -22,7 +22,7 @@ REQUIRED_USE="
 	python? ( ${PYTHON_REQUIRED_USE} )
 "
 
-KEYWORDS="~alpha ~amd64 ~arm ~ia64 ~ppc ~ppc64 ~sparc ~x86"
+KEYWORDS="~alpha amd64 ~arm ~ia64 ~ppc ~ppc64 ~sparc ~x86"
 
 COMMON_DEPEND="
 	>=dev-libs/glib-2.38:2


             reply	other threads:[~2018-03-17 18:14 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-17 18:14 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-17 12:23 [gentoo-commits] repo/gentoo:master commit in: media-sound/rhythmbox/ Pacho Ramos
2024-11-17 12:23 Pacho Ramos
2024-11-03 15:58 Andreas K. Hüttel
2024-05-28 20:49 Sam James
2024-05-18  8:47 Pacho Ramos
2024-01-15  3:32 Ionen Wolkens
2023-10-29 22:23 Mart Raudsepp
2023-09-22  3:14 Matt Turner
2023-07-17 14:35 Matt Turner
2023-06-17 15:54 Arthur Zamarin
2023-06-13 18:17 Arthur Zamarin
2023-06-13 18:03 Sam James
2023-05-31 20:05 Matt Turner
2023-05-23 19:27 Georgy Yakovlev
2023-05-18 12:17 Andreas Sturmlechner
2023-05-06 18:44 Jakov Smolić
2023-05-06 12:11 Sam James
2023-05-06 11:34 Sam James
2023-05-03 19:34 Matt Turner
2022-06-22 23:01 Matt Turner
2022-05-02 16:23 Matt Turner
2022-01-13  2:00 Georgy Yakovlev
2021-10-17 21:07 Mart Raudsepp
2021-09-24  1:37 Yixun Lan
2021-04-30  1:47 Matt Turner
2020-04-20 20:42 Mart Raudsepp
2020-02-15  9:18 Mart Raudsepp
2020-02-09 16:31 Michał Górny
2019-12-04 20:17 Matt Turner
2019-01-06 12:45 Mart Raudsepp
2019-01-06 12:45 Mart Raudsepp
2018-04-29  0:08 Mart Raudsepp
2018-02-01  8:25 Gilles Dartiguelongue
2018-01-31  8:28 Gilles Dartiguelongue
2018-01-28 14:40 Mikle Kolyada
2017-12-09 19:40 Pacho Ramos
2017-08-19 22:49 Gilles Dartiguelongue
2017-04-27 22:08 Mart Raudsepp
2017-04-27 10:36 Agostino Sarubbo
2017-04-23 21:23 Agostino Sarubbo
2017-04-23 11:29 David Seifert
2017-04-17 16:49 David Seifert
2017-04-17 16:49 David Seifert
2016-12-06  9:26 Pacho Ramos
2016-09-11 11:28 Gilles Dartiguelongue
2016-08-21 22:25 Gilles Dartiguelongue
2016-04-03 12:42 Pacho Ramos
2016-04-03 12:42 Pacho Ramos
2016-03-06 20:36 Mikle Kolyada
2016-01-30 12:57 Pacho Ramos
2015-12-31 17:30 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=1521310430.63ba7e3f740a30678075e085b9e35519dd5e98d3.zlogene@gentoo \
    --to=zlogene@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