Source: bridge-utils Version: 1.7.1-2 Severity: important Tags: ftbfs Justification: FTBFS X-Debbugs-Cc: [email protected] User: [email protected] Usertags: rrr-no-as-default-issue
Dear maintainer, During a test rebuild for building packages with `Rules-Requires-Root: no` as the default in `dpkg`, bridge-utils failed to rebuild. Log Summary: ------------------------------------------------------------------------------- [...]57a5dbad908dbb28a790328a67412d47b6826cff 16140 bridge-utils_1.7.1-2.debian.tar.xz
Checksums-Sha256:a61d8be4f1a1405c60c8ef38d544f0c18c05b33b9b07e5b4b31033536165e60e 29632 bridge-utils_1.7.1.orig.tar.xz 59dd869801347a7ad5601d758078204545a4af497a9a4b459f10350fe0eeed55 16140 bridge-utils_1.7.1-2.debian.tar.xz
Files: 3e1fee4dc22cac5457c2f6ffb990a518 29632 bridge-utils_1.7.1.orig.tar.xz 4f167135730272dd1bd80bf994a51e97 16140 bridge-utils_1.7.1-2.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEBqPldg9hG0uxqQ5ouGiMo9h21aMFAmXiWnQACgkQuGiMo9h2 1aN32xAAmh4tnGIT/HKqXULwPtbjHdnJwHTLP7jo4RdFF/H3MPZwZakqj34YAllH 3mUwm1CmkrjH2FrVnASsMz2dAq4LTDNjdrSm6Ylx4xY0T/CgWdRcfdSJqVqzg9/0 NpkjkAJNl/veIxu/jPI7KX3yZ0/UZc4vVj5dgQE5Ra6bBC86oC2STvmCQ9+4V6Vj GZuQy+kuIZaELUTdw4Vx2EmOe0cyZ8KnD+aErUA1uNwDGMQVQlQMbPXUDy+oczwd OpBoYTV9rDmitWY1PWCaeNaROkhY7ZhtXc4d4pjdV6hVxxih/zPjDudu6tltnekC kUOE2q2DlRxOc3I4Djzlya5ZF6+iNE0ACF7t1xR9fYkjk4ln+k5n4Nv67v54kah8 Hjy8xnXxBo1HNlgcMD+xwHmBjcKD+QoE2NNLYp3tPvJtSFyIH5/pmV1VqQcIXKzO QSo65I23ayWZcWk2aa6KKNCh1NBfwiE1IIcyIRuzCNHTSpErVk5b9sfUwqvVseUH CUaQO0Kd65NbUJVoZI6m5r1csCAowRa0qUAVX6oanzT1+Zk/RWstWCKlbYK6Z8fW 3suq2rq8hSRnlKSwa47xXhw0kgmfIG4icuF037twVtelvr6Gl9QvNndUO1eGQwdy 1AZNlEt1Mz1GVSQJQVfUteP7+QQ1xGs63pTsQfaoCE3jFwDMRAE= =ys3i -----END PGP SIGNATURE----- gpgv: Signature made Fri Mar 1 22:45:08 2024 UTC gpgv: using RSA key 06A3E5760F611B4BB1A90E68B8688CA3D876D5A3 gpgv: Can't check signature: No public keydpkg-source: warning: cannot verify inline signature for ./bridge-utils_1.7.1-2.dsc: no acceptable signature found
dpkg-source: info: extracting bridge-utils in /<<PKGBUILDDIR>> dpkg-source: info: unpacking bridge-utils_1.7.1.orig.tar.xz dpkg-source: info: unpacking bridge-utils_1.7.1-2.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying manpage Check disk space ---------------- Sufficient free space for build User Environment ---------------- APT_CONFIG=/var/lib/sbuild/apt.conf HOME=/sbuild-nonexistent LANG=en_US.UTF-8 LC_ALL=C.UTF-8 LOGNAME=debusine-worker PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games SHELL=/bin/sh USER=debusine-worker dpkg-buildpackage ----------------- Command: dpkg-buildpackage -us -uc -b -rfakeroot dpkg-buildpackage: info: source package bridge-utils dpkg-buildpackage: info: source version 1.7.1-2 dpkg-buildpackage: info: source distribution unstabledpkg-buildpackage: info: source changed by Santiago García Mantiñán <[email protected]>
dpkg-source --before-build . dpkg-buildpackage: info: host architecture arm64 debian/rules clean dh_testdir dh_testrootrm -f build-stamp configure-stamp configure bridge-utils.spec libbridge/config.h libbridge/stamp-h1
# Add here commands to clean up after the build process. [ ! -f Makefile ] || /usr/bin/make maintainer-clean dh_clean debian/rules binary dh_testdir # Add here commands to configure the package. autoconf configure.ac:17: warning: The macro 'AC_HEADER_STDC' is obsolete. configure.ac:17: You should run autoupdate. ./lib/autoconf/headers.m4:663: AC_HEADER_STDC is expanded from... configure.ac:17: the top level configure.ac:22: warning: The macro 'AC_HEADER_TIME' is obsolete. configure.ac:22: You should run autoupdate. ./lib/autoconf/headers.m4:702: AC_HEADER_TIME is expanded from... configure.ac:22: the top level./configure --host=aarch64-linux-gnu --build=aarch64-linux-gnu --prefix=/usr --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info
checking for aarch64-linux-gnu-gcc... aarch64-linux-gnu-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.outchecking for suffix of executables... checking whether we are cross compiling... no
checking for suffix of object files... o checking whether the compiler supports GNU C... yes checking whether aarch64-linux-gnu-gcc accepts -g... yeschecking for aarch64-linux-gnu-gcc option to enable C11 features... none needed
checking for a BSD-compatible install... /usr/bin/install -c checking for aarch64-linux-gnu-ranlib... aarch64-linux-gnu-ranlib checking for stdio.h... yes checking for stdlib.h... yes checking for string.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for strings.h... yes checking for sys/stat.h... yes checking for sys/types.h... yes checking for unistd.h... yes checking for sys/time.h... yes checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for sys/ioctl.h... yes checking for sys/time.h... (cached) yes checking for an ANSI C-conforming const... yes checking for gethostname... yes checking for socket... yes checking for strdup... yes checking for uname... yes checking for if_nametoindex... yes checking for if_indextoname... yes checking for strlcpy... yes checking for strlcat... yes configure: creating ./config.status config.status: creating doc/Makefileconfig.status: WARNING: 'doc/Makefile.in' seems to ignore the --datarootdir setting
config.status: creating libbridge/Makefile config.status: creating brctl/Makefileconfig.status: WARNING: 'brctl/Makefile.in' seems to ignore the --datarootdir setting
config.status: creating Makefileconfig.status: WARNING: 'Makefile.in' seems to ignore the --datarootdir setting
config.status: creating bridge-utils.spec config.status: creating libbridge/config.h touch configure-stamp dh_testdir # Add here commands to compile the package. /usr/bin/make make[1]: Entering directory '/<<PKGBUILDDIR>>' for x in libbridge brctl doc; do /usr/bin/make -w -C $x || exit 1 ; done make[2]: Entering directory '/<<PKGBUILDDIR>>/libbridge'aarch64-linux-gnu-gcc -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -I/usr/src/linux/include -c libbridge_devif.c aarch64-linux-gnu-gcc -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -I/usr/src/linux/include -c libbridge_if.c aarch64-linux-gnu-gcc -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -I/usr/src/linux/include -c libbridge_init.c aarch64-linux-gnu-gcc -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -I/usr/src/linux/include -c libbridge_misc.c ar rcs libbridge.a libbridge_devif.o libbridge_if.o libbridge_init.o libbridge_misc.o
aarch64-linux-gnu-ranlib libbridge.a make[2]: Leaving directory '/<<PKGBUILDDIR>>/libbridge' make[2]: Entering directory '/<<PKGBUILDDIR>>/brctl'aarch64-linux-gnu-gcc -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -I../libbridge -I/usr/src/linux/include -c brctl.c aarch64-linux-gnu-gcc -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -I../libbridge -I/usr/src/linux/include -c brctl_cmd.c aarch64-linux-gnu-gcc -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -I../libbridge -I/usr/src/linux/include -c brctl_disp.c aarch64-linux-gnu-gcc -Wl,-z,relro brctl.o brctl_cmd.o brctl_disp.o -L ../libbridge -lbridge -o brctl
make[2]: Leaving directory '/<<PKGBUILDDIR>>/brctl' make[2]: Entering directory '/<<PKGBUILDDIR>>/doc' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/<<PKGBUILDDIR>>/doc' make[1]: Leaving directory '/<<PKGBUILDDIR>>' touch build-stamp dh_testdir dh_testroot dh_prep dh_installdirs # Add here commands to install the package into debian/tmp. #/usr/bin/make install prefix=/<<PKGBUILDDIR>>/debian/bridge-utils/usrinstall -p -o root -g root -m 755 -m 755 brctl/brctl /<<PKGBUILDDIR>>/debian/bridge-utils/usr/sbin install: cannot change ownership of '/<<PKGBUILDDIR>>/debian/bridge-utils/usr/sbin/brctl': Operation not permitted
make: *** [debian/rules:66: install] Error 1dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
-------------------------------------------------------------------------------- Build finished at 2024-11-15T20:37:17Z ------------------------------------------------------------------------------- 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/~nthykier/rrr-no-as-default/logs/975569.gz You can find common solutions at https://people.debian.org/~nthykier/rrr-no-as-default/docs/solutions.md 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. If this package is listed in https://people.debian.org/~nthykier/rrr-no-as-default/docs/static-ownership.list, then please just set `Rules-Requires-Root: binary-targets` to the source stanza of `debian/control` as a fix to this bug. If this package is listed in https://people.debian.org/~nthykier/rrr-no-as-default/docs/maybe-misbuilds.list, then the package was deemed at risk for misbuilding (having wrong ownership) but had a FTBFS problem we tested it. Please test whether the package works with `Rules-Requires-Root: no` validating that the resulting deb has the correct ownership for all paths in the deb. The goal is to have the default changed in `dpkg` either in `Trixie` or `Forky`, depending on progress and feasibility with the release schedule for Trixie. For more information on this bug filing, please see: https://lists.debian.org/debian-dpkg/2024/11/msg00016.html Thanks, PS: The builds were performed in mid-November. If you fixed the problem between between then and this bug being filed, then please just close the bug with the version it was fixed in.
OpenPGP_signature.asc
Description: OpenPGP digital signature
