Launchpad itself

Upload fails for daily PPA build

Asked by Jeremy Sanders

I've updated my daily build PPA, but launchpad is refusing to upload:

 * State: Failed to upload
 * Recipe: jeremysanders/veusz-daily-2
 * Archive: ~jeremysanders/ubuntu/veuszdaily
 * Distroseries: xenial
 * Duration: 4 minutes
 * Build Log: https://launchpad.net/~jeremysanders/+archive/ubuntu/veuszdaily/+recipebuild/1445530/+files/buildlog.txt.gz
 * Upload Log: https://launchpad.net/~jeremysanders/+archive/ubuntu/veuszdaily/+recipebuild/1445530/+files/upload_1445530_log.txt
 * Builder: https://launchpad.net/builders/lgw01-41

I don't understand why. Can anyone help? Thanks.

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
Manfred Hampl (m-hampl) said : 		#1

From your log:

Version older than that in the archive.
1.27-0~2149~201709091746~ubuntu16.04.1 <= 1.27-0~2291~201709021731~ubuntu16.04.1

It seems that you tried to build a version ...2149... although a version with a higher version number ...2291... already exists in your ppa.

Revision history for this message
Jeremy Sanders (jeremysanders) said : 		#2

But these builds are being automatically made by the daily builds, so I don't know why it's doing this.

Revision history for this message
Manfred Hampl (m-hampl) said : 		#3

Where is the version number taken from, how is it composed?

Revision history for this message
Manfred Hampl (m-hampl) said : 		#4

A strange detail:

The version number with 2149 has a higher date code 201709091746 than the other one (2291 and 201709021731)

Revision history for this message
Jeremy Sanders (jeremysanders) said : 		#5

It happened after a merge, so it may be caused by bzr generating an incorrect version number after a git merge.

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

The git merge looks to have been done backwards; someone merged master into their branch, then pushed that branch over master. Since git doesn't make that sort of mistake obvious, it's usually best not to use {revno} in git-derived version numbers. Consider a combination of {date}, {time} and {git-commit} instead.

Revision history for this message
Jeremy Sanders (jeremysanders) said : 		#7

Thanks very much!