Is PPA uploading working at the moment?

Asked by Sampsa Riikonen

Hi,

Is the PPA uploading system working properly?

I uploaded a package with dput, but I get no email, nothing. The package does not show in launchpad either.

When trying to re-upload, I get:

dput ppa:sampsa-riikonen/valkka valkka_0.6.0-0ubuntu1-xenialppa1_source.changes
Package has already been uploaded to ppa on ppa.launchpad.net
Nothing more to do for valkka_0.6.0-0ubuntu1-xenialppa1_source.changes

Regards,

Sampsa

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Colin Watson
Solved:
Last query:
Last reply:
Revision history for this message
Best Colin Watson (cjwatson) said :
#1

Sometimes this happens because the upload was unsigned, but from looking at our logs, I think we had an internal network problem that caused Launchpad to be unable to fetch public keys from the keyserver between about 14:58 and 15:08 UTC today. You should retry your upload.

The "Package has already been uploaded" check is something that dput does all by itself without consulting Launchpad; so, to retry the upload, add the -f option to dput to make it skip that check.

Revision history for this message
Sampsa Riikonen (sampsa-riikonen) said :
#2

It seems its a signature error .. although I don't understand where it comes from.

...
Finished running lintian.
Now signing changes and any dsc files...
 signfile dsc valkka_0.6.0-0ubuntu1-xenialppa1.dsc Sampsa Riikonen <email address hidden>
 fixup_buildinfo valkka_0.6.0-0ubuntu1-xenialppa1.dsc valkka_0.6.0-0ubuntu1-xenialppa1_source.buildinfo
 signfile buildinfo valkka_0.6.0-0ubuntu1-xenialppa1_source.buildinfo Sampsa Riikonen <email address hidden>
 fixup_changes dsc valkka_0.6.0-0ubuntu1-xenialppa1.dsc valkka_0.6.0-0ubuntu1-xenialppa1_source.changes
 fixup_changes buildinfo valkka_0.6.0-0ubuntu1-xenialppa1_source.buildinfo valkka_0.6.0-0ubuntu1-xenialppa1_source.changes
 signfile changes valkka_0.6.0-0ubuntu1-xenialppa1_source.changes Sampsa Riikonen <email address hidden>

C$ dput -f ppa:sampsa-riikonen/valkka valkka_0.6.0-0ubuntu1-xenialppa1_source.changes
Checking signature on .changes
gpg: /home/sampsa/C/valkka_0.6.0-0ubuntu1-xenialppa1_source.changes: Error checking signature from 284B974E9F5BC7FA: SignatureVerifyError: 0
Checking signature on .dsc
gpg: /home/sampsa/C/valkka_0.6.0-0ubuntu1-xenialppa1.dsc: Error checking signature from 284B974E9F5BC7FA: SignatureVerifyError: 0

This is the key I'm using on launchpad:

pub 4096R/9F5BC7FA 2014-04-04 Sampsa Riikonen <email address hidden>
  Fingerprint=50FA 7384 B890 5A93 B4B2 A2C6 284B 974E 9F5B C7FA

Revision history for this message
Sampsa Riikonen (sampsa-riikonen) said :
#3

Running gpg verify manually:

C$ gpg --verify valkka_0.6.0-0ubuntu1-xenialppa1_source.changes
gpg: Signature made ti 2. lokakuuta 2018 20.04.48 EEST
gpg: using RSA key 50FA7384B8905A93B4B2A2C6284B974E9F5BC7FA
gpg: issuer "<email address hidden>"
gpg: Good signature from "Sampsa Riikonen <email address hidden>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 50FA 7384 B890 5A93 B4B2 A2C6 284B 974E 9F5B C7FA

Is it because of this ..?

Revision history for this message
Sampsa Riikonen (sampsa-riikonen) said :
#4

added default-key and trusted-key to

~/.gnupg/gpg.conf

Now works like charm.

Revision history for this message
Sampsa Riikonen (sampsa-riikonen) said :
#5

Thanks Colin Watson, that solved my question.

Revision history for this message
Ramon fried (ramon-fried) said :
#6

Also worked for me :)