$ dput ubuntu ../s390-tools-signed_2.33.1-0ubuntu4_source.changes
Uploading s390-tools-signed using ftp to ubuntu (host: upload.ubuntu.com; directory: /ubuntu)
running supported-distribution: check whether the target distribution is currently supported (using distro-info)
{'allowed': ['release', 'proposed', 'backports', 'security'], 'known': ['release', 'proposed', 'updates', 'backports', 'security']}
running required-fields: check whether a field is present and non-empty in the changes file
running checksum: verify checksums before uploading
running suite-mismatch: check the target distribution for common errors
running check-debs: makes sure the upload contains a binary package
running gpg: check GnuPG signatures before the upload
Uploading s390-tools-signed_2.33.1-0ubuntu4.dsc
Uploading s390-tools-signed_2.33.1-0ubuntu4.tar.xz
Uploading s390-tools-signed_2.33.1-0ubuntu4_source.buildinfo
Uploading s390-tools-signed_2.33.1-0ubuntu4_source.changes
Thank you, Frank. And no worries. :)
I've sponsored s390-tools-signed, too, now.
$ dput ubuntu ../s390- tools-signed_ 2.33.1- 0ubuntu4_ source. changes distribution: check whether the target distribution is currently supported (using distro-info) signed_ 2.33.1- 0ubuntu4. dsc signed_ 2.33.1- 0ubuntu4. tar.xz signed_ 2.33.1- 0ubuntu4_ source. buildinfo signed_ 2.33.1- 0ubuntu4_ source. changes
Uploading s390-tools-signed using ftp to ubuntu (host: upload.ubuntu.com; directory: /ubuntu)
running supported-
{'allowed': ['release', 'proposed', 'backports', 'security'], 'known': ['release', 'proposed', 'updates', 'backports', 'security']}
running required-fields: check whether a field is present and non-empty in the changes file
running checksum: verify checksums before uploading
running suite-mismatch: check the target distribution for common errors
running check-debs: makes sure the upload contains a binary package
running gpg: check GnuPG signatures before the upload
Uploading s390-tools-
Uploading s390-tools-
Uploading s390-tools-
Uploading s390-tools-