usbdux xenial submissions won't be built

Asked by Bernd Porr

I've uploaded new versions of my software to:
https://launchpad.net/~berndporr/+archive/ubuntu/usbdux/+index
for xenial. However they have never been built even that it's now a couple of weeks ago. When I try to upload them again dput reports that they have already been uploaded.
The software in question is: iir1 and comedirecord.

Question information

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

Your uploads were rejected because we couldn't verify the public key. I can't tell at this point whether that was a transient keyserver failure or whether there's some more permanent failure.

dput's message saying that they've already been uploaded is purely a local check. I suggest using "dput -f" to try uploading again and see if it works this time. We normally send an email acknowledgement within a few minutes of an upload if it passes a signature check.

Revision history for this message
Bernd Porr (berndporr) said :
#2

I've tried this now a couple of times and there is just no feedback at all.

Now, I have deleted all keys I had about and created a new one.

Used the commandline:

gpg --send-keys --keyserver keyserver.ubuntu.com XXXXXXXX

gpg --recv-keys --keyserver keyserver.ubuntu.com XXXXXXXX
gpg: requesting key XXXXXXXX from hkp server keyserver.ubuntu.com
gpg: key XXXXXXX: "Bernd Porr <email address hidden>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1

bp1@bp1-Precision-WorkStation-T5400:~/sandbox$ dput ppa:berndporr/usbdux iir1_1.0-0xenial_source.changes
Checking signature on .changes
gpg: Signature made Tue 20 Sep 2016 23:43:21 BST using RSA key ID FD6A5C3B
gpg: Good signature from "Bernd Porr <email address hidden>"
Good signature on /home/bp1/sandbox/iir1_1.0-0xenial_source.changes.
Checking signature on .dsc
gpg: Signature made Tue 20 Sep 2016 23:43:21 BST using RSA key ID FD6A5C3B
gpg: Good signature from "Bernd Porr <email address hidden>"
Good signature on /home/bp1/sandbox/iir1_1.0-0xenial.dsc.
Uploading to ppa (via ftp to ppa.launchpad.net):
  Uploading iir1_1.0-0xenial.dsc: done.
  Uploading iir1_1.0-0xenial.tar.gz: done.
  Uploading iir1_1.0-0xenial_source.changes: done.
Successfully uploaded packages.
bp1@bp1-Precision-WorkStation-T5400:~/sandbox$

I'm still waiting for a confirmation e-mail from ppa.

Revision history for this message
Bernd Porr (berndporr) said :
#3

ps: I've also used the -f option. Still no ppa generated.

Revision history for this message
William Grant (wgrant) said :
#4

Generating a new key won't do any good if Launchpad has no idea that the key is yours! Visit https://launchpad.net/~/+editpgpkeys and add the new key's fingerprint, then try uploading again.

Revision history for this message
Bernd Porr (berndporr) said :
#5

"To start using an OpenPGP key with your Launchpad account, simply paste its fingerprint below. The key must be registered with the Ubuntu key server. (How to get the fingerprint)"

...which I've done a month ago and nothing happened. Turns out I _first_ need to submit it to the keyserver and _then_ use this web page. The web page doesn't mention that.

To save other long time sufferers the time I've spent on it, here is the recipe:

1) Generate your keys: gpg --gen-key
2) Upload the key to the ubuntu keyserver: gpg --send-keys --keyserver keyserver.ubuntu.com YOURKEYHERE
3) Check that it has arrived: gpg --recv-keys --keyserver keyserver.ubuntu.com YOURKEYHERE
4) Get the fingerprint: gpg --fingerprint
5) Go to https://launchpad.net/~/+editpgpkeys and enter your fingerprint there
6) You get an e-mail from launchpad which is encrypted with the pgp key
7) Install enigmail or another plugin so that it can decrypt your e-mail from launchpad (point it to /usr/bin/gpg2).
8) You should see now the decrypted e-mail. Click on the link in the decrypted e-mail pointing to launchpad.
9) that's it.

Revision history for this message
Bernd Porr (berndporr) said :
#6

...ooops! and it's actually in the text. ;)