Unexpected package version going backwards warnings.

Unexpected package version going backwards warnings.

[Daniel Squires]

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

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

[image: EA Phone Number]+44 (0)1326 378129

[image: RoboThespian FB] <https://www.facebook.com/RobotThespian> [image:
RoboThespian Twitter] <https://twitter.com/robothespian> [image: EA YouTube]
<http://youtube.com/EngineeredArts>
[image: Engineered Arts Logo] <https://www.engineeredarts.co.uk/>


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

[image: Subscribe to Mailing List]
<https://www.engineeredarts.co.uk/mailing-list/>

[-- Attachment #2: Type: text/html, Size: 2812 bytes --]

Re: [poky] Unexpected package version going backwards warnings.

[Richard Purdie]

On Fri, 2022-12-09 at 16:02 +0000, Daniel Squires 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?

We probably need to know a bit more about how you're building things.
Do you have a pool of workers building against a common sstate?

Are you using hash equivalence? Are you using a PR server? 

I ask the questions as the answer is probably somewhere in the way data
is being shared/reused between builds.

If you're not using package management on device to upgrade them, it
probably isn't a big issue but it is worth understanding the sstate
reuse in this context.

Cheers,

Richard

Re: [poky] Unexpected package version going backwards warnings.

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 1847 bytes --]

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
>
> [image: EA Phone Number]+44 (0)1326 378129
>
> [image: RoboThespian FB] <https://www.facebook.com/RobotThespian> [image:
> RoboThespian Twitter] <https://twitter.com/robothespian> [image: EA
> YouTube] <http://youtube.com/EngineeredArts>
> [image: Engineered Arts Logo] <https://www.engineeredarts.co.uk/>
>
>
> * Engineered Arts Ltd *
> E1-E3 Church View Business Park,
> Bickland Water Road,
> Falmouth Cornwall,
> TR11 4FZ
> United Kingdom
>
> [image: Subscribe to Mailing List]
> <https://www.engineeredarts.co.uk/mailing-list/>
>
>
> 
>
>

[-- Attachment #2: Type: text/html, Size: 3717 bytes --]

Re: [poky] Unexpected package version going backwards warnings.

[Richard Purdie]

On Fri, 2022-12-09 at 17:13 +0100, Alexander Kanavin wrote:
> 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.

Rather than dropping, you can just disable that QA check too, something
like:

ERROR_QA:remove = "version-going-backwards"

Cheers,

Richard

Re: [poky] Unexpected package version going backwards warnings.

[Peter Kjellerstedt]

> -----Original Message-----
> From: poky@lists.yoctoproject.org <poky@lists.yoctoproject.org> On Behalf
> Of Richard Purdie
> Sent: den 9 december 2022 17:20
> To: Alexander Kanavin <alex.kanavin@gmail.com>; Daniel Squires
> <dan@engineeredarts.co.uk>
> Cc: poky@lists.yoctoproject.org
> Subject: Re: [poky] Unexpected package version going backwards warnings.
> 
> On Fri, 2022-12-09 at 17:13 +0100, Alexander Kanavin wrote:
> > 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.

Unfortunately that is only true if the real tasks are actually run.
If the setscene tasks are used, then the version can go back to 
whatever version is stored in the sstate cache. 

That said, I have also seen occasional cases where the PR goes back 
to r0.0 for no apparent reason. 

> 
> Rather than dropping, you can just disable that QA check too, something
> like:
> 
> ERROR_QA:remove = "version-going-backwards"
> 
> Cheers,
> 
> Richard

//Peter

Re: [poky] Unexpected package version going backwards warnings.

[Daniel Squires]

[-- Attachment #1: Type: text/plain, Size: 2293 bytes --]

We are not currently running multiple instances of bitbake against the same
sstate cache. We are using PR servers, but currently only local to a build,
not shared. We do use packages to update targets.
Below is the content of local.conf (generated by kas).

Cheers

Dan

# meta-custom
PACKAGE_CLASSES ?= "package_deb"
LICENSE_FLAGS_ACCEPTED += "commercial"
# Number of parrallel bitbake tasks
BB_NUMBER_THREADS = "6"
# number of parraellel task run by "make" et al
PARALLEL_MAKE = "-j 4"

# meta-custom-tritium-os
BBFILE_PRIORITY_meta-aws = "11"

# meta-local
PRSERV_HOST = "localhost:0"
# It is recommended to activate "buildhistory" for testing the PR service
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"

MACHINE ??= "containerx86-64"
DISTRO ??= "tritium3-container"
BBMULTICONFIG ?= ""

On Fri, 9 Dec 2022 at 16:11, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Fri, 2022-12-09 at 16:02 +0000, Daniel Squires 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?
>
> We probably need to know a bit more about how you're building things.
> Do you have a pool of workers building against a common sstate?
>
> Are you using hash equivalence? Are you using a PR server?
>
> I ask the questions as the answer is probably somewhere in the way data
> is being shared/reused between builds.
>
> If you're not using package management on device to upgrade them, it
> probably isn't a big issue but it is worth understanding the sstate
> reuse in this context.
>
> Cheers,
>
> Richard
>

[-- Attachment #2: Type: text/html, Size: 3632 bytes --]