Hello Chris,

On Mon, 2025-03-17 at 11:55 +0100, Chris Hofstaedtler wrote:
> > 
> > I'll try figure out the reason of this failure. Just wanted to keep
> > you
> > informed that the issue is being taken care of.
> 
> You might be workaround this by using an older dupload/dput, which 
> still uses gpg, or maybe by changing the crypto policy [1].
> 
> There might also be a possibility to update your key to use a 
> stronger hash (using sqv). However I don't know what effect this has 
> on your key in the Debian ecosystem.

`dput` has not been kind to me at all. Neither dput nor dput-ng, given
that the issue has something to do with the ftp-mode.


Thankfully I've been able to unblock myself with dupload.

@ dupload --skip-hooks openpgp-check bpfcc_0.31.0+ds-5_source.changes
dupload note: no announcement will be sent.
dupload: warning: skipping pre-upload changes hook
/usr/share/dupload/openpgp-check %1
Checking Debian transitions for bpfcc...
  Ok, not found in any.
Uploading (scpb) to
ssh.upload.debian.org:/srv/upload.debian.org/UploadQueue/
[ Preparing job bpfcc_0.31.0+ds-5_source from bpfcc_0.31.0+ds-
5_source.changes
 bpfcc_0.31.0+ds-5.debian.tar.xz, size ok, md5sum ok, sha1sum ok,
sha256sum ok
 bpfcc_0.31.0+ds-5.dsc, size ok, md5sum ok, sha1sum ok, sha256sum ok
 bpfcc_0.31.0+ds-5_source.buildinfo, size ok, md5sum ok, sha1sum ok,
sha256sum ok
 bpfcc_0.31.0+ds-5_source.changes ok ]
Uploading (scpb) to debian-ssh (ssh.upload.debian.org)
[ Uploading job bpfcc_0.31.0+ds-5_source
 bpfcc_0.31.0+ds-5.debian.tar.xz 22.5 kB, uploading
 bpfcc_0.31.0+ds-5.dsc 2.8 kB, uploading
 bpfcc_0.31.0+ds-5_source.buildinfo 9.3 kB, uploading
 bpfcc_0.31.0+ds-5_source.changes 2.2 kB, uploading
 ]


And this upload was signed after the cleansing of the keys from the
SHA1 algo signatures. So it should be a good test validation if it
passes the ftpmaster's checks.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to