Control: forwarded -1 https://gitlab.gnome.org/GNOME/gimp/-/issues/11929
On 2024-08-10 Lucas Nussbaum <lu...@debian.org> wrote: > Source: gimp > Version: 2.10.38-2 > Severity: serious [...] > > dh_install: warning: Cannot find (any matches for) > > "usr/lib/gimp/2.0/plug-ins/file-heif" (tried in ., debian/tmp) [...] Looking at the build logs we find building against libheif-dev_1.17.6-4+b2 vs libheif-dev_1.18.1-1 and - HEIC: import: yes - export: yes [profile support: yes] - AVIF: import: yes - export: yes + HEIC: import: - export: [profile support: no] + AVIF: import: - export: This is caused by can_import_heic=`$PKG_CONFIG --variable=builtin_h265_decoder libheif` and similar code in configure.ac and heif dropping dead code from libheif.pc https://github.com/strukturag/libheif/commit/cf0d89c6e0809427427583290547a7757428cf5a -# Contrary to older versions of libheif (<= 1.14.2), the available-codec-variables are now all set to 'yes' -# as since 1.14.0, codecs can be dynamically loaded at runtime and it is not possible anymore to determine -# the available codecs at compile-time. You'll get an unknown codec error at runtime if you try to use an -# unavailable codec. -builtin_h265_decoder=yes -builtin_h265_encoder=yes -builtin_avif_decoder=yes -builtin_avif_encoder=yes There is a resolved bug for gimp https://gitlab.gnome.org/GNOME/gimp/-/issues/9080 but it is about the master branch and its meson build system not about 2.10 which uses autoconf. (I have just submitted essentially the same info as an upstream bug.) cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
