Your package fails to build with the newest autoconf-2.71, which was part of a recent wide Fedora change. More information about Fedora autoconf Change available here: https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test. The easiest way to reproduce the problem is to execute a fedora scratch-build on your package. Thank you for cooperation!
This is not an autoconf issue, this is because of vala 0.53, and just like last time vala updated and broke dee, I have no clue what to adjust to fix it. :/
Seems like the same as https://bugzilla.redhat.com/show_bug.cgi?id=1999471
Still broken with vala-0.53.2-1.fc36: /usr/bin/vapigen --pkg gio-2.0 --library dee-1.0 --metadatadir=. ../src/Dee-1.0.gir Dee-1.0-custom.vala Dee-1.0.gir:1180.7-1180.58: warning: Field `Dee.Filter.destroy' conflicts with method of the same name <method name="destroy" c:identifier="dee_filter_destroy"> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dee-1.0.gir:1274.7-1274.42: error: `Dee.Filter' already contains a definition for `new' <function name="new" c:identifier="dee_filter_new"> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dee-1.0-custom.vala:19.3-19.27: note: previous definition of `new' was here public static Filter @new (Dee.StaticFilterMapFunc map_func, owned Dee.FilterMapNotify map_notify); ^^^^^^^^^^^^^^^^^^^^^^^^^ Dee-1.0.gir:8618.7-8618.70: warning: Field `Dee.ModelReader.destroy' conflicts with method of the same name <method name="destroy" c:identifier="dee_model_reader_destroy"> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Generation failed: 1 error(s), 2 warning(s) make[2]: *** [Makefile:569: dee-1.0.vapi] Error 1 make[2]: Leaving directory '/builddir/build/BUILD/dee-1.2.7/vapi' make[1]: *** [Makefile:527: all-recursive] Error 1 make[1]: Leaving directory '/builddir/build/BUILD/dee-1.2.7' make: *** [Makefile:433: all] Error 2
The following builds were made after this report was opened: vala-0.53.1-2.fc36 vala-0.53.2-1.fc36 vala-0.54.0-1.fc36 vala-0.54.1-1.fc36 vala-0.54.2-1.fc36 vala-0.54.3-1.fc36
Still broken, same bug.
*** Bug 2038928 has been marked as a duplicate of this bug. ***
Patched around this in dee. Not sure if my approach is correct or not, but it builds, and all the dependencies (libunity, zeitgeist) build against it, so it can't be too wrong (hopefully).