Your message dated Wed, 16 Aug 2023 13:47:38 +0200
with message-id <[email protected]>
and subject line Re: Bug#1049697: mupdf: Fails to build binary packages again
after successful build
has caused the Debian Bug report #1049697,
regarding mupdf: 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.)
--
1049697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049697
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mupdf
Version: 1.22.2+ds1-1
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 mupdf
> dpkg-buildpackage: info: source version 1.22.2+ds1-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Kan-Ru Chen (é³ä¾å¦)
> <[email protected]>
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> dpkg-source: info: using options from mupdf-1.22.2+ds1/debian/source/options:
> --extend-diff-ignore=(^|/)(source/pdf/cmaps/|generated/resources/fonts/urw/|thirdparty/extract/test/)
> debian/rules clean
> dh clean
> debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> rm -rf build
> rm -rf generated
> rm -rf source/pdf/cmaps
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_clean
> debian/rules binary
> dh binary
> dh_update_autotools_config
> dh_autoreconf
> dh_auto_configure
> debian/rules override_dh_auto_build
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> debian/replace-fonts.sh
> ln: failed to create symbolic link
> 'resources/fonts/droid/DroidSansFallback.ttf': File exists
> ln: failed to create symbolic link
> 'resources/fonts/droid/DroidSansFallbackFull.ttf': File exists
> make[1]: *** [debian/rules:51: override_dh_auto_build] Error 1
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> make: *** [debian/rules:75: binary] Error 2
> dpkg-buildpackage: error: debian/rules binary 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/mupdf_1.22.2+ds1-1_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 ---
Version: 1.22.2+ds1-2
--- End Message ---
