Your message dated Mon, 25 May 2026 14:35:05 +0000
with message-id <[email protected]>
and subject line Bug#1049132: fixed in ruby-rbnacl 7.1.2-3
has caused the Debian Bug report #1049132,
regarding ruby-rbnacl: 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.)


-- 
1049132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049132
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ruby-rbnacl
Version: 7.1.1-1
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 ruby-rbnacl
> dpkg-buildpackage: info: source version 7.1.1-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Unit 193 <[email protected]>
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean --buildsystem=ruby --with ruby
>    dh_auto_clean -O--buildsystem=ruby
>       dh_ruby --clean
> W: XS-Ruby-Versions is deprecated, and will be ignored
>    dh_autoreconf_clean -O--buildsystem=ruby
>    dh_clean -O--buildsystem=ruby
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building ruby-rbnacl using existing 
> ./ruby-rbnacl_7.1.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: newly created empty file 
> 'coverage/.resultset.json.lock' will not be represented in diff
> dpkg-source: info: local changes detected, the modified files are:
>  ruby-rbnacl-7.1.1/coverage/.last_run.json
>  ruby-rbnacl-7.1.1/coverage/.resultset.json
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/ruby-rbnacl_7.1.1-1.diff.ENIbaG
> 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/ruby-rbnacl_7.1.1-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: ruby-rbnacl
Source-Version: 7.1.2-3
Done: Sruthi Chandran <[email protected]>

We believe that the bug you reported is fixed in the latest version of
ruby-rbnacl, 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.
Sruthi Chandran <[email protected]> (supplier of updated ruby-rbnacl 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: SHA512

Format: 1.8
Date: Mon, 25 May 2026 19:00:07 +0530
Source: ruby-rbnacl
Architecture: source
Version: 7.1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 
<[email protected]>
Changed-By: Sruthi Chandran <[email protected]>
Closes: 1049132
Changes:
 ruby-rbnacl (7.1.2-3) unstable; urgency=medium
 .
   * Team upload
   * Use d/clean to remove unnecessary files created during build
     (Closes: #1049132)
   * Bump Standards-Version to 4.7.4 (no changes needed)
   * Update watch file version
Checksums-Sha1:
 4b6d6ee1cea303044ca7bbebdc48227a56e4f2df 1869 ruby-rbnacl_7.1.2-3.dsc
 59e763712439b9b352cf98db95a2679da6bed041 4612 ruby-rbnacl_7.1.2-3.debian.tar.xz
 d5b8eda40457304c8ea542e60691cf46a0f84502 7189 
ruby-rbnacl_7.1.2-3_amd64.buildinfo
Checksums-Sha256:
 d8bd60648ef97bba85378c6dee03c8c0a194dfa896ae99bbb82d1bbccc1d020e 1869 
ruby-rbnacl_7.1.2-3.dsc
 2395e4b0c3bfbdbece5aa1c0deb03a617eaab3d48cdd10eb3aa5b5878a3025e7 4612 
ruby-rbnacl_7.1.2-3.debian.tar.xz
 aa1ba76728dff63a4302eba45a3bf02852a897babd4a47e9cc1eeb43831b2e11 7189 
ruby-rbnacl_7.1.2-3_amd64.buildinfo
Files:
 6297221c4d21406d3d19ed2f53cf8a9b 1869 ruby optional ruby-rbnacl_7.1.2-3.dsc
 01facdf43d2399b2dbc3670a1ff67079 4612 ruby optional 
ruby-rbnacl_7.1.2-3.debian.tar.xz
 4ceb2f33db0f925125cff147f2c25c38 7189 ruby optional 
ruby-rbnacl_7.1.2-3_amd64.buildinfo

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

iQGzBAEBCgAdFiEEcd3Fxr6GmkZB13n+x+ob4VdN7V0FAmoUWaUACgkQx+ob4VdN
7V0d9gv/aHtUjeO8dJR9haCfpTa+swG/nQnrQXZB9CiggBk/jvXTPDFr3FOGvJsy
2hnOFFvcC5X97igqcdbB29aXIj/d79b4GTTH7ap7f/ZJyWn+pZosHzQ8Hr0PAkMF
f84BbMBg/HuoHZTKajCUPmN3NgQYSn29+RgJmCxWgCGd4FDwqZS78NLQhAd3kDMo
baCuYncTP7M23c6o49lWSdZjY/Zy1dliglrDkYW8tlPrnI4s3Pu8SlfWOariB9nE
oGwF5Xj6CGspn8kuE9o/gTm5DCZPccEGfKKSt1YDDtHZxHpgaTFAAj5Udeqz+Sd8
hKz8mlKBz9GQVbk0v1Zmq6zaB/QtnuOiOraFotTjj5mwMIXjQG2bbiKpkVmIdXFa
S9E8gnOUnl3LWNO0QxJeE05wZKxyJg3chefWgxjgWt2hKlSU0r+wPnUHZyd+GL0d
YVAOsGUJscpK9OYs7Az63CPZ+oP5DhOOg3ikvZbkphMpcCiEnHsO8jR9pHYgdiQp
efP49c1s
=O5Vr
-----END PGP SIGNATURE-----

Attachment: pgprFemfAY9vp.pgp
Description: PGP signature


--- End Message ---

Reply via email to