Bug#1089632: dgit: --delayed not passed through to dput-ng

2024-12-10 Thread Ian Jackson
Control: tag -1 confirmed Control: severity -1 serious Ian Jackson writes ("Re: Bug#1089632: dgit: --delayed not passed through to dput-ng"): > $ dgit --damp-run --delayed=5 push-source > ... > # dput --delayed=5 ftp-master '../bpd/dgit_12.1~WRONG_source.changes' &g

Bug#1089632: dgit: --delayed not passed through to dput-ng

2024-12-10 Thread Chris Hofstaedtler
On Tue, Dec 10, 2024 at 05:03:26PM +0800, Sean Whitton wrote: [..] > signfile changes ../libsoup2.4_2.74.3-8.1_source.changes > 8DC2487E51ABDD90B5C4753F0F56D0553B6D411B > > Successfully signed dsc, changes files > Uploading libsoup2.4 using sftp to ssh-upload (host: > ssh.upl

Bug#1089632: dgit: --delayed not passed through to dput-ng

2024-12-10 Thread Ian Jackson
Sean Whitton writes ("Bug#1089632: dgit: --delayed not passed through to dput-ng"): > Package: dgit > Version: 12.0 > Severity: important > > An NMU I did today with --delayed=5 hit unstable immediately. How unfortunate. > The only thing that I can think is that

Bug#1089632: dgit: --delayed not passed through to dput-ng

2024-12-10 Thread Sean Whitton
Package: dgit Version: 12.0 Severity: important An NMU I did today with --delayed=5 hit unstable immediately. The only thing that I can think is that I use dput-ng and dgit only knows how to pass --delayed to dput? But I'm surprised this hasn't come up before, if it's that. Or could it be that