Package: src:pygobject
Version: 3.48.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:

--------------------------------------------------------------------------------
[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure-arch
make[1]: Entering directory '/<<PKGBUILDDIR>>'
set -e; for v in 3.12; do \
        dh_auto_configure \
                --builddirectory=build-$v \
                -- \
                -Dpython=/usr/bin/python$v \
                -Dauto_features=enabled \
                ; \
done
        cd build-3.12 && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson 
setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 
-Dpython=/usr/bin/python3.12 -Dauto_features=enabled
The Meson build system
Version: 1.5.2
Source dir: /<<PKGBUILDDIR>>
Build dir: /<<PKGBUILDDIR>>/build-3.12
Build type: native build
Project name: pygobject
Project version: 3.48.2
C compiler for the host machine: cc (gcc 14.2.0 "cc (Debian 14.2.0-5) 14.2.0")
C linker for the host machine: cc ld.bfd 2.43.1
Host machine cpu family: x86_64
Host machine cpu: x86_64
Program /usr/bin/python3.12 found: YES (/usr/bin/python3.12)
Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1
Run-time dependency python found: YES 3.12
Run-time dependency gobject-introspection-1.0 found: YES 1.82.0
Run-time dependency glib-2.0 found: YES 2.82.1
Run-time dependency gobject-2.0 found: YES 2.82.1
Run-time dependency gio-2.0 found: YES 2.82.1
Run-time dependency gmodule-2.0 found: YES 2.82.1
Run-time dependency libffi found: YES 3.4.6
Run-time dependency cairo found: YES 1.18.2
Run-time dependency cairo-gobject found: YES 1.18.2
Message: Found pycairo with target Python: 
/usr/lib/python3/dist-packages/cairo/include
Compiler for C supports arguments -Wall: YES
Compiler for C supports arguments -Warray-bounds: YES
Compiler for C supports arguments -Wcast-align: YES
Compiler for C supports arguments -Wduplicated-branches: YES
Compiler for C supports arguments -Wextra: YES
Compiler for C supports arguments -Wformat=2: YES
Compiler for C supports arguments -Wformat-nonliteral: YES
Compiler for C supports arguments -Wformat-security: YES
Compiler for C supports arguments -Wimplicit-function-declaration: YES
Compiler for C supports arguments -Winit-self: YES
Compiler for C supports arguments -Wjump-misses-init: YES
Compiler for C supports arguments -Wlogical-op: YES
Compiler for C supports arguments -Wmissing-declarations: YES
Compiler for C supports arguments -Wmissing-format-attribute: YES
Compiler for C supports arguments -Wmissing-include-dirs: YES
Compiler for C supports arguments -Wmissing-noreturn: YES
Compiler for C supports arguments -Wmissing-prototypes: YES
Compiler for C supports arguments -Wnested-externs: YES
Compiler for C supports arguments -Wnull-dereference: YES
Compiler for C supports arguments -Wold-style-definition: YES
Compiler for C supports arguments -Wpacked: YES
Compiler for C supports arguments -Wpointer-arith: YES
Compiler for C supports arguments -Wrestrict: YES
Compiler for C supports arguments -Wreturn-type: YES
Compiler for C supports arguments -Wshadow: YES
Compiler for C supports arguments -Wsign-compare: YES
Compiler for C supports arguments -Wstrict-aliasing: YES
Compiler for C supports arguments -Wstrict-prototypes: YES
Compiler for C supports arguments -Wswitch-default: YES
Compiler for C supports arguments -Wundef: YES
Compiler for C supports arguments -Wunused-but-set-variable: YES
Compiler for C supports arguments -Wwrite-strings: YES
Compiler for C supports arguments 
-Wno-incompatible-pointer-types-discards-qualifiers: NO
Compiler for C supports arguments -Wno-missing-field-initializers: YES
Compiler for C supports arguments -Wno-unused-parameter: YES
Compiler for C supports arguments -Wno-discarded-qualifiers: YES
Compiler for C supports arguments -Wno-sign-conversion: YES
Compiler for C supports arguments -Wno-cast-function-type: YES
Compiler for C supports arguments -Wno-int-conversion: YES
Compiler for C supports arguments -fno-strict-aliasing: YES
Compiler for C supports arguments -fvisibility=hidden: YES
Configuring config.h using configuration
Configuring pygobject-3.0.pc using configuration
Configuring PyGObject-3.48.2.egg-info using configuration
Compiler for C supports arguments -fvisibility=hidden: YES (cached)
Dependency gobject-introspection-1.0 found: YES 1.82.0 (cached)
Dependency gobject-introspection-1.0 found: YES 1.82.0 (cached)
Program /usr/bin/x86_64-linux-gnu-g-ir-scanner found: YES 
(/usr/bin/x86_64-linux-gnu-g-ir-scanner)
Dependency gobject-introspection-1.0 found: YES 1.82.0 (cached)
Program /usr/bin/x86_64-linux-gnu-g-ir-compiler found: YES 
(/usr/bin/x86_64-linux-gnu-g-ir-compiler)
Dependency gio-2.0 found: YES 2.82.1 (cached)
Program /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas found: YES 
(/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas)
Build targets in project: 10

pygobject 3.48.2

  User defined options
    auto_features     : enabled
    buildtype         : plain
    libdir            : lib/x86_64-linux-gnu
    localstatedir     : /var
    prefix            : /usr
    sysconfdir        : /etc
    wrap_mode         : nodownload
    python.bytecompile: -1
    python            : /usr/bin/python3.12

Found ninja-1.12.1 at /usr/bin/ninja
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   debian/rules override_dh_auto_build-arch
make[1]: Entering directory '/<<PKGBUILDDIR>>'
set -e; for v in 3.12; do \
        PYTHON=/usr/bin/python$v \
        dh_auto_build \
                --arch \
                --builddirectory=build-$v \
                -- \
                ; \
done
        cd build-3.12 && LC_ALL=C.UTF-8 ninja -j2 -v
[1/58] cc -Itests/libgimarshallingtests.so.p -Itests -I../tests 
-I/usr/share/gobject-introspection-1.0/tests -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/libmount 
-I/usr/include/blkid -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
'-D_GI_EXTERN=__attribute__((visibility("default"))) extern' -fvisibility=hidden -MD -MQ 
tests/libgimarshallingtests.so.p/gimarshallingtestsextra.c.o -MF 
tests/libgimarshallingtests.so.p/gimarshallingtestsextra.c.o.d -o 
tests/libgimarshallingtests.so.p/gimarshallingtestsextra.c.o -c ../tests/gimarshallingtestsextra.c
FAILED: tests/libgimarshallingtests.so.p/gimarshallingtestsextra.c.o
cc -Itests/libgimarshallingtests.so.p -Itests -I../tests -I/usr/share/gobject-introspection-1.0/tests 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 
-I/usr/include/libmount -I/usr/include/blkid -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall 
-Winvalid-pch -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection 
-Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
'-D_GI_EXTERN=__attribute__((visibility("default"))) extern' -fvisibility=hidden -MD -MQ 
tests/libgimarshallingtests.so.p/gimarshallingtestsextra.c.o -MF 
tests/libgimarshallingtests.so.p/gimarshallingtestsextra.c.o.d -o 
tests/libgimarshallingtests.so.p/gimarshallingtestsextra.c.o -c ../tests/gimarshallingtestsextra.c
In file included from ../tests/gimarshallingtestsextra.c:19:
../tests/gimarshallingtestsextra.h:40:1: error: unknown type name 
‘_GI_TEST_EXTERN’; did you mean ‘GI_TEST_EXTERN’?
   40 | _GI_TEST_EXTERN
      | ^~~~~~~~~~~~~~~
      | GI_TEST_EXTERN
../tests/gimarshallingtestsextra.h:41:7: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ 
or ‘__attribute__’ before ‘gi_marshalling_tests_extra_flags_get_type’
   41 | GType gi_marshalling_tests_extra_flags_get_type (void) G_GNUC_CONST;
      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../tests/gimarshallingtestsextra.h:44:16: error: expected ‘;’ before ‘void’
   44 | _GI_TEST_EXTERN
      |                ^
      |                ;
   45 | void gi_marshalling_tests_compare_two_gerrors_in_gvalue (GValue *v, 
GValue *v1);
      | ~~~~
../tests/gimarshallingtestsextra.h:46:1: error: unknown type name 
‘_GI_TEST_EXTERN’; did you mean ‘GI_TEST_EXTERN’?
   46 | _GI_TEST_EXTERN
      | ^~~~~~~~~~~~~~~
      | GI_TEST_EXTERN
../tests/gimarshallingtestsextra.h:47:10: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ 
or ‘__attribute__’ before ‘gi_marshalling_tests_nullable_gerror’
   47 | gboolean gi_marshalling_tests_nullable_gerror(GError *error);
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../tests/gimarshallingtestsextra.h:49:16: error: expected ‘;’ before ‘void’
   49 | _GI_TEST_EXTERN
      |                ^
      |                ;
   50 | void gi_marshalling_tests_ghashtable_enum_none_in (GHashTable 
*hash_table);
      | ~~~~
../tests/gimarshallingtestsextra.h:51:1: error: unknown type name 
‘_GI_TEST_EXTERN’; did you mean ‘GI_TEST_EXTERN’?
   51 | _GI_TEST_EXTERN
      | ^~~~~~~~~~~~~~~
      | GI_TEST_EXTERN
../tests/gimarshallingtestsextra.h:52:12: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ 
or ‘__attribute__’ before ‘*’ token
   52 | GHashTable * gi_marshalling_tests_ghashtable_enum_none_return (void);
      |            ^
../tests/gimarshallingtestsextra.h:54:1: error: unknown type name 
‘_GI_TEST_EXTERN’; did you mean ‘GI_TEST_EXTERN’?
   54 | _GI_TEST_EXTERN
      | ^~~~~~~~~~~~~~~
      | GI_TEST_EXTERN
../tests/gimarshallingtestsextra.h:55:7: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ 
or ‘__attribute__’ before ‘*’ token
   55 | gchar * gi_marshalling_tests_filename_copy (gchar *path_in);
      |       ^
../tests/gimarshallingtestsextra.h:56:1: error: unknown type name 
‘_GI_TEST_EXTERN’; did you mean ‘GI_TEST_EXTERN’?
   56 | _GI_TEST_EXTERN
      | ^~~~~~~~~~~~~~~
      | GI_TEST_EXTERN
../tests/gimarshallingtestsextra.h:57:10: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ 
or ‘__attribute__’ before ‘gi_marshalling_tests_filename_exists’
   57 | gboolean gi_marshalling_tests_filename_exists (gchar *path);
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../tests/gimarshallingtestsextra.h:58:1: error: unknown type name 
‘_GI_TEST_EXTERN’; did you mean ‘GI_TEST_EXTERN’?
   58 | _GI_TEST_EXTERN
      | ^~~~~~~~~~~~~~~
      | GI_TEST_EXTERN
../tests/gimarshallingtestsextra.h:59:7: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ 
or ‘__attribute__’ before ‘*’ token
   59 | gchar * gi_marshalling_tests_filename_to_glib_repr (gchar *path_in, 
gsize *len);
      |       ^
../tests/gimarshallingtestsextra.h:61:1: error: unknown type name 
‘_GI_TEST_EXTERN’; did you mean ‘GI_TEST_EXTERN’?
   61 | _GI_TEST_EXTERN
      | ^~~~~~~~~~~~~~~
      | GI_TEST_EXTERN
../tests/gimarshallingtestsextra.h:62:29: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ 
or ‘__attribute__’ before ‘*’ token
   62 | GIMarshallingTestsExtraEnum * 
gi_marshalling_tests_enum_array_return_type (gsize *n_members);
      |                             ^
../tests/gimarshallingtestsextra.h:64:16: error: expected ‘;’ before ‘void’
   64 | _GI_TEST_EXTERN
      |                ^
      |                ;
   65 | void gi_marshalling_tests_extra_flags_large_in 
(GIMarshallingTestsExtraFlags value);
      | ~~~~
../tests/gimarshallingtestsextra.h:67:1: error: unknown type name 
‘_GI_TEST_EXTERN’; did you mean ‘GI_TEST_EXTERN’?
   67 | _GI_TEST_EXTERN
      | ^~~~~~~~~~~~~~~
      | GI_TEST_EXTERN
../tests/gimarshallingtestsextra.h:68:7: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ 
or ‘__attribute__’ before ‘*’ token
   68 | gchar *gi_marshalling_tests_extra_utf8_full_return_invalid (void);
      |       ^
../tests/gimarshallingtestsextra.h:69:16: error: expected ‘;’ before ‘void’
   69 | _GI_TEST_EXTERN
      |                ^
      |                ;
   70 | void gi_marshalling_tests_extra_utf8_full_out_invalid (gchar **utf8);
      | ~~~~
[2/58] cc -Itests/libgimarshallingtests.so.p -Itests -I../tests 
-I/usr/share/gobject-introspection-1.0/tests -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/libmount 
-I/usr/include/blkid -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
'-D_GI_EXTERN=__attribute__((visibility("default"))) extern' -fvisibility=hidden -MD -MQ 
tests/libgimarshallingtests.so.p/_usr_share_gobject-introspection-1.0_tests_gimarshallingtests.c.o 
-MF 
tests/libgimarshallingtests.so.p/_usr_share_gobject-introspection-1.0_tests_gimarshallingtests.c.o.d 
-o tests/libgimarshallingtests.so.p/_usr_share_gobject-introspection-1.0_tests_gimarshallingtests.c.o 
-c /usr/share/gobject-introspection-1.0/tests/gimarshallingtests.c
ninja: build stopped: subcommand failed.
dh_auto_build: error: cd build-3.12 && LC_ALL=C.UTF-8 ninja -j2 -v returned 
exit code 1
make[1]: *** [debian/rules:30: override_dh_auto_build-arch] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:17: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------

The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202409/

About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.

Reply via email to