Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

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!
Tasklist

FS#73273 - [chromaprint] PLEASE ENTER SUMMARY

Attached to Project: Arch Linux
Opened by Alkaris (Alkaris) - Thursday, 06 January 2022, 06:33 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 06 January 2022, 08:49 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

This package causes so much issues with other applications requiring FFMPEG. It keeps overriding other packages that depend on ffmpeg that even if you remove chromaprint, it still stays in the systems library path unable to be removed by other packages.

install literally any other package that depends on these packages from ffmpeg after removing Chromaprint and you get this;

```
could not satisfy dependencies:
- unable to satisfy dependency 'libavcodec.so=58-64' required by chromaprint
- unable to satisfy dependency 'libavformat.so=58-64' required by chromaprint
- unable to satisfy dependency 'libavutil.so=56-64' required by chromaprint
- unable to satisfy dependency 'libswresample.so=3-64' required by chromaprint
```

Why is this package preventing any other application that depends on ffmpeg to not satisfy the dependency when it clearly shouldn't interfere with other packages like this. What's causing chromaprint to hold on to these packages and prevent it from being removed or updated? If Chromaprint was removed, this shouldn't be an issue, but since I removed it, chromaprint still somehow exists on the system and prevents any other packages from being installed.
This task depends upon

Closed by  Antonio Rojas (arojas)
Thursday, 06 January 2022, 08:49 GMT
Reason for closing:  Not a bug
Additional comments about closing:  please use the forum for support questions

Loading...