Your message dated Tue, 7 Jul 2026 09:39:26 +0200 with message-id <[email protected]> and subject line Re: Bug#869642: debsign: simplify redundant "Successfully signed $HAVE_SIGNED file" has caused the Debian Bug report #869642, regarding debsign: simplify redundant "Successfully signed $HAVE_SIGNED file" 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.) -- 869642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869642 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: devscripts Version: 2.17.9 Severity: normal Dear Maintainer, * What led up to the situation? As I commented in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863497#18, mutiple resigning causes flood of redundant "Successfully signed $HAVE_SIGNED file". * What exactly did you do (or not do) that was effective (or ineffective)? $ debsign --re-sign multiple .dsc (may be hundred or more) * What was the outcome of this action? debsign prints "Successfully signed dsc, dsc, dsc ... files". If you debsign against 100 dsc at once, debsign prints dsc, dsc, dsc, ... dsc files. (100 dsc!) it's redundant. * What outcome did you expect instead? debsign prints "Successfully signed $N files". -- Package-specific info: --- /etc/devscripts.conf --- --- ~/.devscripts --- DEBSIGN_KEYID=D92025640886D27D14A9EE02D22C1A883455D448 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.utf8, LC_CTYPE=ja_JP.utf8 (charmap=UTF-8), LANGUAGE=ja_JP.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages devscripts depends on: ii dpkg-dev 1.18.24 ii libc6 2.24-12 ii libfile-homedir-perl 1.00-1 ii perl 5.26.0-4 ii python3 3.5.3-3 Versions of packages devscripts recommends: ii apt 1.5~beta1 ii at 3.1.20-3 ii curl 7.52.1-5 ii dctrl-tools 2.24-2+b1 ii debian-keyring 2017.05.28 ii dput 0.12.1 ii equivs 2.0.10 ii fakeroot 1.21-3.1 ii file 1:5.30-1 ii gnupg 2.1.18-8 ii gnupg2 2.1.18-8 ii libdistro-info-perl 0.17 ii libdpkg-perl 1.18.24 ii libencode-locale-perl 1.05-1 ii libgit-wrapper-perl 0.047-1 ii liblist-compare-perl 0.53-1 ii liblwp-protocol-https-perl 6.07-1 ii libsoap-lite-perl 1.20-1 ii liburi-perl 1.71-1 ii libwww-perl 6.15-1 ii licensecheck 3.0.30-1 ii lintian 2.5.52 ii man-db 2.7.6.1-2 ii patch 2.7.5-1+b2 ii patchutils 0.3.4-2 ii python3-debian 0.1.30 ii python3-magic 1:5.30-1 ii python3-unidiff 0.5.4-1 ii sensible-utils 0.0.9+nmu1 ii strace 4.15-2 ii unzip 6.0-21 ii wdiff 1.2.2-2 ii wget 1.19.1-4 ii xz-utils 5.2.2-1.3 Versions of packages devscripts suggests: ii adequate 0.15.1 ii autopkgtest 4.4 pn bls-standalone <none> ii build-essential 12.3 pn check-all-the-things <none> pn cvs-buildpackage <none> pn devscripts-el <none> pn diffoscope <none> pn disorderfs <none> pn dose-extra <none> pn duck <none> pn faketime <none> pn gnuplot <none> ii gpgv 2.1.18-8 pn how-can-i-help <none> ii libauthen-sasl-perl 2.1600-1 ii libfile-desktopentry-perl 0.22-1 pn libnet-smtps-perl <none> pn libterm-size-perl <none> ii libtimedate-perl 2.3000-2 pn libyaml-syck-perl <none> ii mailutils [mailx] 1:3.1.1-1 pn mozilla-devscripts <none> pn mutt <none> ii openssh-client [ssh-client] 1:7.5p1-5 ii piuparts 0.77 ii quilt 0.63-8.1 pn ratt <none> pn reprotest <none> ii svn-buildpackage 0.8.6 ii w3m 0.5.3-34 -- no debconf information
pgpsi9Koc3oGF.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---Version: devscripts/2.26.10 On Tue, Jul 07, 2026 at 12:38:13PM +0900, Kentaro HAYASHI wrote: > Hello, > > Thank you for kindly reminding that issue. > > I've confirmed that that issue was solved in devscripts 2.26.10. Thanks for confirming, closing bug report. -- Agustin
--- End Message ---
