Launchpad itself

How to debug package upload failures without error messages?

Asked by Matt Amos

I've uploaded a new version of a package, but haven't had an email from Launchpad indicating success or failure. I assume there was a problem during uploading, as it hasn't appeared in the builds list under any status. The dput log doesn't indicate any immediate problem:

$ dput ppa:osmadmins/ppa openstreetmap-cgimap_0.5.8-0ubuntu0ppa0~xenial1_source.changes
Checking signature on .changes
gpg: Signature made Thu 03 Nov 2016 12:31:41 GMT using RSA key ID 5C5EFDD3
gpg: Good signature from "Matt Amos <email address hidden>"
Good signature on /home/matt/Programming/OSM/build-area/openstreetmap-cgimap_0.5.8-0ubuntu0ppa0~xenial1_source.changes.
Checking signature on .dsc
gpg: Signature made Thu 03 Nov 2016 12:31:41 GMT using RSA key ID 5C5EFDD3
gpg: Good signature from "Matt Amos <email address hidden>"
Good signature on /home/matt/Programming/OSM/build-area/openstreetmap-cgimap_0.5.8-0ubuntu0ppa0~xenial1.dsc.
Package includes an .orig.tar.gz file although the debian revision suggests
that it might not be required. Multiple uploads of the .orig.tar.gz may be
rejected by the upload queue management software.
Uploading to ppa (via ftp to ppa.launchpad.net):
  Uploading openstreetmap-cgimap_0.5.8-0ubuntu0ppa0~xenial1.dsc: done.
  Uploading openstreetmap-cgimap_0.5.8.orig.tar.gz: done.
  Uploading openstreetmap-cgimap_0.5.8-0ubuntu0ppa0~xenial1.debian.tar.xz: done.
  Uploading openstreetmap-cgimap_0.5.8-0ubuntu0ppa0~xenial1_source.changes: done.
Successfully uploaded packages.

How can I test my packages before uploading them to see if there's something wrong with them? Is there a tool to check the validity of the changes, dsc, and so forth? I've run the package through cowbuilder successfully, and the build process runs Lintian as part of both the source package build and cowbuilder. What else should I be doing?

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

If you don't get an email at all, it's typically due to a problem with how you signed the .changes:

  https://help.launchpad.net/Packaging/UploadErrors#The_upload_appears_to_work_but_I_don.27t_get_any_email_about_it

And indeed in this case I see in our logs:

  2016-11-03 12:32:19 INFO Failed to parse changes file '/srv/launchpad.net/ppa-queue/incoming/upload-ftp-20161103-123149-080587/~osmadmins/ppa/openstreetmap-cgimap_0.5.8-0ubuntu0ppa0~xenial1_source.changes': Signing key CFCCB04FD03E936DF821628A3C8F426B5C5EFDD3 not registered in launchpad.

So you need to register that key before you can upload packages signed using it. The help.launchpad.net URL above has a suitable link.

Revision history for this message
Matt Amos (zerebubuth) said : 		#2

Thanks! That was the problem.

I'm confused, though. This is the same key I was using when I reported https://answers.launchpad.net/launchpad/+question/402707 a month ago, and it was working until the 24th October when I last uploaded a package signed with it. Do keys expire out of Launchpad before the expiry date set in them?

Revision history for this message
Matt Amos (zerebubuth) said : 		#3

Thanks Colin Watson, that solved my question.