'Successfully uploaded packages' but nothing appears

Bug #693727 reported by John Pye
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

I 'successfully' uploaded my IPOPT package to my PPA, see below:

john@deit252:~$ dput ppa:jdpipe/ppa ipopt_3.9.1_i386.changes
Checking signature on .changes
gpg: Signature made Wed 22 Dec 2010 23:17:34 EST using RSA key ID C8BF806D
gpg: Good signature from "John Pye (Aug 2010) <email address hidden>"
Good signature on /home/john/ipopt_3.9.1_i386.changes.
Checking signature on .dsc
gpg: Signature made Wed 22 Dec 2010 23:17:33 EST using RSA key ID C8BF806D
gpg: Good signature from "John Pye (Aug 2010) <email address hidden>"
Good signature on /home/john/ipopt_3.9.1.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 ipopt_3.9.1.dsc: done.
  Uploading ipopt_3.9.1.orig.tar.gz: done.
  Uploading ipopt_3.9.1.diff.gz: done.
  Uploading libipopt0_3.9.1_i386.deb: done.
  Uploading libipopt-dev_3.9.1_i386.deb: done.
  Uploading libipopt-dbg_3.9.1_i386.deb: done.
  Uploading ipopt_3.9.1_i386.changes: done.
Successfully uploaded packages.

After waiting several minutes, nothing has shown up in my PPA and I have received no emails. This website should immediately show SOMETHING if the command-line tool has indicated success. Otherwise there is a credibility gap: if the dput reported no error, then the PPA has received something, and Launchpad needs to immediately indicate to the user that it's working on doing the next step.

I note that this is not a duplicate of
bug #139422 because the triager said that they "needed more information about how to fix"
but #191666 because it is reported "fixed".

Revision history for this message
William Grant (wgrant) wrote :

The log says this:

 FatalUploadError: Signing key CD65978843FE14E7D2A71E38722EDBE8C8BF806D not registered in launchpad.

You don't seem to have an OpenPGP key associated with your account, so we can't authenticate the upload. We can't accept an upload which we can't authenticate, but we also can't notify you of its rejection, because we don't know which email address to use.

Changed in launchpad:
status: New → Invalid
Revision history for this message
John Pye (jdpipe) wrote :

OK, but this is still a bug!!! There needs to be a communication channel whereby I get some more information back from Launchpad and/or dput.

Changed in launchpad:
status: Invalid → New
Revision history for this message
William Grant (wgrant) wrote :

Indeed, although it's not entirely simple, since dput predates Launchpad by quite a long time. I've marked this bug as a duplicate of an older one describing this issue.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.