Re: [Launchpad-users] question on PPA builds

[Michael Hudson <michael.hudson@xxxxxxxxxxxxx>]

Olivier Tilloy wrote:
> Greetings Launchpad users,
> 
> During the past week I've been building in my PPA [1] successive
> versions of the same packages for internal pre-release testing purposes.
> As requested for the build to succeed, each time I was uploading a new
> source package, I bumped the version number (the <n> component in
> ~karmic1ubuntu<n> at the end of the package name). And that worked fine.
> 
> But it happened that the original source tarballs had some changes too
> between some of the builds. I assumed they were re-uploaded each time
> along with the source packages, so I didn't bother bumping their version
> numbers.
> 
> And it appears that all the builds were done using the source tarballs
> uploaded for the first build, all the subsequent tarballs with the same
> version numbers were ignored.
> 
> Is that a bug in the build system, or the expected behaviour?

I'm not an expert, but the behavior you describe is what I'd expect.

> The mail launchpad sends to confirm that a build has been accepted and
> is pending is not really clear about it. E.g.:
> 
>   Accepted:
>    OK: moovida-plugins-ugly_1.0.8.orig.tar.gz
>    OK: moovida-plugins-ugly_1.0.8-1fluendo1~ppa1~karmic1ubuntu3.diff.gz
>    OK: moovida-plugins-ugly_1.0.8-1fluendo1~ppa1~karmic1ubuntu3.dsc
>        -> Component: main Section: gnome
> 
> It doesn't mention that the orig.tar.gz file is re-used from previous
> builds. The only way for me to notice would be to compare the sha checksums.
> 
> In any case, is there a way (other than bumping the version numbers) I
> can force uploading the updated source tarballs?

Why do you want to have the same version number on different tarballs?
That sounds like a recipe for confusion!

Cheers,
mwh