Your message dated Mon, 09 Dec 2024 20:38:55 +0000
with message-id <[email protected]>
and subject line Bug#1089376: fixed in lockfile-progs 0.1.20
has caused the Debian Bug report #1089376,
regarding lockfile-progs: Supporting rootless builds by default
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1089376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089376
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: lockfile-progs
Version: 0.1.19+nmu1
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`,
lockfile-progs failed to rebuild.

Log Summary:
-------------------------------------------------------------------------------
[...]

+------------------------------------------------------------------------------+
| Build
                                                                       |
+------------------------------------------------------------------------------+


Unpack source
-------------

Format: 3.0 (native)
Source: lockfile-progs
Binary: lockfile-progs
Architecture: any
Version: 0.1.19+nmu1
Maintainer: Rob Browning <[email protected]>
Standards-Version: 3.9.8
Build-Depends: liblockfile-dev, debhelper (>= 9)
Package-List:
 lockfile-progs deb misc optional arch=any
Checksums-Sha1:
 11fd3b4a27104f050382de1f45cf984f214fe65a 14156 lockfile-
progs_0.1.19+nmu1.tar.xz
Checksums-Sha256:
 a176942f749f034dc42f56798b7aa4636d904b79410ca65c052b63cf3e53dcc2 14156
lockfile-progs_0.1.19+nmu1.tar.xz
Files:
 f257690852b9f3f4df1417ff2c54584c 14156 lockfile-progs_0.1.19+nmu1.tar.xz


gpgv: Signature made Mon Mar 25 21:03:56 2024 UTC
gpgv:                using RSA key 406220C8B8552802378CCE411F5C7A8B45564314
gpgv:                issuer "[email protected]"
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify inline signature for ./lockfile-
progs_0.1.19+nmu1.dsc: no acceptable signature found
dpkg-source: info: extracting lockfile-progs in /<<PKGBUILDDIR>>
dpkg-source: info: unpacking lockfile-progs_0.1.19+nmu1.tar.xz

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 lockfile-progs
dpkg-buildpackage: info: source version 0.1.19+nmu1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Bastian Germann <[email protected]>
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture arm64
 debian/rules clean
dh clean
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   debian/rules override_dh_testdir
make[1]: Entering directory '/<<PKGBUILDDIR>>'
test -f debian/rules
test -f lockfile-progs.c
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_auto_clean
dh_auto_clean: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
        make -j1 distclean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
rm -f lockfile-create lockfile-remove lockfile-touch lockfile-check
rm -f mail-lock mail-unlock mail-touchlock
rm -f *.o *~
rm -rf bin man
rm -rf check
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_clean
dh_clean: warning: Compatibility levels before 10 are deprecated (level
9 in use)
 debian/rules binary
dh binary
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   debian/rules override_dh_testdir
make[1]: Entering directory '/<<PKGBUILDDIR>>'
test -f debian/rules
test -f lockfile-progs.c
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_update_autotools_config
   dh_auto_configure
dh_auto_configure: warning: Compatibility levels before 10 are
deprecated (level 9 in use)
   dh_auto_build
dh_auto_build: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
        make -j1
make[1]: Entering directory '/<<PKGBUILDDIR>>'
cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/
<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -
Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time
-D_FORTIFY_SOURCE=2  -c -o lockfile-progs.o lockfile-progs.c
cc -o lockfile-create -Wl,-z,relro lockfile-progs.o -llockfile
rm -rf bin
mkdir -p bin
cp -a lockfile-create bin
cp -a lockfile-create bin/mail-lock
cd bin && ln lockfile-create lockfile-remove
cd bin && ln lockfile-create lockfile-touch
cd bin && ln lockfile-create lockfile-check
cd bin && ln mail-lock mail-unlock
cd bin && ln mail-lock mail-touchlock
mkdir -p man
cp -a lockfile-progs.1 man
(cd man && ln -sf lockfile-progs.1 lockfile-create.1 && \
           ln -sf lockfile-progs.1 lockfile-remove.1 && \
           ln -sf lockfile-progs.1 lockfile-touch.1 && \
           ln -sf lockfile-progs.1 lockfile-check.1 && \
           ln -sf lockfile-progs.1 mail-lock.1 && \
           ln -sf lockfile-progs.1 mail-unlock.1 && \
           ln -sf lockfile-progs.1 mail-touchlock.1)
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_auto_test
dh_auto_test: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
        make -j1 check
make[1]: Entering directory '/<<PKGBUILDDIR>>'
rm -rf bin
mkdir -p bin
cp -a lockfile-create bin
cp -a lockfile-create bin/mail-lock
cd bin && ln lockfile-create lockfile-remove
cd bin && ln lockfile-create lockfile-touch
cd bin && ln lockfile-create lockfile-check
cd bin && ln mail-lock mail-unlock
cd bin && ln mail-lock mail-touchlock
mkdir -p man
cp -a lockfile-progs.1 man
(cd man && ln -sf lockfile-progs.1 lockfile-create.1 && \
           ln -sf lockfile-progs.1 lockfile-remove.1 && \
           ln -sf lockfile-progs.1 lockfile-touch.1 && \
           ln -sf lockfile-progs.1 lockfile-check.1 && \
           ln -sf lockfile-progs.1 mail-lock.1 && \
           ln -sf lockfile-progs.1 mail-unlock.1 && \
           ln -sf lockfile-progs.1 mail-touchlock.1)
rm -rf check
mkdir check
bin/lockfile-create check/file
bin/lockfile-touch --oneshot check/file
bin/lockfile-check check/file
bin/lockfile-remove check/file
! test -e check/file.lock
bin/lockfile-create --lock-name check/file.lock
bin/lockfile-touch --oneshot --lock-name check/file.lock
bin/lockfile-check --lock-name check/file.lock
bin/lockfile-remove --lock-name check/file.lock
! test -e check/file.lock
bin/lockfile-create --use-pid --lock-name check/file.lock
bin/lockfile-touch --oneshot --lock-name check/file.lock
bin/lockfile-check --use-pid --lock-name check/file.lock
bin/lockfile-remove --lock-name check/file.lock
! test -e check/file.lock
bin/lockfile-create --use-pid --lock-name check/lockfile.no-pid
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_prep
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<<PKGBUILDDIR>>'
install -d debian/lockfile-progs/usr/bin
cp -a bin/* debian/lockfile-progs/usr/bin/
install -d debian/lockfile-progs/usr/share/man/man1
cp -a man/* debian/lockfile-progs/usr/share/man/man1
find debian/lockfile-progs/usr/share/man -type f | xargs gzip -9v
debian/lockfile-progs/usr/share/man/man1/lockfile-progs.1:       60.7% --
replaced with debian/lockfile-progs/usr/share/man/man1/lockfile-progs.1.gz
(cd debian/lockfile-progs/usr/share/man && \
 for file in `find -type l`; \
 do \
   ln -sf lockfile-progs.1.gz ${file}.gz; \
   rm -f ${file}; \
 done)
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_installdocs
dh_installdocs: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
   dh_installchangelogs
dh_installchangelogs: warning: Compatibility levels before 10 are
deprecated (level 9 in use)
   dh_installman
dh_installman: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
   dh_lintian
dh_lintian: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
   dh_perl
   dh_link
dh_link: warning: Compatibility levels before 10 are deprecated (level 9
in use)
   dh_strip_nondeterminism
   dh_compress
dh_compress: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
   debian/rules override_dh_fixperms
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_fixperms
chown :mail debian/lockfile-progs/usr/bin/mail-lock
chown: changing group of 'debian/lockfile-progs/usr/bin/mail-lock':
Operation not permitted
make[1]: *** [debian/rules:31: override_dh_fixperms] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:8: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit
status 2
--------------------------------------------------------------------------------
Build finished at 2024-11-17T09:18:39Z

-------------------------------------------------------------------------------


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/1020429.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.

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: lockfile-progs
Source-Version: 0.1.20
Done: Rob Browning <[email protected]>

We believe that the bug you reported is fixed in the latest version of
lockfile-progs, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rob Browning <[email protected]> (supplier of updated lockfile-progs 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 09 Dec 2024 13:42:32 -0600
Source: lockfile-progs
Architecture: source
Version: 0.1.20
Distribution: unstable
Urgency: medium
Maintainer: Rob Browning <[email protected]>
Changed-By: Rob Browning <[email protected]>
Closes: 1089376
Changes:
 lockfile-progs (0.1.20) unstable; urgency=medium
 .
   * Migrate to debhelper-compat 13.
   * Use .so links and handle manpages via dh_installman.
   * Handle bin via dh_install.
   * Add Vcs fields to debian/control.
   * Remove obsolete TODO file.
   * Include environment CFLAGS.
   * Improve error messages, including messages for orphaned and stale
     locks.
   * Update debian/control Standards-Version to 4.7.0.
   * Set DEB_BUILD_MAINT_OPTIONS to hardening=+all.
   * Set Rules-Requires-Root to yes in debian/control. Root is needed to
     set the mail-lock group to mail. (Closes: 1089376)
   * Add ${misc:Depends} to Depends
Checksums-Sha1:
 78da4313355a43a9f6d1d8f6efa10166cd6f1866 1609 lockfile-progs_0.1.20.dsc
 a0bdf26aad6312ef70d3f98b889649c949fdc785 14460 lockfile-progs_0.1.20.tar.xz
 b768370219751ad76ed0f42f85038dfd2bc2b4df 6197 
lockfile-progs_0.1.20_amd64.buildinfo
Checksums-Sha256:
 f948f47b907f64076668919d4f5e329dad52ba67e1e2fff4c026c349f4f5662f 1609 
lockfile-progs_0.1.20.dsc
 0197e8b7826ce393b0585d345f3dd97e51829aba465a8770b5658837b6d4188c 14460 
lockfile-progs_0.1.20.tar.xz
 14ba93a1f3ac513ad94393f0bc6f5a50f3932001fc6bb03c0edbd803aa383bf1 6197 
lockfile-progs_0.1.20_amd64.buildinfo
Files:
 34eb148557a36ddc3fdf6dde48ff6623 1609 misc optional lockfile-progs_0.1.20.dsc
 ad01caffb03b50ac59b9e1369c9d7022 14460 misc optional 
lockfile-progs_0.1.20.tar.xz
 d64c864a42be7d31d13ef31c3f9ff02e 6197 misc optional 
lockfile-progs_0.1.20_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJJBAEBCAAzFiEEPTFSABe5ruOuhW+97vEWxVpaQvEFAmdXSssVHHJsYkBkZWZh
dWx0dmFsdWUub3JnAAoJEO7xFsVaWkLxpUwQAIJV8yp0XYpcFS6yQWwXVpFbxQ2s
vbcOJAK55VTJVvogBiQSlwfWjkLhOeyG20eEI06X24L4+HY1Pt521wv7v4lUivLv
EXyI/klWl1hjBLY+QZNDbHccC7dClSFHmIBL95XFP9LPNjpa02plbOPweXJVmWlH
vS6EAN+vgH1R9D/BZsh6RRzfuEwW0jfisFau7hjobqvNBWhhNx7jJKSg7ZhFftuB
reaVUoRnDkgH+224Rd8wxcawOpKyYGF4yfps7CkftkPg1KtNVqyZoHDlwm2Jh9cS
nngi5ING+vsKqMzSImW1sUrYHzFk4LAFYjFP8rzpqMwFn0DqqD8kwjOlIAJG2Vq3
nYC16eqF12b1kZgCMDNnxod3Xwhi9eu7U2OhihZaHa65h+RLB+MzcusxeESC5vzw
SfjuxvCaEKSb7lqGlb6zEdXr+ssbT8VtPTJf6cgCBfHABeEc3hHO2uWxQ1L1fgQU
WxbSmqybam7PTZ6IJDuK6frFZhI5YCzHbWZ3q9D+jUPx+JtXLm7/doEk4Tu3zYK7
0vEqfO8Dd5ZdZD09iCexYCjzOPw06IFgzBz9OMyOtlCz53stDlX8AGFM9u0Kxx/T
m6XwHuirllmq0Aw9GDJL4Bf9vQ5rRXVWJbmk6e1xYXDvli7kiNR3MOhuecIG90bx
/PR0TgmXSan8/0Ey
=5vDO
-----END PGP SIGNATURE-----

Attachment: pgpGBaPQXE1FI.pgp
Description: PGP signature


--- End Message ---

Reply via email to