Your message dated Sun, 15 Feb 2026 15:09:26 +0000 with message-id <[email protected]> and subject line Re: Bug#1127666: how to recover from intermittent SSH push.dgit.d.o issue? has caused the Debian Bug report #1127666, regarding how to recover from intermittent SSH push.dgit.d.o issue? 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.) -- 1127666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127666 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: dgit Version: 14.7~bpo13+1 I wanted to do a NEW upload so I built a package and ran this: jas@frallan:~/dpkg/golang-filippo-nistec$ dgit push-built --new -Cgolang-filippo-nistec_0.0.4-2_amd64.changes Format `3.0 (quilt)', need to check/update patch stack canonical suite name for unstable is sid kex_exchange_identification: read: Connection reset by peer Connection reset by 82.195.75.78 port 22 dgit: failed command: ssh '[email protected]' ': dgit debian git-check golang-filippo-nistec ; set -e; cd /dgit/debian/repos; if test -d golang-filippo-nistec.git; then echo 1; else echo 0; fi' dgit: error: subprocess failed with error exit status 255 ! Push failed, while checking state of the archive. ! You can retry the push, after fixing the problem, if you like. jas@frallan:~/dpkg/golang-filippo-nistec$ I retried and got the same error, then retried again and got this: jas@frallan:~/dpkg/golang-filippo-nistec$ dgit push-built --new -Cgolang-filippo-nistec_0.0.4-2_amd64.changes Format `3.0 (quilt)', need to check/update patch stack canonical suite name for unstable is sid no version available from the archive nothing quilty to commit, ok. checking that golang-filippo-nistec_0.0.4-2.dsc corresponds to HEAD dpkg-source: varning: extraherar osignerat källkodspaket (/home/jas/dpkg/golang-filippo-nistec/../golang-filippo-nistec_0.0.4-2.dsc) dpkg-source: info: extraherar golang-filippo-nistec i unpacked dpkg-source: info: packar upp golang-filippo-nistec_0.0.4.orig.tar.gz dpkg-source: info: packar upp golang-filippo-nistec_0.0.4-2.debian.tar.xz kex_exchange_identification: read: Connection reset by peer Connection reset by 82.195.75.78 port 22 dgit: failed command: ssh '[email protected]' ': dgit debian policy-client-query golang-filippo-nistec tainted-objects sid ; true' dgit: error: subprocess failed with error exit status 255 ! Push failed, while preparing your push. ! You can retry the push, after fixing the problem, if you like. jas@frallan:~/dpkg/golang-filippo-nistec$ So I retried again: jas@frallan:~/dpkg/golang-filippo-nistec$ dgit push-built --new -Cgolang-filippo-nistec_0.0.4-2_amd64.changes Format `3.0 (quilt)', need to check/update patch stack canonical suite name for unstable is sid no version available from the archive nothing quilty to commit, ok. checking that golang-filippo-nistec_0.0.4-2.dsc corresponds to HEAD dpkg-source: varning: extraherar osignerat källkodspaket (/home/jas/dpkg/golang-filippo-nistec/../golang-filippo-nistec_0.0.4-2.dsc) dpkg-source: info: extraherar golang-filippo-nistec i unpacked dpkg-source: info: packar upp golang-filippo-nistec_0.0.4.orig.tar.gz dpkg-source: info: packar upp golang-filippo-nistec_0.0.4-2.debian.tar.xz History contains tainted commit 089445ef0355a294a39643e8f4d476fd88844fb5 Taint recorded at time 2026-02-11 00:43:10 Z for any package Reason: tag archive/debian/0.0.4-1 referred to this object in git tree but all previously pushed versions were found to have been removed from NEW (ie, rejected) (or never arrived) Could perhaps be forced using --deliberately. Consult documentation. History contains tainted commit 089445ef0355a294a39643e8f4d476fd88844fb5 Taint recorded at time 2026-02-11 00:43:10 Z for any package Reason: tag debian/0.0.4-1 referred to this object in git tree but all previously pushed versions were found to have been removed from NEW (ie, rejected) (or never arrived) Could perhaps be forced using --deliberately. Consult documentation. dgit: error: pushing tainted objects (which server would reject) ! Push failed, while preparing your push. ! You can retry the push, after fixing the problem, if you like. jas@frallan:~/dpkg/golang-filippo-nistec$ I'm not sure if the --deliberately suggestion was targetted at me, but it didn't work: jas@frallan:~/dpkg/golang-filippo-nistec$ dgit push-built --new -Cgolang-filippo-nistec_0.0.4-2_amd64.changes --deliberately dgit: unknown long option `--deliberately' As far as I can tell, the package is now stuck. How would I recover from this situation and upload using dgit? Meanwhile I reverted to debsign+dput, but wanted to report this to have a solution for next time. /Simon
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Simon Josefsson writes ("Bug#1127666: how to recover from intermittent SSH push.dgit.d.o issue?"): > I wanted to do a NEW upload so I built a package and ran this: Thanks for this report. As discussed, it showed a number of things going wrong: > jas@frallan:~/dpkg/golang-filippo-nistec$ dgit push-built --new > -Cgolang-filippo-nistec_0.0.4-2_amd64.changes > Format `3.0 (quilt)', need to check/update patch stack > canonical suite name for unstable is sid > kex_exchange_identification: read: Connection reset by peer > Connection reset by 82.195.75.78 port 22 > dgit: failed command: ssh '[email protected]' ': dgit debian > git-check golang-filippo-nistec ; set -e; cd /dgit/debian/repos; if test -d > golang-filippo-nistec.git; then echo 1; else echo 0; fi' > > dgit: error: subprocess failed with error exit status 255 > ! Push failed, while checking state of the archive. > ! You can retry the push, after fixing the problem, if you like. > jas@frallan:~/dpkg/golang-filippo-nistec$ This was a transient ssh failure (due to attacks on the dgit git server's ssh port). DSA have made some configuration changes here which we think may help. [rt.debian.org #9945] > History contains tainted commit 089445ef0355a294a39643e8f4d476fd88844fb5 > Taint recorded at time 2026-02-11 00:43:10 Z for any package > Reason: tag debian/0.0.4-1 referred to this object in git tree but all > previously pushed versions were found to have been removed from NEW (ie, > rejected) (or never arrived) > Could perhaps be forced using --deliberately. Consult documentation. This message was unhelpful. We have improved it. (dgit 14.8, which is not yet deployed but will be in the forthcoming weeks.) > How would I recover from this situation and upload using dgit? You probably wanted --deliberately-include-questionable-history. The new output will make more helpful suggestions. (We also have #1127470 which is a request for this to be conveniently available from git-debpush.) In another case we saw that if you use that --deliberately option, the output is incorrect. That's #1127378, which is likewise fixed in 14.8 but not yet deployed. I think therefore that everything in this bug report has been dealt with, or is recorded elsewhere, so I'm closing it. Thanks, Ian. -- Ian Jackson <[email protected]> These opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
--- End Message ---
