Source: libpam-chroot Version: 0.9-5.3 Severity: important Tags: ftbfs Justification: FTBFS X-Debbugs-Cc: ni...@thykier.net User: ni...@thykier.net 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`,
libpam-chroot failed to rebuild.
Log Summary:
-------------------------------------------------------------------------------
[...]
+------------------------------------------------------------------------------+
| Build
|
+------------------------------------------------------------------------------+
Unpack source
-------------
Format: 3.0 (quilt)
Source: libpam-chroot
Binary: libpam-chroot
Architecture: any
Version: 0.9-5.3
Maintainer: Javier Fernandez-Sanguino Pen~a <j...@debian.org>
Homepage: http://sourceforge.net/projects/pam-chroot/
Standards-Version: 3.9.2
Build-Depends: libpam0g-dev, debhelper (>> 3.0.0)
Package-List:
libpam-chroot deb devel optional arch=any
Checksums-Sha1:
766da389fc3770bb543e1818fa0686982b7d873c 15250 libpam-
chroot_0.9.orig.tar.gz
24945bbd7c6fac24aa9cb83a7cd854c98b974834 11140 libpam-
chroot_0.9-5.3.debian.tar.xz
Checksums-Sha256:
3f63939fd2aff376c9715464f87547160b8d5976de9a5dfbd2f1cd3bb408f19e 15250
libpam-chroot_0.9.orig.tar.gz
60f8c66556f72f67266678b302709069155a8e15bea9c61669f85bffe16027bf 11140
libpam-chroot_0.9-5.3.debian.tar.xz
Files:
9f1e9eae63ee24fdfeba662ca02ecb0c 15250 libpam-chroot_0.9.orig.tar.gz
f840fca460d54f3b91ef0e9ea78a5b55 11140 libpam-chroot_0.9-5.3.debian.tar.xz
gpgv: Signature made Sat May 25 19:55:11 2024 UTC
gpgv: using RSA key 7D1ACFFAD9E0806C9C4CD3925C13D6DB93052E03
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify inline signature for ./libpam-
chroot_0.9-5.3.dsc: no acceptable signature found
dpkg-source: info: extracting libpam-chroot in /<<PKGBUILDDIR>>
dpkg-source: info: unpacking libpam-chroot_0.9.orig.tar.gz
dpkg-source: info: unpacking libpam-chroot_0.9-5.3.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying debian.patch
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 libpam-chroot
dpkg-buildpackage: info: source version 0.9-5.3
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Chris Hofstaedtler
<z...@debian.org>
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture arm64
debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp /usr/bin/make clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
rm -f *.o pam_chroot.so
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_clean
dh_clean: warning: Compatibility levels before 10 are deprecated (level
7 in use)
debian/rules binary
dh_testdir
dh_auto_build
dh_auto_build: warning: Compatibility levels before 10 are deprecated
(level 7 in use)
make -j1
make[1]: Entering directory '/<<PKGBUILDDIR>>'
gcc -fPIC -O2 -Wall -Werror -pedantic -I. -c -o pam_chroot.o pam_chroot.c
gcc -shared -o pam_chroot.so pam_chroot.o -lpam
rm pam_chroot.o
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
touch build-stamp
dh_testdir
dh_testroot
dh_installdirs
dh_installdirs: warning: Compatibility levels before 10 are deprecated
(level 7 in use)
mkdir -p /<<PKGBUILDDIR>>/debian/libpam-chroot/usr/lib/aarch64-linux-
gnu/security
# Add here commands to install the package into debian/libpam-chroot
/usr/bin/make install DESTDIR=/<<PKGBUILDDIR>>/debian/libpam-chroot
LIBDIR=/<<PKGBUILDDIR>>/debian/libpam-chroot/usr/lib/aarch64-linux-gnu/
security INSTALL="install --strip-program=true"
make[1]: Entering directory '/<<PKGBUILDDIR>>'
install --strip-program=true -s -o0 -g0 -m755 pam_chroot.so /
<<PKGBUILDDIR>>/debian/libpam-chroot/usr/lib/aarch64-linux-gnu/security
install: cannot change ownership of '/<<PKGBUILDDIR>>/debian/libpam-
chroot/usr/lib/aarch64-linux-gnu/security/pam_chroot.so': Operation not
permitted
make[1]: *** [Makefile:23: install] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:36: install] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit
status 2
--------------------------------------------------------------------------------
Build finished at 2024-11-17T03:54:06Z
-------------------------------------------------------------------------------
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/1013829.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
