From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/libvmaf/
Date: Sun, 20 Mar 2022 13:13:15 +0000 (UTC) [thread overview]
Message-ID: <1647781990.39f3b86fff8b739e1afd463223087215498e5944.juippis@gentoo> (raw)
commit: 39f3b86fff8b739e1afd463223087215498e5944
Author: Adel KARA SLIMANE <adel.ks <AT> zegrapher <DOT> com>
AuthorDate: Thu Mar 17 12:24:28 2022 +0000
Commit: Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Sun Mar 20 13:13:10 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=39f3b86f
media-libs/libvmaf: restrict TEST phase
The hardcoded paths are buggy for some tests,
the library works otherwise
The testing code could be patched otherwise
Closes: https://bugs.gentoo.org/835471
Signed-off-by: Adel KARA SLIMANE <adel.ks <AT> zegrapher.com>
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>
media-libs/libvmaf/libvmaf-2.3.0.ebuild | 3 +++
1 file changed, 3 insertions(+)
diff --git a/media-libs/libvmaf/libvmaf-2.3.0.ebuild b/media-libs/libvmaf/libvmaf-2.3.0.ebuild
index 289a427e83d2..7adc3c9eca99 100644
--- a/media-libs/libvmaf/libvmaf-2.3.0.ebuild
+++ b/media-libs/libvmaf/libvmaf-2.3.0.ebuild
@@ -21,6 +21,9 @@ fi
LICENSE="BSD-2-with-patent"
SLOT="0"
+# upstream issue, see bug #835471
+RESTRICT="test"
+
BDEPEND="
dev-lang/nasm
"
next reply other threads:[~2022-03-20 13:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 13:13 Joonas Niilola [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-22 15:17 [gentoo-commits] repo/gentoo:master commit in: media-libs/libvmaf/ Sam James
2024-03-16 8:38 Joonas Niilola
2023-10-06 12:46 Joonas Niilola
2023-10-06 12:46 Joonas Niilola
2022-12-02 18:44 WANG Xuerui
2022-06-16 16:30 Sam James
2022-05-22 7:42 Jakov Smolić
2022-04-18 6:43 Joonas Niilola
2022-04-14 3:47 Joonas Niilola
2022-04-07 20:00 Sam James
2022-03-20 13:13 Joonas Niilola
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=1647781990.39f3b86fff8b739e1afd463223087215498e5944.juippis@gentoo \
--to=juippis@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