Fri, 09 Oct 2026 20:03:53 +0200 Javier Llorente <[email protected]>:
> Done. It should be fixed once changes are propagated. What does that change really do in practice? Why would anyone want to have the mini variant from Packman installed? It does the very same thing as ffmpeg.rpm and ffmpeg-mini-libs.rpm from OBS: almost nothing, because there is just a single "BuildRequires: c_compiler" The mini package is just for bootstrap in OBS. Everything else should use the non-mini variant. Simply because the mini variant pretends that certain ABIs exist at runtime because the API is in the header files. But at runtime they can not be there. The internal ffmpeg-mini pkg in Packman makes sure the mini variant from OBS is masked and never selected by the solver. Since yesterday all ffmpeg packages which _link to OBS also have useforbuild disabled to avoid breakage when the ABI of the variant in OBS and in Packman get out of sync, due to build failures for example. There is still a chance that these out-of-sync packages end up on the mirror and can not be installed. But that was the case with the previous setup as well. So all this change does is that it builds yet another copy of ffmeg, which can not be used in Packman, because it is masked by ffmeg-mini, and it is also needlessly published. I think the proper way to address this would have been an investigation why "libavcodec62 = 8.1.2-1699.6.pm.35" could not be installed. For some reason zypper lacks the functionality to recursively resolve and show the real error. In addition the ffmpeg.spec should be adjusted to have the current Requires: (libav* or ffmpeg-mini-libs) in the non BUILD_ORIG case, and Requires: libav* in the BUILD_ORIG case, simply because there can be no matching mini package. Thanks, Olaf
pgpJViEZE3_Mk.pgp
Description: Digitale Signatur von OpenPGP
_______________________________________________ Packman mailing list [email protected] https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
