Your message dated Thu, 20 Feb 2025 13:04:49 +0000
with message-id <[email protected]>
and subject line Bug#1046610: fixed in yaws 2.2.0+dfsg-2
has caused the Debian Bug report #1046610,
regarding yaws: Fails to build source 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.)


-- 
1046610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1046610
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: yaws
Version: 2.1.1+dfsg-2
Severity: minor
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: [email protected]
Usertags: qa-doublebuild

Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

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/SourceAfterBuild

Relevant part of the build log:
> cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
> -us -uc -rfakeroot -S
> --------------------------------------------------------------------------------------------------------------------
> 
> dpkg-buildpackage: info: source package yaws
> dpkg-buildpackage: info: source version 2.1.1+dfsg-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Sergei Golovan 
> <[email protected]>
>  dpkg-source --before-build .
>  fakeroot debian/rules clean
> dh clean
>    debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_testdir
> dh_testroot
> #
> # Clean up applications included into yaws distribution
> [ ! -f Makefile ] || \
> for appdir in applications/* ; do \
>     (cd $appdir ; \
>      /usr/bin/make clean || exit 1 ; \
>      /usr/bin/make cleandocs || exit 1) \
> done
> make[2]: Entering directory '/<<PKGBUILDDIR>>/applications/chat'
> Making clean in src
> make[3]: Entering directory '/<<PKGBUILDDIR>>/applications/chat/src'
> rm -rf .libs _libs
> rm -f ./../ebin/chat.beam
> rm -f *.lo
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/applications/chat/src'
> Making clean in ebin
> make[3]: Entering directory '/<<PKGBUILDDIR>>/applications/chat/ebin'
> rm -rf .libs _libs
> rm -f *.beam
> rm -f *.lo
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/applications/chat/ebin'
> make[3]: Entering directory '/<<PKGBUILDDIR>>/applications/chat'
> rm -rf .libs _libs
> rm -f *.lo
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/applications/chat'
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/applications/chat'
> make[2]: Entering directory '/<<PKGBUILDDIR>>/applications/chat'
> make[2]: *** No rule to make target 'cleandocs'.  Stop.
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/applications/chat'
> make[2]: Entering directory '/<<PKGBUILDDIR>>/applications/mail'
> Making clean in src
> make[3]: Entering directory '/<<PKGBUILDDIR>>/applications/mail/src'
> rm -rf .libs _libs
> rm -f ./../ebin/mail.beam ./../ebin/attachment.beam ./../ebin/smtp.beam 
> ./../ebin/mail_html.beam
> rm -f *.lo
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/applications/mail/src'
> Making clean in ebin
> make[3]: Entering directory '/<<PKGBUILDDIR>>/applications/mail/ebin'
> rm -rf .libs _libs
> rm -f *.beam
> rm -f *.lo
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/applications/mail/ebin'
> make[3]: Entering directory '/<<PKGBUILDDIR>>/applications/mail'
> rm -rf .libs _libs
> rm -f *.lo
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/applications/mail'
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/applications/mail'
> make[2]: Entering directory '/<<PKGBUILDDIR>>/applications/mail'
> make[2]: *** No rule to make target 'cleandocs'.  Stop.
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/applications/mail'
> make[2]: Entering directory '/<<PKGBUILDDIR>>/applications/wiki'
> Making clean in src
> make[3]: Entering directory '/<<PKGBUILDDIR>>/applications/wiki/src'
> rm -rf .libs _libs
> rm -f ./../ebin/utils.beam ./../ebin/wiki_diff.beam ./../ebin/wiki.beam 
> ./../ebin/wiki_format_txt.beam ./../ebin/wiki_plugin_backlinks.beam 
> ./../ebin/wiki_plugin_dummy.beam ./../ebin/wiki_plugin_menu.beam 
> ./../ebin/wiki_split.beam ./../ebin/wiki_templates.beam 
> ./../ebin/wiki_to_html.beam ./../ebin/wiki_utils.beam ./../ebin/wiki_yaws.beam
> rm -f *.lo
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/applications/wiki/src'
> Making clean in ebin
> make[3]: Entering directory '/<<PKGBUILDDIR>>/applications/wiki/ebin'
> rm -rf .libs _libs
> rm -f *.beam
> rm -f *.lo
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/applications/wiki/ebin'
> make[3]: Entering directory '/<<PKGBUILDDIR>>/applications/wiki'
> rm -rf .libs _libs
> rm -f *.lo
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/applications/wiki'
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/applications/wiki'
> make[2]: Entering directory '/<<PKGBUILDDIR>>/applications/wiki'
> make[2]: *** No rule to make target 'cleandocs'.  Stop.
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/applications/wiki'
> make[2]: Entering directory '/<<PKGBUILDDIR>>/applications/yapp'
> Making clean in src
> make[3]: Entering directory '/<<PKGBUILDDIR>>/applications/yapp/src'
> rm -rf .libs _libs
> rm -f ./../ebin/yapp.app ./../ebin/yapp.appup ./../ebin/yapp_app.beam 
> ./../ebin/yapp.beam ./../ebin/yapp_ets_server.beam 
> ./../ebin/yapp_event_handler.beam ./../ebin/yapp_handler.beam 
> ./../ebin/yapp_mnesia_server.beam ./../ebin/yapp_registry.beam 
> ./../ebin/yapp_server.beam ./../ebin/yapp_sup.beam
> rm -f *.lo
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/applications/yapp/src'
> Making clean in ebin
> make[3]: Entering directory '/<<PKGBUILDDIR>>/applications/yapp/ebin'
> rm -rf .libs _libs
> rm -f yapp.app yapp.appup *.beam
> rm -f *.lo
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/applications/yapp/ebin'
> make[3]: Entering directory '/<<PKGBUILDDIR>>/applications/yapp'
> rm -rf .libs _libs
> rm -rf doc
> rm -f *.lo
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/applications/yapp'
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/applications/yapp'
> make[2]: Entering directory '/<<PKGBUILDDIR>>/applications/yapp'
> make[2]: *** No rule to make target 'cleandocs'.  Stop.
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/applications/yapp'
> make[1]: *** [debian/rules:35: override_dh_auto_clean] Error 1
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> make: *** [debian/rules:28: clean] Error 2
> dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
> exit status 2
> 
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage 
> --sanitize-env -us -uc -rfakeroot -S' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/13/yaws_2.1.1+dfsg-2_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 ---
Source: yaws
Source-Version: 2.2.0+dfsg-2
Done: Sergei Golovan <[email protected]>

We believe that the bug you reported is fixed in the latest version of
yaws, 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.
Sergei Golovan <[email protected]> (supplier of updated yaws 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: Thu, 20 Feb 2025 15:42:17 +0300
Source: yaws
Architecture: source
Version: 2.2.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Erlang Packagers <[email protected]>
Changed-By: Sergei Golovan <[email protected]>
Closes: 1046610 1049496
Changes:
 yaws (2.2.0+dfsg-2) unstable; urgency=medium
 .
   * Fix building source/binary packages after successful build of the
     binary one (closes: #1046610, #1049496).
Checksums-Sha1:
 58106ff947dd6f713d82a995eb393aa292fe81fd 2542 yaws_2.2.0+dfsg-2.dsc
 d660851ea42e2d1a1084e0357ddb079ef347f9b5 28740 yaws_2.2.0+dfsg-2.debian.tar.xz
 67bf4e5bc8546082457f111005c745214f94e82a 12346 
yaws_2.2.0+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 9ce66b1f0fd92f1e9768c5f57d0658825221b18865b7d23a8d9758d0a67d9844 2542 
yaws_2.2.0+dfsg-2.dsc
 7782e85026983f36b8f75d4b20dc32d0db1c706776a08a2abc12f1548965e863 28740 
yaws_2.2.0+dfsg-2.debian.tar.xz
 e61bd721ce35028d289e118ed130ef80607e6efc7b5da0a365e46635619b041a 12346 
yaws_2.2.0+dfsg-2_amd64.buildinfo
Files:
 3ed831a4fa3c280ef8077a332c7e7ecd 2542 httpd optional yaws_2.2.0+dfsg-2.dsc
 e15f8bcc8b604ffd9c8b7abdd1fbeade 28740 httpd optional 
yaws_2.2.0+dfsg-2.debian.tar.xz
 5cae85ab9cce8d6485fdcd86b6d5417c 12346 httpd optional 
yaws_2.2.0+dfsg-2_amd64.buildinfo

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

iQIzBAEBCAAdFiEE/SYPsyDB+ShSnvc4Tyrk60tj54cFAme3JHkACgkQTyrk60tj
54f8zg/6Auju2Htu95+zWWApDi86u14Qaq34VY/bGLjI382m8cohagraIRx78G57
dxIHKW83FrBuw60h+hu/P4OlvHzmBh6XhBzQizYzxfc0kr2wHbfclhNL9MQvFNq5
oTYgz8wmEFwyvz7LqklHx+9hxouVRHj/hOSSjQhuDNwqU+Bl5McsObTx6M0NYXra
4ujMT4+ld88VwKrK2QZNxhAyecw5iJJ+d6I5yHf9zNcOOYTx49EIYucyAty0VeCn
WT3COJz5b1wATRq+g3ryF6PHmkaSBvP69SN8Zz7riZ0uM9qpMNrzw2cgNlQ1VAVQ
oK6a32ZCuQVPCmfJAQl+9SB5+e5tAYiIZ67zT/4ZP++CQfvLQ+DZ/K7E4MOQzbCr
KzcF+mZErPGBAZCEtg+u3XYamGO/gpRr77Jlf27K1Nc0NEaH15QFS8uPWT2wbD2C
7BX1ySRaMY4kjULZ7H1uhQfY6qx0Yt1msQkRsh10+E6CaJHGems1/b8cMJ1WmFXP
ci+T+qmeQbCL9YR4kpkMx169ig8741ScQfqQHfH18j0sjerNmQBevZG/iuYxr4Xc
4Zfie1AcvzNIxz0MGTlG6IkZsfvV86de4RYjl3dsMEH8vNXL3nLdpBh7ylm3qcFk
Mp1VR8KA9dFOidJHMnBgLm7url7VfXT2A2VYH7CzCPFBl3o/08k=
=kB/y
-----END PGP SIGNATURE-----

Attachment: pgpinPPi9KNsW.pgp
Description: PGP signature


--- End Message ---

Reply via email to