Launchpad itself

Uploaded package not showing in my Launchpad PPA

Asked by Kaleb S. KEITHLEY

I'm working on some new packages that are dependencies for ceph. They build successfully for me locally with debuild and pbuilder.

But they're not showing up in my PPA when I dput them. They are signed. They have a good email address in the control file (same as other packages I build in launchpad.)

https://launchpad.net/~ceph-apache-arrow/+archive/ubuntu/orc

dput says the source.changes was successfully uploaded.

redoing the dput says the package has already been uploaded.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
William Grant
Solved:
Last query:
Last reply:
Revision history for this message
Clinton Fung (clinton-fung) said : 		#1

I acknowledge that you mentioned you build with other packages, and so just a due diligence question: have you checked and confirmed that you didn't receive an e-mail, or that something like an e-mail filter hasn't perhaps archived an e-mail?

Looking into past cases similar to this, when people have `dput` something that didn't show up, it's because the upload was rejected for some reason.

In general, `dput` just uploads the package without particularly extensive checks; then Launchpad checks it over and accepts or rejects it. Rejections are notified via email (except for the case where the package is unsigned, which isn't the case here).

Revision history for this message
Clinton Fung (clinton-fung) said : 		#2

Can you also please share a rough date/time when you performed the successful `dput`? That will help me to narrow down the search space in the logs.

Revision history for this message
Clinton Fung (clinton-fung) said : 		#3

Oh, and the actual package name, too, please.

Revision history for this message
Kaleb S. KEITHLEY (kkeithleatredhat) said (last edit ): 		#4

yes, I have checked that I have not received any email. And it's not in my spam folder.

The package name is orc (liborc1 and liborc-dev)

The date/time on the .upload file is 17:24 (UTC)

I'm sure it was rejected for a reason. What is the reason?

Revision history for this message
Clinton Fung (clinton-fung) said : 		#5

The signing key you used is not registered in Launchpad. When signature verification fails, we don't send e-mail.

Revision history for this message
Clinton Fung (clinton-fung) said : 		#6

The signing key you used is not registered in Launchpad. When signature verification fails, we don't send e-mail.

Revision history for this message
Kaleb S. KEITHLEY (kkeithleatredhat) said (last edit ): 		#7

I tried again with a correct, registered key* and dput a new build around 23:45 UTC. It has not shown up either.

I changed the name of the package to liborc and signed with the registered key and dput that at 23:49 UTC, and it too has not shown up.

* it is (now) the same key I use for gluster[1] and nfs-ganesha[2] builds, so I know it is a registered key.

[1] https://launchpad.net/~gluster
[2] https://launchpad.net/~nfs-ganesha

Revision history for this message
Clinton Fung (clinton-fung) said : 		#8

Please check your e-mail. This is the error message in the logs, which appeared along with t mention that an e-mail was sent:

`Signer has no upload rights to this PPA.`

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

Importantly, the key you used belongs to https://launchpad.net/~gluster-builder, not your personal account. That ~gluster-builder account has no rights on the ~ceph-apache-arrow PPA.

Revision history for this message
Kaleb S. KEITHLEY (kkeithleatredhat) said : 		#10

Thanks William Grant, that solved my question.