Opened 5 weeks ago

Last modified 3 days ago

#7214 new license violation

Amazon violates (L)GPL

Reported by: kierank Owned by:
Priority: normal Component: undetermined
Version: unspecified Keywords:
Cc: flamefew Blocked By:
Blocking: Reproduced by developer: yes
Analyzed by developer: no


Amazon distribute a binary of FFmpeg with some kind of FPGA acceleration that is nonfree. No source code provided.

Change History (12)

comment:1 Changed 5 weeks ago by llogan

They (AWSOpen) have been notified about this on Twitter.

comment:3 Changed 5 weeks ago by cehoyos

  • Reproduced by developer set
$ md5sum ffmpeg
09725a633a31da86b9cec69676a4f85c  ffmpeg

comment:4 Changed 4 weeks ago by flamefew

Thank you ffmpeg community for your patience.

We've worked with @ThomasXilinx on GitHub to update this conference tutorial with the build instructions and patch file. The build downloads the official ffmpeg source code from, and we have noted this in the LICENSE_README file so users know where they can get the source code from. If you would like us to also provide a copy of the source ourselves, please let me know and we can put a copy up on S3 and link to that.

Last edited 4 weeks ago by flamefew (previous) (diff)

comment:5 Changed 4 weeks ago by cehoyos

The ffmpeg binaries in the two repositories are different, the provided patch does not allow to build the binary you distribute.

comment:6 Changed 4 weeks ago by flamefew

Thanks @cehoyos.

We went back to the contributor, fixed some build-script errors, and had multiple people checking that the build scripts successfully reproduces the uploaded binary. We also found that there were two copies of the binary in the repository and removed one:

comment:7 Changed 4 weeks ago by cehoyos

The patchfile looks unchanged, so I don't understand how this can be fixed now.

comment:8 Changed 5 days ago by cehoyos

  • Cc flamefew added

Are you planning to fix this or will you stop distributing binaries based on FFmpeg?

comment:9 Changed 3 days ago by flamefew

Apologies for the delay; I've asked the contributing company (Xilinx) to respond.

comment:10 Changed 3 days ago by twowings

@cehoyos, you are correct that the patchfile we distributed did not allow to build the same binary. This is because as we uploaded the correct patchfile, we mistakenly uploaded an incorrect binary. This was fixed with, not by uploading a new patchfile, but uploading the correct binary. The current patchfile and build scripts posted on Github will allow you to build the correct binary. This is why we believe the Github content to be now resolving the issue even if the patchfile didn’t change.

comment:11 Changed 3 days ago by cehoyos

But where can I find the source to build the original binary?

comment:12 Changed 3 days ago by kierank

The ffmpeg binary that is shipped still contains "--enable-nonfree"

Note: See TracTickets for help on using tickets.