Your message dated Tue, 19 Nov 2024 10:44:29 -0500
with message-id <[email protected]>
and subject line fixed in shaarli 0.13.0+dfsg-1
has caused the Debian Bug report #1049647,
regarding shaarli: Fails to build binary packages again after successful build
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.)
--
1049647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049647
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: shaarli
Version: 0.12.1+dfsg-8
Severity: minor
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build
User: [email protected]
Usertags: qa-doublebuild
Hi,
This package fails to do build a binary-only build (not source) after a
successful build (dpkg-buildpackage ; dpkg-buildpackage -b).
This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.
More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/DoubleBuild
Relevant part of the build log:
> cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env
> -us -uc -rfakeroot -b
> ---------------------------------------------------------------------------------------------------------------------------
>
> dpkg-buildpackage: info: source package shaarli
> dpkg-buildpackage: info: source version 0.12.1+dfsg-8
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by James Valleroy
> <[email protected]>
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --with apache2 --with phpcomposer
> dh_auto_clean
> make -j8 clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_clean
> rm -f debian/debhelper-build-stamp
> rm -rf debian/.debhelper/
> rm -f -- debian/shaarli.substvars debian/shaarli.postinst.debhelper
> debian/shaarli.postrm.debhelper debian/shaarli.prerm.debhelper
> ./.phpunit.result.cache ./assets/default/css ./autoload.php debian/files
> rm: cannot remove './assets/default/css': Is a directory
> dh_clean: error: rm -f -- debian/shaarli.substvars
> debian/shaarli.postinst.debhelper debian/shaarli.postrm.debhelper
> debian/shaarli.prerm.debhelper ./.phpunit.result.cache ./assets/default/css
> ./autoload.php debian/files returned exit code 1
> make: *** [debian/rules:5: clean] Error 25
> dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2
>
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage
> --sanitize-env -us -uc -rfakeroot -b' failed to run.
The full build log is available from:
http://qa-logs.debian.net/2023/08/16/shaarli_0.12.1+dfsg-8_unstable.log
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Package: src:shaarli
Version: 0.13.0+dfsg-1
This was fixed with the following change:
* d/clean: Specify css directory
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
