Well.. considering this is a SRU, we should probably not fix the memory-leak within this bug but restrict ourselves to the minimal required change, as provided here.
Also, checking out the upstream github repo shows a 664 filemode for curl.* so that must have been a hiccup on my side.
So LGTM after all!
$ dput ubuntu ../s390-tools_2.12.0-0ubuntu3.4_source.changes
D: Setting host argument.
Checking signature on .changes
gpg: ../s390-tools_2.12.0-0ubuntu3.4_source.changes: Valid signature from 5889C17AB1C8D890
Checking signature on .dsc
gpg: ../s390-tools_2.12.0-0ubuntu3.4.dsc: Valid signature from 5889C17AB1C8D890
Uploading to ubuntu (via sftp to upload.ubuntu.com):
Uploading s390-tools_2.12.0-0ubuntu3.4.dsc: done.
Uploading s390-tools_2.12.0-0ubuntu3.4.debian.tar.xz: done.
Uploading s390-tools_2.12.0-0ubuntu3.4_source.buildinfo: done.
Uploading s390-tools_2.12.0-0ubuntu3.4_source.changes: done.
Successfully uploaded packages.
Well.. considering this is a SRU, we should probably not fix the memory-leak within this bug but restrict ourselves to the minimal required change, as provided here.
Also, checking out the upstream github repo shows a 664 filemode for curl.* so that must have been a hiccup on my side.
So LGTM after all!
$ dput ubuntu ../s390- tools_2. 12.0-0ubuntu3. 4_source. changes tools_2. 12.0-0ubuntu3. 4_source. changes: Valid signature from 5889C17AB1C8D890 tools_2. 12.0-0ubuntu3. 4.dsc: Valid signature from 5889C17AB1C8D890 2.12.0- 0ubuntu3. 4.dsc: done. 2.12.0- 0ubuntu3. 4.debian. tar.xz: done. 2.12.0- 0ubuntu3. 4_source. buildinfo: done. 2.12.0- 0ubuntu3. 4_source. changes: done.
D: Setting host argument.
Checking signature on .changes
gpg: ../s390-
Checking signature on .dsc
gpg: ../s390-
Uploading to ubuntu (via sftp to upload.ubuntu.com):
Uploading s390-tools_
Uploading s390-tools_
Uploading s390-tools_
Uploading s390-tools_
Successfully uploaded packages.