Redundant daily build starts and (or course) fails to updload

[Pierre Barbier de Reuille]

I have configured some daily builds on launchpad. And from time to time, it will try to re-build the project, even though there hasn't been any new update. Of course, this means that the package upload fails as there is already an identical package in my PPA. Is there anything I can do to avoid that?

If this helps, last time it happened, I had triggered a build by hand the day before. And although I don't exactly remember, I think that it only happened the day after I triggered a build. However, triggering a build doesn't always lead to that problem.

Here is the recipe that causes trouble:

https://code.launchpad.net/~pierre-barbierdereuille/+recipe/lithographx-daily

[Gianfranco Costamagna (costamagnagianfranco)]

hi, obviously you can't upload twice the same binary, with different content.
I suggest you to edit your recipe to add some sort of timestamp or similar to the version, e.g. time or whatever.
You can find some details here
https://help.launchpad.net/Packaging/SourceBuilds/Recipes

[Pierre Barbier de Reuille (pierre-barbierdereuille)]

The problem is not with my recipe or the build but with the trigger!
I don't understand why the build is triggered at all when no new code has been committed.

[Gianfranco Costamagna (costamagnagianfranco)]

the build is *not* triggered automatically if no commits are available. The issue you see is when you trigger a manual build *before* the automatic one.
In fact the auto build has no knowledge about a manual one triggered before.

[Gianfranco Costamagna (costamagnagianfranco)]

(I won't close it, I don't want to be an authoritative answer, and I'm pretty sure I didn't provide a full/correct explanation here)

[Pierre Barbier de Reuille (pierre-barbierdereuille)]

So maybe that's the issue. Maybe the automatic trigger should check there has been changes since the last manual trigger too, or the manual trigger should reset the need for an automatic one.