public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jakov Smolić" <jsmolic@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-plugins/gst-plugins-soundtouch/
Date: Fri,  1 Apr 2022 15:20:53 +0000 (UTC)	[thread overview]
Message-ID: <1648826400.54d7a2a129d751dbf258714d2fb0b097b718180d.jsmolic@gentoo> (raw)

commit:     54d7a2a129d751dbf258714d2fb0b097b718180d
Author:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
AuthorDate: Fri Apr  1 15:20:00 2022 +0000
Commit:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
CommitDate: Fri Apr  1 15:20:00 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=54d7a2a1

media-plugins/gst-plugins-soundtouch: Stabilize 1.18.6 x86, #835598

Signed-off-by: Jakov Smolić <jsmolic <AT> gentoo.org>

 .../gst-plugins-soundtouch/gst-plugins-soundtouch-1.18.6.ebuild         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-plugins/gst-plugins-soundtouch/gst-plugins-soundtouch-1.18.6.ebuild b/media-plugins/gst-plugins-soundtouch/gst-plugins-soundtouch-1.18.6.ebuild
index 9ff704b78571..ca56dcbcf280 100644
--- a/media-plugins/gst-plugins-soundtouch/gst-plugins-soundtouch-1.18.6.ebuild
+++ b/media-plugins/gst-plugins-soundtouch/gst-plugins-soundtouch-1.18.6.ebuild
@@ -7,7 +7,7 @@ GST_ORG_MODULE=gst-plugins-bad
 inherit gstreamer-meson
 
 DESCRIPTION="Beats-per-minute detection and pitch controlling plugin for GStreamer"
-KEYWORDS="amd64 ~x86"
+KEYWORDS="amd64 x86"
 IUSE=""
 
 RDEPEND=">=media-libs/libsoundtouch-1.7.1[${MULTILIB_USEDEP}]"


             reply	other threads:[~2022-04-01 15:21 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01 15:20 Jakov Smolić [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-22  8:19 [gentoo-commits] repo/gentoo:master commit in: media-plugins/gst-plugins-soundtouch/ Arthur Zamarin
2024-04-19 14:23 Arthur Zamarin
2024-04-01 19:55 Mart Raudsepp
2023-10-15 20:54 Mart Raudsepp
2023-07-25 18:10 Arthur Zamarin
2023-07-23 19:32 Arthur Zamarin
2023-06-10  9:45 Arthur Zamarin
2023-05-30 18:21 Sam James
2023-05-30 18:05 Sam James
2023-01-14 15:50 Sam James
2022-12-15  4:46 Arthur Zamarin
2022-12-13 20:03 Arthur Zamarin
2022-10-10  2:34 Matt Turner
2022-09-16  6:52 Agostino Sarubbo
2022-09-14  7:47 Agostino Sarubbo
2022-08-26 13:10 Sam James
2022-06-07 13:59 Matt Turner
2022-05-16 12:35 Jakov Smolić
2022-04-01  7:14 Arthur Zamarin
2021-09-16  6:27 Sam James
2021-05-30  0:40 Sam James
2021-02-19 23:16 Mart Raudsepp
2021-02-14 14:50 Sam James
2021-02-14  2:12 Sam James
2021-02-13 19:49 Mart Raudsepp
2020-06-29 15:51 Mikle Kolyada
2020-06-21 16:52 Thomas Deutschmann
2019-12-07 13:17 Mikle Kolyada
2019-12-07 13:12 Mikle Kolyada
2019-08-27 21:05 Mart Raudsepp
2019-02-05 22:57 Mart Raudsepp
2019-01-15 23:11 Mart Raudsepp
2019-01-09  4:37 Matt Turner
2019-01-09  1:35 Thomas Deutschmann
2018-09-21  5:23 Mart Raudsepp
2018-09-17 23:52 Mart Raudsepp
2018-07-31  8:02 Mart Raudsepp
2018-07-31  0:43 Thomas Deutschmann
2018-07-16 14:01 Mikle Kolyada
2018-06-21 10:40 Mart Raudsepp
2018-06-16 18:27 Mart Raudsepp
2018-03-17 18:03 Mikle Kolyada
2018-02-14 22:06 Mart Raudsepp
2018-01-03  0:05 Mart Raudsepp
2017-12-16 11:33 Tobias Klausmann
2017-12-12 16:55 Mart Raudsepp
2017-10-09 22:48 Thomas Deutschmann
2017-09-18 21:42 Mart Raudsepp
2017-09-18 21:42 Mart Raudsepp
2017-09-16 19:46 Mart Raudsepp
2017-07-15 15:50 Tobias Klausmann
2017-06-18  8:31 Mart Raudsepp
2017-02-25 20:46 Mart Raudsepp
2017-02-16 17:26 Agostino Sarubbo
2017-02-16 13:25 Agostino Sarubbo
2017-02-11 14:52 Mart Raudsepp
2016-07-09 10:12 Pacho Ramos
2016-07-09 10:12 Pacho Ramos
2016-04-02 20:38 Pacho Ramos
2016-01-31 14:45 Gilles Dartiguelongue
2015-12-26 18:21 Gilles Dartiguelongue
2015-12-26 17:15 Gilles Dartiguelongue
2015-11-08 19:27 Gilles Dartiguelongue
2015-10-25 17:32 Gilles Dartiguelongue

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=1648826400.54d7a2a129d751dbf258714d2fb0b097b718180d.jsmolic@gentoo \
    --to=jsmolic@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