Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#68746 - [mpv] incorrect dependency recently added for libjpeg-turbo

Attached to Project: Community Packages
Opened by Adam Fontenot (amfontenot) - Wednesday, 25 November 2020, 22:08 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 25 November 2020, 23:03 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



Recently a hard dependency was added to the mpv package for libjpeg-turbo. This makes mpv incompatible with other libjpegs that have the same drop-in ABI, e.g. mozjpeg.

Please swap out the dependency to be for libjpeg instead. See for example gdk-pixbuf2 (which is required by a ton of packages): and

Additional info:
* mpv 1:0.33.0-2
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 25 November 2020, 23:03 GMT
Reason for closing:  Not a bug
Additional comments about closing:  The AUR package doesn't have the correctly provided. End of story. Complain to the maintainer.
Comment by Adam Fontenot (amfontenot) - Wednesday, 25 November 2020, 22:54 GMT
  • Field changed: Percent Complete (100% → 0%)
I incorrectly said "required". I meant that the mozjpeg package already *provides* libjpeg-turbo. And yet any package directly requiring libjpeg-turbo is trying to install it.

I personally have 49 of the 128 repository packages depending on a libjpeg installed, and all of them except mpv appear to depend on libjpeg (because they're not incompatible with mozjpeg). My understanding was that depending on libjpeg was a best practice.

Can you have a look at the PKGBUILD? If you know how to resolve the conflict on my end, please let me know.
Comment by Eli Schwartz (eschwartz) - Wednesday, 25 November 2020, 22:55 GMT
mpv links to libjpeg, not libturbojpeg, therefore it's reasonable for it to depend on libjpeg, not libjpeg-turbo. It might not be the only such package with that distinction.

mpv does not, presumably, care about the libturbojpeg API, only the libjpeg one... :)
Comment by Adam Fontenot (amfontenot) - Wednesday, 25 November 2020, 23:02 GMT
@Eli: is there anything I can do to make the mozjpeg PKGBUILD more compatible with packages that require libjpeg-turbo. I'm already providing it as you can see here:

I think it's quite possible that I'm just forgetting something stupid. I know I've done AUR packages in the past that provided drop-in replacements for a repo package, and they worked fine. Something complex going on with libjpeg vs libjpeg-turbo that I'm not quite seeing.