Launchpad itself

Successfully uploaded packages do not build or show up

Asked by Christian Haudum

Hi,

I've been trying to build a hotfix release of an already superseded version for Crate (https://launchpad.net/~crate/+archive/stable/) and upload it to the PPA.

The upload process finishes successfully:

Now signing changes and any dsc files...
 signfile crate_0.42.5-1.dsc CRATE Jenkins <email address hidden>
 signfile crate_0.42.5-1_source.changes CRATE Jenkins <email address hidden>
Successfully signed dsc and changes files
+ dput -f ppa:crate/stable crate_0.42.5-1_source.changes
gpg: Signature made Sun 05 Oct 2014 01:29:36 PM CEST using RSA key ID 06F6EAEB
gpg: Good signature from "CRATE Jenkins <email address hidden>"
gpg: Signature made Sun 05 Oct 2014 01:29:36 PM CEST using RSA key ID 06F6EAEB
gpg: Good signature from "CRATE Jenkins <email address hidden>"
Checking signature on .changes
Good signature on /var/lib/jenkins/workspace/debuild/debuild/crate/crate_0.42.5-1_source.changes.
Checking signature on .dsc
Good signature on /var/lib/jenkins/workspace/debuild/debuild/crate/crate_0.42.5-1.dsc.
Uploading to ppa (via ftp to ppa.launchpad.net):
  Uploading crate_0.42.5-1.dsc: done.
  Uploading crate_0.42.5.orig.tar.gz: done.
  Uploading crate_0.42.5-1.debian.tar.gz: done.
  Uploading crate_0.42.5-1_source.changes: done.
Successfully uploaded packages.

But the build does not show up on the PPA, neither as failed nor as pending. Also, I did not get any email notification. I've tried re-uploading several times already.

Any help is appreciated!

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:

This question was reopened

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

pub 4096R/06F6EAEB 2014-01-07 CRATE Jenkins <email address hidden>

The signing key expired in January. You must either generate a new key or extend the expiry date on the existing one.

Revision history for this message
Christian Haudum (christian-haudum) said : 		#2

Hi William,

Thanks for the response, but Jan 7th is the creation date of the key, as you can see also on http://keyserver.ubuntu.com/pks/lookup?op=vindex&search=crate%20jenkins&fingerprint=on

We've been building with this key before. The last build (crate 0.44.4) was on 2014-10-04.

Thanks,
Christian

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

Er, yes, I totally misread that.

From our logs, we sent an email to CRATE Jenkin's contact address:

"""
2014-10-04 20:50:19 DEBUG Rejected:
2014-10-04 20:50:19 DEBUG crate_0.42.5-1.dsc: Version older than that in the archive. 0.42.5-1 <= 0.44.4-1
"""

You can't upload an older version unless you delete the existing one first.

Revision history for this message
Christian Haudum (christian-haudum) said : 		#4

Hm, that is what I feared already :(
Thanks for the clarification!

So there is no way to build hotfixes for older versions that have been superseded already? Is there a workaround?

Best,
Christian

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

Each PPA has at most one version of each package for each Ubuntu release. apt-get on client machines will upgrade to that version as long as it's newer than the current installed one, so it's unlikely that anyone using that PPA still has 0.42.x installed.

If you want to distribute multiple release series simultaneously, you'll probably want one PPA for each. For example, many projects have a stable PPA, a beta PPA and a nightly PPA, and others have a 0.1.x PPA, a 0.2.x PPA, etc.

Revision history for this message
Christian Haudum (christian-haudum) said : 		#6

We again have an issue with packages not showing up after uploading. This time it is not related to already superseded builds, but happens with new versions.
I don't want to open another question since the topic is exactly the same.
@wigrant last time you could take a look at the logs. could you do that again?
The only thing that changed on our side is that we now build and upload from a Docker container and not from a VM any more. The keys are the same though.
pub 4096R/06F6EAEB 2014-01-07
uid CRATE Jenkins <email address hidden>

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

We sent email notifications to <email address hidden> indicating the problem; figuring out what's wrong with your mail delivery would save you time in the long run, I think. Here are a few rejection messages from our logs:

2016-01-20 10:43:18 DEBUG File crate_0.54.3.orig.tar.gz already exists in CRATE stable, but uploaded version has different contents. See more information about this error in https://help.launchpad.net/Packaging/UploadErrors.
2016-01-20 10:43:18 DEBUG File crate_0.54.3-1.debian.tar.xz already exists in CRATE stable, but uploaded version has different contents. See more information about this error in https://help.launchpad.net/Packaging/UploadErrors.
2016-01-20 10:43:18 DEBUG Files specified in DSC are broken or missing, skipping package unpack verification.
2016-01-20 10:43:18 DEBUG utopic is obsolete and will not accept new uploads.

2016-01-20 10:43:20 DEBUG File crate_0.54.3.orig.tar.gz already exists in CRATE stable, but uploaded version has different contents. See more information about this error in https://help.launchpad.net/Packaging/UploadErrors.
2016-01-20 10:43:20 DEBUG File crate_0.54.3-1.debian.tar.xz already exists in CRATE stable, but uploaded version has different contents. See more information about this error in https://help.launchpad.net/Packaging/UploadErrors.
2016-01-20 10:43:20 DEBUG Files specified in DSC are broken or missing, skipping package unpack verification.

2016-01-20 10:44:15 DEBUG File crate_0.54.3.orig.tar.gz already exists in CRATE stable, but uploaded version has different contents. See more information about this error in https://help.launchpad.net/Packaging/UploadErrors.
2016-01-20 10:44:15 DEBUG File crate_0.54.3-1.debian.tar.xz already exists in CRATE stable, but uploaded version has different contents. See more information about this error in https://help.launchpad.net/Packaging/UploadErrors.
2016-01-20 10:44:15 DEBUG Files specified in DSC are broken or missing, skipping package unpack verification.

2016-01-20 10:44:17 DEBUG File crate_0.54.3.orig.tar.gz already exists in CRATE stable, but uploaded version has different contents. See more information about this error in https://help.launchpad.net/Packaging/UploadErrors.
2016-01-20 10:44:17 DEBUG File crate_0.54.3-1.debian.tar.xz already exists in CRATE stable, but uploaded version has different contents. See more information about this error in https://help.launchpad.net/Packaging/UploadErrors.
2016-01-20 10:44:17 DEBUG Files specified in DSC are broken or missing, skipping package unpack verification.

To summarise: your trusty upload was accepted (see https://launchpad.net/~crate/+archive/ubuntu/stable); you can't upload to utopic at all; and you can't do what you're trying to do by uploading the exact same version to vivid/wily/xenial - instead you must either upload to the oldest series you want to support, wait for it to build and publish, and then copy with binaries to other series, or else you must use a different version number for each series. Something like 0.54.3-1~ubuntu14.04.1 etc. would be usual practice if you take the latter approach, which I suspect will be easier for you to arrange.

Even if you take that latter approach, you must still ensure that crate_0.54.3.orig.tar.gz is bitwise-identical in each upload. It would normally be a direct copy of an upstream release, not built afresh for each source package you upload.

Revision history for this message
Christian Haudum (christian-haudum) said : 		#8

ok makes sense! we'll use crate_<VERSION>-<REVISION>~<DISTRO> for naming then. thanks!

Revision history for this message
Christian Haudum (christian-haudum) said : 		#9

Thanks Colin Watson, that solved my question.