Uploaded a package to my PPA but can not see it

Asked by Cosmic DNA

Hi. I uploaded today my package to my PPA with the following logs:

Checking signature on .changes gpg: /home/daniel/Workspaces/Boiler/gitload_1.0_source.changes: Error checking signature from 406898842D145FAF: SignatureVerifyError: 0 Checking signature on .dsc gpg: /home/daniel/Workspaces/Boiler/gitload_1.0.dsc: Error checking signature from 406898842D145FAF: SignatureVerifyError: 0 Uploading to ppa-cosmic-dna (via ftp to ppa.launchpad.net): Uploading gitload_1.0.dsc: done. Uploading gitload_1.0.tar.gz: done. Uploading gitload_1.0_source.buildinfo: done. Uploading gitload_1.0_source.changes: done. Successfully uploaded packages.

I am not sure why there were SignatureVerifyErrors. Maybe because at the time I uploaded I had not yet added my fingerprint or sent my PGP key to ubuntu server...

The thing is when I try to dput again it says:
Package has already been uploaded to ppa-cosmic-dna on ppa.launchpad.net
Nothing more to do for gitload_1.0_source.changes

But I can not see the package in my PPA yet. Is there a delay or is there something amiss?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Guruprasad
Solved:
Last query:
Last reply:
Revision history for this message
Cosmic DNA (cosmic-dna) said :
#1

Here is the ppa: ppa:cosmic-dna/milky-way

Revision history for this message
Guruprasad (lgp171188) said :
#2

Hi,

Launchpad verifies that each upload is signed by a GPG key that has been added to the uploader's Launchpad account. If the verification fails or the key doesn't exist on the keyservers (this is likely what happened), Launchpad silently rejects the upload and doesn't send an email about it.

This behaviour is documented in https://help.launchpad.net/Packaging/UploadErrors#The_upload_appears_to_work_but_I_don.27t_get_any_email_about_it

Since the Ubuntu keyservers are part of a distributed system, it can take a few hours for the new key to show up on the keyservers. And once that happens, you can retry your upload using the 'dput' command with the 'force' option.

Revision history for this message
Cosmic DNA (cosmic-dna) said :
#3

And when I try to add repository with sudo add-apt-repository ppa:cosmic-dna/milky-way:

Repository: 'deb https://ppa.launchpadcontent.net/cosmic-dna/milky-way/ubuntu/ bookworm main'
More info: https://launchpad.net/~cosmic-dna/+archive/ubuntu/milky-way
Adding repository.
Press [ENTER] to continue or Ctrl-c to cancel.
Found existing deb entry in /etc/apt/sources.list.d/cosmic-dna-ubuntu-milky-way-bookworm.list
Adding deb entry to /etc/apt/sources.list.d/cosmic-dna-ubuntu-milky-way-bookworm.list
Found existing deb-src entry in /etc/apt/sources.list.d/cosmic-dna-ubuntu-milky-way-bookworm.list
Adding disabled deb-src entry to /etc/apt/sources.list.d/cosmic-dna-ubuntu-milky-way-bookworm.list
Warning: could not get PPA signing_key_fingerprint from LP, using anyway
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:3 http://security.debian.org/debian-security bookworm-security InRelease
Hit:4 http://ftp.debian.org/debian bookworm-backports InRelease
Err:5 https://ppa.launchpadcontent.net/cosmic-dna/milky-way/ubuntu bookworm InRelease
  403 Forbidden [IP: 185.125.190.80 443]
Reading package lists... Done
E: Failed to fetch https://ppa.launchpadcontent.net/cosmic-dna/milky-way/ubuntu/dists/bookworm/InRelease 403 Forbidden [IP: 185.125.190.80 443]
E: The repository 'https://ppa.launchpadcontent.net/cosmic-dna/milky-way/ubuntu bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Hit:1 http://ftp.debian.org/debian bookworm-backports InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://security.debian.org/debian-security bookworm-security InRelease
Err:5 https://ppa.launchpadcontent.net/cosmic-dna/milky-way/ubuntu bookworm InRelease
  403 Forbidden [IP: 185.125.190.80 443]
Reading package lists... Done
E: Failed to fetch https://ppa.launchpadcontent.net/cosmic-dna/milky-way/ubuntu/dists/bookworm/InRelease 403 Forbidden [IP: 185.125.190.80 443]
E: The repository 'https://ppa.launchpadcontent.net/cosmic-dna/milky-way/ubuntu bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Revision history for this message
Cosmic DNA (cosmic-dna) said :
#4

I just uploaded with dput -f:

Checking signature on .changes
gpg: /home/daniel/Workspaces/Boiler/gitload_1.0_source.changes: Valid signature from 406898842D145FAF
Checking signature on .dsc
gpg: /home/daniel/Workspaces/Boiler/gitload_1.0.dsc: Valid signature from 406898842D145FAF
Uploading to ppa-cosmic-dna (via ftp to ppa.launchpad.net):
  Uploading gitload_1.0.dsc: done.
  Uploading gitload_1.0.tar.gz: done.
  Uploading gitload_1.0_source.buildinfo: done.
  Uploading gitload_1.0_source.changes: done.
Successfully uploaded packages.

But still I can not see the package here within my PPA...

Revision history for this message
Guruprasad (lgp171188) said (last edit ):
#5

Hi,

In see you are trying to upload a PPA package for Debian to an Ubuntu PPA and that will likely not work well, if it works at all. Also, the upload is just the first step of publishing a package to a Launchpad PPA and there are multiple steps that Launchpad performs before it gets published to the PPA and this can take an hour or so depending on various factors.

From the upload processor logs, I see that you should have received a rejection email explaining why your upload was rejected. You are attempting to upload your package to the 'unstable' series, which only exists in Debian and not in Ubuntu, which your PPA is for.

Revision history for this message
Best Guruprasad (lgp171188) said :
#6
Revision history for this message
Cosmic DNA (cosmic-dna) said :
#7

Thanks Guruprasad, that solved my question.