Re: delayed argument errors from dput

[Matthew Fernandez <matthew.fernandez@gmail.com>]

On 6/15/24 10:12, Soren Stoutner wrote:
> What is the content of your ~/.dput.cf?  It is possible that you can an entry
> there that is causing this behavior.

  [mentors]
    fqdn = mentors.debian.net
    incoming = /upload
    method = https
    allow_unsigned_uploads = 0
    progress_indicator = 2
    allowed_distributions = .*

> On Friday, June 14, 2024 4:27:27 PM MST Matthew Fernandez wrote:
> > On 6/15/24 09:26, Matthew Fernandez wrote:
> > > Hello mentors,
> > >
> > > I am getting the following behaviour when trying to upload to mentors:
> > >     $ dput mentors ../rumur_2024.05.07-1_source.changes
> > >     Checking signature on .changes
> > >     gpg: ../rumur_2024.05.07-1_source.changes: Valid signature from
> > >
> > > A44D25C91888A6A4
> > >
> > >     Checking signature on .dsc
> > >     gpg: ../rumur_2024.05.07-1.dsc: Valid signature from A44D25C91888A6A4
> > >     Incorrect delayed argument: ValueError: delayed days value must be a
> > >
> > > decimal integer:
> > >     $ dput --version
> > >     dput 1.2
> > >     $ gpg --version
> > >     gpg (GnuPG) 2.2.43
> > >     libgcrypt 1.10.3
> > >     …
> > >
> > > dput seems to somehow think I’m passing --delayed with an argument of…
> > > nothing? Searching these error messages or fragments thereof turns up no
> > > clues on the internet. Does anyone have a guess/explanation of what’s
> > > going on here?
> >
> > FTR, manually passing --delayed=0 bypasses this error. But I’m still
> > unclear what is happening here.