
On 8/12/22 02:04, Thorsten Kukuk wrote:
Hi,
On Thu, Aug 11, David C. Rankin wrote:
All,
I've package libheif for the hiec-convert feature, but there are various packages previously pulled in by darktable, gimp-plugin-heic and imagemagick heic files that conflict with the new libraries that are built with my libheif package.
We have already a libheif package. We cannot have two packages with the same name. Why is a new package with the same name necessary? Why can you not enhance or adjust the current package?
Thorsten
I'll rename it -- but, the libheif provided by openSUSE does not provide a functional: /usr/bin/heif-convert /usr/bin/heif-enc /usr/bin/heif-info /usr/bin/heif-thumbnailer With the libs provided by openSUSE, you end up with: $ heif-convert IMG_0257.heic IMG_0257.jpg File contains 1 image Could not decode image: 0: Unsupported feature: Unsupported codec ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ That is because openSUSE doesn't require libde265.so.0, libx265so.199, and librav1e.so.0 with the X265, and rav1e packages I don't require renaming, I'm just looking for advise on how to handle the conflict for the openSUSE packages that don't Apple .heic conversion. Apparently, this does work on TW, so I'm not sure why 15.4 doesn't. Yes, we can likely fix the current 15.4 package by simply adding the Requires: and the "%configure --enable-static=no". I'll see if I can branch on buildservice and report back. -- David C. Rankin, J.D.,P.E.