public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Miroslav Šulc" <fordfrog@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-sound/audacity/
Date: Mon,  3 Aug 2020 05:00:28 +0000 (UTC)	[thread overview]
Message-ID: <1596430811.0c90b828ce1b43eb173e89427ad01d011548fd54.fordfrog@gentoo> (raw)

commit:     0c90b828ce1b43eb173e89427ad01d011548fd54
Author:     Miroslav Šulc <fordfrog <AT> gentoo <DOT> org>
AuthorDate: Mon Aug  3 05:00:11 2020 +0000
Commit:     Miroslav Šulc <fordfrog <AT> gentoo <DOT> org>
CommitDate: Mon Aug  3 05:00:11 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0c90b828

media-sound/audacity: fixed lilv dep in 2.4.2-r1

Closes: https://bugs.gentoo.org/735256
Package-Manager: Portage-3.0.1, Repoman-2.3.23
Signed-off-by: Miroslav Šulc <fordfrog <AT> gentoo.org>

 media-sound/audacity/audacity-2.4.2-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-sound/audacity/audacity-2.4.2-r1.ebuild b/media-sound/audacity/audacity-2.4.2-r1.ebuild
index 3cb2f876023..5c79d8c9882 100644
--- a/media-sound/audacity/audacity-2.4.2-r1.ebuild
+++ b/media-sound/audacity/audacity-2.4.2-r1.ebuild
@@ -38,7 +38,7 @@ RDEPEND="dev-libs/expat
 	lv2? (
 		dev-libs/serd
 		dev-libs/sord
-		media-libs/lilv
+		>=media-libs/lilv-0.24.6-r2
 		media-libs/lv2
 		media-libs/sratom
 		media-libs/suil


             reply	other threads:[~2020-08-03  5:00 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03  5:00 Miroslav Šulc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-13 14:42 [gentoo-commits] repo/gentoo:master commit in: media-sound/audacity/ Miroslav Šulc
2025-03-11 19:07 Miroslav Šulc
2025-01-25  9:38 Miroslav Šulc
2024-12-29 17:19 Miroslav Šulc
2024-12-29 17:19 Miroslav Šulc
2024-12-24  5:06 Sam James
2024-12-14  5:36 Miroslav Šulc
2024-10-31 19:20 Miroslav Šulc
2024-06-01  3:46 Ionen Wolkens
2024-05-17 18:26 Sam James
2024-04-17 19:20 Ionen Wolkens
2024-03-21  2:52 Sam James
2024-03-05  4:48 Sam James
2024-01-16  3:36 Sam James
2024-01-11 13:03 Sam James
2024-01-11 13:01 Sam James
2023-12-15 12:37 Arthur Zamarin
2023-12-15  3:30 Sam James
2023-12-15  3:26 Ionen Wolkens
2023-12-05 18:25 Ionen Wolkens
2023-12-04 10:20 Sam James
2023-10-03 14:44 Mike Gilbert
2023-10-02  7:02 Miroslav Šulc
2023-06-19  6:47 Miroslav Šulc
2023-06-07  5:19 Miroslav Šulc
2023-06-06 16:55 Arthur Zamarin
2023-05-01  8:32 Miroslav Šulc
2023-05-01  7:35 Arthur Zamarin
2023-03-02  6:43 Miroslav Šulc
2023-01-29 11:12 Miroslav Šulc
2023-01-21 16:18 Arsen Arsenović
2021-09-22 14:30 Yixun Lan
2021-08-16 21:28 Sam James
2020-09-13  8:44 Sergei Trofimovich
2020-09-09 21:59 Sergei Trofimovich
2020-09-07  8:59 Miroslav Šulc
2020-09-07  7:35 Sergei Trofimovich
2020-09-07  7:31 Sergei Trofimovich
2020-08-23 10:39 Miroslav Šulc
2020-08-06  7:33 Miroslav Šulc
2020-08-06  2:35 Sam James
2020-08-04  6:47 Miroslav Šulc
2020-08-02 18:23 Miroslav Šulc
2020-08-02 11:10 Miroslav Šulc
2020-04-25 20:09 Mikle Kolyada
2020-02-12 14:14 Miroslav Šulc
2019-03-11 15:54 Lars Wendler
2018-11-04 22:26 Andreas Sturmlechner
2018-11-04 22:03 Sergei Trofimovich
2018-08-25 18:55 Sergei Trofimovich
2018-08-23  2:32 Mikle Kolyada
2018-08-23  1:41 Thomas Deutschmann
2018-08-22 17:07 Andreas Sturmlechner
2018-08-22 17:07 Andreas Sturmlechner
2018-02-21 10:18 Lars Wendler
2018-02-21 10:14 Lars Wendler
2018-02-21 10:14 Lars Wendler
2017-12-07 11:17 Lars Wendler
2017-11-06 11:11 Lars Wendler
2017-11-06 11:09 Lars Wendler
2017-09-11 12:10 Alexis Ballier
2017-06-18 16:42 Alexis Ballier
2017-06-13 12:31 Agostino Sarubbo
2017-06-05 11:05 Agostino Sarubbo
2017-05-11  9:37 Lars Wendler
2017-05-11  9:37 Lars Wendler
2016-03-31 12:22 Lars Wendler
2015-11-08 10:07 Alexis Ballier
2015-11-08 10:07 Alexis Ballier
2015-10-30 15:21 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=1596430811.0c90b828ce1b43eb173e89427ad01d011548fd54.fordfrog@gentoo \
    --to=fordfrog@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