Your message dated Sun, 12 Nov 2023 23:04:13 +0000
with message-id <e1r2juz-008693...@fasolo.debian.org>
and subject line Bug#1048300: fixed in mescc-tools 1.5.2-1
has caused the Debian Bug report #1048300,
regarding mescc-tools: 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 ow...@bugs.debian.org
immediately.)


-- 
1048300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1048300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mescc-tools
Version: 1.4.0-1
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian...@lists.debian.org
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 mescc-tools
> dpkg-buildpackage: info: source version 1.4.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Vagrant Cascadian 
> <vagr...@debian.org>
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean
>    dh_auto_clean
>       make -j8 clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> make[1]: git: No such file or directory
> rm -rf bin/ test/results/
> ./test/test1/cleanup.sh
> ./test/test2/cleanup.sh
> ./test/test3/cleanup.sh
> ./test/test4/cleanup.sh
> ./test/test5/cleanup.sh
> ./test/test6/cleanup.sh
> ./test/test7/cleanup.sh
> ./test/test8/cleanup.sh
> ./test/test9/cleanup.sh
> ./test/test10/cleanup.sh
> ./test/test11/cleanup.sh
> cd Kaem && make clean
> make[2]: Entering directory '/<<PKGBUILDDIR>>/Kaem'
> make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
> rule.
> rm -rf ../bin/
> rm -rf test/results/
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/Kaem'
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_clean
>       rm -f debian/debhelper-build-stamp
>       rm -rf debian/.debhelper/
>       rm -f debian/mescc-tools.debhelper.log
>       rm -f -- debian/mescc-tools.substvars debian/files
>       rm -fr -- debian/mescc-tools/ debian/tmp/
>       find .  \( \( \
>               \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path 
> .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o 
> -type f -a \
>               \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
>                -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
>                -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
>                -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
>               \) -exec rm -f {} + \) -o \
>               \( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) 
> \)
>  dpkg-source -b .
> dpkg-source: warning: upstream signing key but no upstream tarball signature
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building mescc-tools using existing 
> ./mescc-tools_1.4.0.orig-M2libc.tar.gz
> dpkg-source: info: building mescc-tools using existing 
> ./mescc-tools_1.4.0.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  mescc-tools-1.4.0/test/test12/footer.M1
>  mescc-tools-1.4.0/test/test12/hello.hex2
>  mescc-tools-1.4.0/test/test13/hello.hex2
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/mescc-tools_1.4.0-1.diff.SLaUAB
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . 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/mescc-tools_1.4.0-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 ---
Source: mescc-tools
Source-Version: 1.5.2-1
Done: Vagrant Cascadian <vagr...@debian.org>

We believe that the bug you reported is fixed in the latest version of
mescc-tools, 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 1048...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vagrant Cascadian <vagr...@debian.org> (supplier of updated mescc-tools 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 12 Nov 2023 14:41:02 -0800
Source: mescc-tools
Architecture: source
Version: 1.5.2-1
Distribution: unstable
Urgency: medium
Maintainer: Vagrant Cascadian <vagr...@debian.org>
Changed-By: Vagrant Cascadian <vagr...@debian.org>
Closes: 1048300
Changes:
 mescc-tools (1.5.2-1) unstable; urgency=medium
 .
   * New upstream version 1.5.2.
   * debian/patches: Run cleanup.sh for test12 and test13.
     (Closes: #1048300)
Checksums-Sha1:
 5727ba1652df0b277262e0042f77913ba932b015 1557 mescc-tools_1.5.2-1.dsc
 419a06e4b3227af72088619cac54952a7d8bed2a 174747 mescc-tools_1.5.2.orig.tar.gz
 d449c164c147e10e8510acfc881605d2a42664b9 228 mescc-tools_1.5.2.orig.tar.gz.asc
 b5b255c223b0b2ecd38becc7c7813886ac97a4bc 22608 
mescc-tools_1.5.2-1.debian.tar.xz
 b933fd362531e80ca957e415632815087c2b6518 5593 
mescc-tools_1.5.2-1_arm64.buildinfo
Checksums-Sha256:
 edcffc8573ec2443754ef0ed696a18a01fa7891f2e96f8a886e293abfb689013 1557 
mescc-tools_1.5.2-1.dsc
 936c186cb35ab2e2d1ab4dc11bf0d727248d69b28ebfdb1a920b2dd55f3053c9 174747 
mescc-tools_1.5.2.orig.tar.gz
 78d6851ad59c871983710fe0560b2eeae0a0bf2f2305c87fb32a771a559a8a90 228 
mescc-tools_1.5.2.orig.tar.gz.asc
 62653853d8f1bcd351526bdac2d23da29bea4c5f3652ab827827f6fd01d9c45a 22608 
mescc-tools_1.5.2-1.debian.tar.xz
 340a35a588aa4d72e856e6e1a3bf52e87e722c48bc88e379ab106d06630a2c9f 5593 
mescc-tools_1.5.2-1_arm64.buildinfo
Files:
 0f8d3c80760cdad5eb28851305c2d806 1557 devel optional mescc-tools_1.5.2-1.dsc
 f82dd9054cfab08b5d50f4a0deb71357 174747 devel optional 
mescc-tools_1.5.2.orig.tar.gz
 77c13c429c979ef2483775d35f9b990c 228 devel optional 
mescc-tools_1.5.2.orig.tar.gz.asc
 501438dff9bc582df66298077004c6df 22608 devel optional 
mescc-tools_1.5.2-1.debian.tar.xz
 e7586647f5b60611fbeb586b1acabe41 5593 devel optional 
mescc-tools_1.5.2-1_arm64.buildinfo

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

iIkEARYKADEWIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCZVFWJhMcdmFncmFudEBk
ZWJpYW4ub3JnAAoJENxRj8h/lxaqTbcA/0LmC6tjY8VDeUhe+zam76ast9B99QE7
l5uM2NXOPJiXAQCaURJ0SKnymhVyINcAfZWnrZcTAL6Z9hKSINV3ygHADg==
=VQ2L
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to