The version number of automatically built packages in Jenkins is inaccurate: 2.0~0.0alpha0 isn't an official release. This is a more accurate release number for automatic builds:

anarcat@marcos:provision$ ./debian/rules show-version
2.0~f2355d5

... however, it is still incorrect, as an alpha release (for example), will not upgrade from such a package. We should rather name this 2.0~0.x, as such:

anarcat@marcos:provision$ dpkg --compare-versions 2.0~f2355d5 lt 2.0~alpha1 ; echo $?
1
anarcat@marcos:provision$ dpkg --compare-versions 2.0~0.f2355d5 lt 2.0~alpha1 ; echo $?
0

It is unclear to me where those version numbers are generated, so I'll leave this to others for now.

Comments

anarcat’s picture

Status: Active » Fixed

I think I figured it out - somehow in the vagrant migration, we dropped the use of a script that was auto-generating a new version number. So in the jenkins job, I have changed:

git-buildpackage -kjenkins@ci.aegirproject.org 

to:

DOMAIN=ci.aegirproject.org ./debian/rules jenkins-build-auto

I have also fixed the version number generated by that build tool in git.

anarcat’s picture

I have enabled the Discard all but the last successful/stable artifact to save disk space flag on the debian build to make sure the previous builds are not kept around forever, which may confuse later builds.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

anarcat’s picture

So now I have updated the changelog to have 2.0~alpha1, and this breaks again. So I fixed the autobuilder to just append the jenkins build number and git tag to that version, so we're actually a version *ahead* of the one specified in the debian/changelog. I think that's fine.