public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/chromaprint/
Date: Thu,  5 May 2022 17:30:13 +0000 (UTC)	[thread overview]
Message-ID: <1651771796.77e1410445e95f4a37ffd01c3fe59c43f945ddaf.arthurzam@gentoo> (raw)

commit:     77e1410445e95f4a37ffd01c3fe59c43f945ddaf
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Thu May  5 17:29:56 2022 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Thu May  5 17:29:56 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=77e14104

media-libs/chromaprint: Stabilize 1.5.1-r2 sparc, #842690

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 media-libs/chromaprint/chromaprint-1.5.1-r2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-libs/chromaprint/chromaprint-1.5.1-r2.ebuild b/media-libs/chromaprint/chromaprint-1.5.1-r2.ebuild
index 6f28f800db69..845bcde80333 100644
--- a/media-libs/chromaprint/chromaprint-1.5.1-r2.ebuild
+++ b/media-libs/chromaprint/chromaprint-1.5.1-r2.ebuild
@@ -15,7 +15,7 @@ SRC_URI="https://github.com/acoustid/${PN}/releases/download/v${PV}/${P}.tar.gz
 
 LICENSE="LGPL-2.1"
 SLOT="0/1"
-KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~ia64 ~ppc ppc64 ~riscv ~sparc x86"
+KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~ia64 ~ppc ppc64 ~riscv sparc x86"
 IUSE="test tools"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2022-05-05 17:30 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 17:30 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-20  8:02 [gentoo-commits] repo/gentoo:master commit in: media-libs/chromaprint/ Miroslav Šulc
2024-01-19 23:08 Ionen Wolkens
2024-01-15 14:01 Sam James
2024-01-15  8:32 Arthur Zamarin
2024-01-15  8:32 Arthur Zamarin
2024-01-15  8:32 Arthur Zamarin
2023-09-24 23:47 Sam James
2023-09-24 23:47 Sam James
2023-02-26 18:16 Arthur Zamarin
2023-02-15  6:48 Sam James
2022-05-06  6:21 Miroslav Šulc
2022-05-05 20:28 Sam James
2022-05-05 17:49 Arthur Zamarin
2022-05-05 17:30 Arthur Zamarin
2022-05-05 10:25 Jakov Smolić
2022-05-05  9:54 Jakov Smolić
2022-04-05  4:58 Sam James
2022-04-05  4:57 Sam James
2022-02-22  6:46 Sam James
2022-01-26  9:00 Miroslav Šulc
2022-01-25 21:25 Sam James
2022-01-24 14:42 Sam James
2022-01-24  3:42 Sam James
2022-01-24  3:42 Sam James
2022-01-23 15:21 Sam James
2022-01-23 13:09 Jakov Smolić
2022-01-23 13:09 Jakov Smolić
2021-12-24  8:10 Miroslav Šulc
2021-08-21  8:44 Marek Szuba
2021-04-25  5:14 Sam James
2021-04-25  5:14 Sam James
2021-04-23 16:13 Sam James
2021-04-22 23:01 Sam James
2021-04-22 23:01 Sam James
2021-04-22 20:15 Sam James
2021-04-22 12:23 Sam James
2021-04-22 11:10 Miroslav Šulc
2020-05-07 14:07 Lars Wendler
2020-05-07 12:42 Lars Wendler
2020-04-26  8:31 Mikle Kolyada
2020-04-11 10:20 Sergei Trofimovich
2019-11-20 14:06 Andreas Sturmlechner
2018-10-20 12:16 Sergei Trofimovich
2018-10-02 14:02 Tobias Klausmann
2018-09-03 17:40 Markus Meier
2018-08-21  0:13 Sergei Trofimovich
2018-08-18 23:18 Mikle Kolyada
2018-08-18 22:24 Sergei Trofimovich
2018-08-18 19:24 Sergei Trofimovich
2018-05-24  0:42 Aaron Bauman
2018-04-19 19:42 Sergei Trofimovich
2017-06-20  9:20 Alexis Ballier
2017-06-10 20:14 Sergei Trofimovich
2017-04-05 14:07 Tobias Klausmann
2017-02-23 12:35 Michael Weber
2017-02-22 21:09 Michael Weber
2017-02-22 13:19 Jeroen Roovers
2017-02-18  8:51 Jeroen Roovers
2017-02-17 17:28 Markus Meier
2017-02-15 15:56 Agostino Sarubbo
2017-02-15 15:05 Agostino Sarubbo
2017-02-05 11:59 Jeroen Roovers
2017-01-02 11:02 Lars Wendler
2017-01-02 11:02 Lars Wendler
2016-12-24 10:33 Alexis Ballier
2016-07-13 10:16 Lars Wendler
2016-02-18 15:59 Alexis Ballier
2015-10-30 14:45 Alexis Ballier
2015-10-30 14:45 Alexis Ballier

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=1651771796.77e1410445e95f4a37ffd01c3fe59c43f945ddaf.arthurzam@gentoo \
    --to=arthurzam@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