Groovy PPA uploads not appearing anywhere

Asked by Michael Rutter on 2021-01-08

Uploading packages to my PPA, Xenial, Bionic, and Focal packages upload and build without issue. Groovy packages appear to upload without error, but do not appear in the PPA. No email about it being accepted or rejected. This only effects Groovy.

Question information

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

Could you tell us the package name and version, and roughly when you uploaded it?

Revision history for this message
Michael Rutter (marutter) said :
#2

All can be found here: https://launchpad.net/~marutter/+archive/ubuntu/rrutter4.0

All times EST

rmatrix - 1.3-2-1.2010.0 Jan 7th 11:30 AM
rpy2 3.4.1-1.2010.1 Jan 6th 7:45 PM
foreign 0.8.81-1.2010.0 Dec 23, 1:00 PM

Builds for Xenial, Bionic, and Focal were accepted. I really only check to see if things were rejected, which I why I missed this. I have others going back further if need be.

Revision history for this message
Colin Watson (cjwatson) said :
#3

Our logs from around the relevant times say:

2021-01-07 16:50:09 DEBUG Considering changefile ~marutter/rrutter4.0/rmatrix_1.3-2-1.2010.0_source.changes
2021-01-07 16:50:09 DEBUG Finding fresh policy
2021-01-07 16:50:09 INFO Processing upload rmatrix_1.3-2-1.2010.0_source.changes
2021-01-07 16:50:09 DEBUG Beginning processing.
2021-01-07 16:50:09 DEBUG Verifying signature on rmatrix_1.3-2-1.2010.0_source.changes
2021-01-07 16:50:09 INFO Not sending rejection notice without a signing key.
2021-01-07 16:50:09 INFO Upload was rejected:
2021-01-07 16:50:09 INFO GPG verification of /srv/launchpad.net/ppa-queue/incoming/upload-ftp-20210107-164927-018543/~marutter/rrutter4.0/rmatrix_1.3-2-1.2010.0_source.changes failed: (7, 58, u'No data')
2021-01-07 16:50:09 INFO Further error processing not possible because of a critical previous error.

2021-01-07 00:20:07 DEBUG Considering changefile ~marutter/rrutter4.0/rpy2_3.4.1-1.2010.0_source.changes
2021-01-07 00:20:07 DEBUG Finding fresh policy
2021-01-07 00:20:07 INFO Processing upload rpy2_3.4.1-1.2010.0_source.changes
2021-01-07 00:20:07 DEBUG Beginning processing.
2021-01-07 00:20:07 DEBUG Verifying signature on rpy2_3.4.1-1.2010.0_source.changes
2021-01-07 00:20:08 INFO Not sending rejection notice without a signing key.
2021-01-07 00:20:08 INFO Upload was rejected:
2021-01-07 00:20:08 INFO GPG verification of /srv/launchpad.net/ppa-queue/incoming/upload-ftp-20210107-001944-017976/~marutter/rrutter4.0/rpy2_3.4.1-1.2010.0_source.changes failed: (7, 58, u'No data')
2021-01-07 00:20:08 INFO Further error processing not possible because of a critical previous error.

2020-12-23 17:55:08 DEBUG Considering changefile ~marutter/rrutter4.0/foreign_0.8.81-1.2010.0_source.changes
2020-12-23 17:55:08 DEBUG Finding fresh policy
2020-12-23 17:55:08 INFO Processing upload foreign_0.8.81-1.2010.0_source.changes
2020-12-23 17:55:08 DEBUG Beginning processing.
2020-12-23 17:55:08 DEBUG Verifying signature on foreign_0.8.81-1.2010.0_source.changes
2020-12-23 17:55:09 INFO Not sending rejection notice without a signing key.
2020-12-23 17:55:09 INFO Upload was rejected:
2020-12-23 17:55:09 INFO GPG verification of /srv/launchpad.net/ppa-queue/incoming/upload-ftp-20201223-175434-006751/~marutter/rrutter4.0/foreign_0.8.81-1.2010.0_source.changes failed: (7, 58, u'No data')
2020-12-23 17:55:09 INFO Further error processing not possible because of a critical previous error.

Now, it's possible that this was some kind of keyserver outage, but normally that would leave a bit more of a trace. It seems more likely that you just forgot to sign these uploads - is that possible?

Unfortunately a missing signature is the main case where we can't effectively notify the uploader of the problem by email, as we just don't have a reliable enough way to identify the uploader in that case. I can think of some possible ways to improve the situation, but at present an unsigned upload won't result in an email notification.

Revision history for this message
Michael Rutter (marutter) said :
#4

Thank you. At some point I started using the wrong debuild options in the Groovy chroot, which was the issue.

Can't offer a solution, but is there a post somewhere that describes that this might be the cause of the described behavior?

Thanks again.