If you do not care about updating packages on target with a package manager, then you can drop SRCPV from your recipe versions.

Otherwise, you probably need to use a prserv, as described here:

https://docs.yoctoproject.org/dev-manual/common-tasks.html#incrementing-a-package-version

which will ensure package versions would never go backwards.

Alex

On Fri, 9 Dec 2022 at 17:02, Daniel Squires <dan@engineeredarts.co.uk> wrote:

Hi!
We're using kirkstone, though not the very latest at present.
Every now and then a a number of packages will unexpectedly give the error re package versions going backwards and teh version may have done something like go from git5-######-r0.1 to git3-#######-r0.0.
We always see this if we've been using devtool for a given recipe and then do a devtool reset, it complains about going back from git999 to e.g. git5 but this makes sense and we just run the build again and forget about it. However sometimes this just seems to happen randomly for a given recipe when it picks up a new commit from our repos and the git autoinc number will have gone back a few.
Does anybody know why and if it is a bug or an be fixed?

--
Dan Squires
Senior Roboticist
www.engineeredarts.co.uk

+44 (0)1326 378129

Engineered Arts Ltd
E1-E3 Church View Business Park,
Bickland Water Road,
Falmouth Cornwall,
TR11 4FZ
United Kingdom