OpenSuse still appears to violate FFmpeg copyrights

[Carl Eugen Hoyos]

I have repeatedly asked people at openSUSE to stop violating the copyright of the FFmpeg developers (or to stop actively supporting such violations) by distributing non-free versions of FFmpeg.
The most memorable answer was that I should stop stop bullying open source projects, I have no idea how to continue.

[Gyan]

Can you share a link to the package details?

[Balling]

What part of --enable-nonfree? Nvidia's nvpp? Cause --enable-cuda_llvm is free now.

[Carl Eugen Hoyos]

I cannot share a link but I can confirm that after updating the packaged version of FFmpeg, I still see a non-free version installed on my system.

[Balling]

Replying to Carl Eugen Hoyos:

I cannot share a link but I can confirm that after updating the packaged version of FFmpeg, I still see a non-free version installed on my system.

Is it chromium-ffmpeg or ffmpeg-full-extra or ffmpeg-ma or ffmpeg-libfdk_aac or ffmpegthumbs one? See ​https://software.opensuse.org/search?utf8=%E2%9C%93&baseproject=ALL&q=Ffmpeg There is this thingy that is called "dpkg -S binary" that can tell you that. Also AGAIN, what NON-FREE is there? Non-free in by itself does not mean there is non-free stuff activated. AFAIK, non-free like from nvidia is not so simple to compile.

Also where is a bug there? ​https://bugzilla.opensuse.org

Also, it is a joke that even the official builds on github cannot activate non-free stuff. Maybe you can waive copyright to that repo somehow? Since you all now created the central beurocratic abstraction.

[Gyan]

It looks to be this one

​https://build.opensuse.org/package/view_file/home:aevseev/ffmpeg/ffmpeg.spec?expand=1

Line 298:
--enable-nonfree \

Line 329:
--enable-openssl \

[Balling]

So what, openssl? Seriosly?

Right, "The Fraunhofer FDK AAC and OpenSSL libraries are under licenses which are incompatible with the GPLv2 and v3. To the best of our knowledge, they are compatible with the LGPL."

WTF, lol, what a joke. openssl is cryptolibrary, I do not think that any copyright applies there, SERIOSULY? They cannot say it is their software when so many stuff depends on openssl, of (inter)national security. That is lost case immediatelly. Even ffmpeg can try to argue that, but openssl...

Also, openssl is now relicenced to Apache-2.0 in 3.0 version with some very crazy GPL crosslicensing. Alas, I am not very into openssl, know only some crypto stuff there. But couple of issues of mine are still open there.

[Balling]

Very cool. ​https://github.com/BtbN/FFmpeg-Builds/commit/93719c1a54bbfa2d013261341b419a2f026110f9

"OpenSSL 3.0 with Apache license is not out yet."

You cannot be serious, Carl. In both senses of the work Carl.