public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowi@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/ffmpeg] epel9-next: Drop unused opencv BuildRequires
Date: Tue, 14 Jul 2026 21:59:46 GMT	[thread overview]
Message-ID: <178406638698.1.4839605842776425441.rpms-ffmpeg-4c7c44eb6ab1@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/ffmpeg
            Branch : epel9-next
            Commit : 4c7c44eb6ab1dedbd80907d95b02157ee9e5a8aa
            Author : Yaakov Selkowitz <yselkowi@redhat.com>
            Date   : 2023-02-15T16:02:24-05:00
            Stats  : +0/-1 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/ffmpeg/c/4c7c44eb6ab1dedbd80907d95b02157ee9e5a8aa?branch=epel9-next

            Log:
            Drop unused opencv BuildRequires

opencv has deliberately broken their C API as of 3.4 and completely
removed it in 4.0, meaning there is no way to enable OpenCV in ffmpeg
without completely rewriting the filter in C++.

https://github.com/opencv/opencv/wiki/ChangeLog#version400
https://ffmpeg.org/pipermail/ffmpeg-devel/2018-March/226872.html
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915544

---
diff --git a/ffmpeg.spec b/ffmpeg.spec
index 321be04..42699c7 100644
--- a/ffmpeg.spec
+++ b/ffmpeg.spec
@@ -221,7 +221,6 @@ BuildRequires:  pkgconfig(ogg)
 BuildRequires:  pkgconfig(openal)
 BuildRequires:  pkgconfig(opencore-amrnb)
 BuildRequires:  pkgconfig(OpenCL)
-BuildRequires:  pkgconfig(opencv4)
 BuildRequires:  pkgconfig(opus)
 BuildRequires:  pkgconfig(rav1e)
 BuildRequires:  pkgconfig(rubberband)

             reply	other threads:[~2026-07-14 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 21:59 Yaakov Selkowitz [this message]
2026-07-14 21:59 [rpms/ffmpeg] epel9-next: Drop unused opencv BuildRequires Yaakov Selkowitz

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=178406638698.1.4839605842776425441.rpms-ffmpeg-4c7c44eb6ab1@fedoraproject.org \
    --to=yselkowi@redhat.com \
    --cc=git-commits@fedoraproject.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