From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Alexander Kanavin <alex.kanavin@gmail.com>,
Daniel Squires <dan@engineeredarts.co.uk>
Cc: "poky@lists.yoctoproject.org" <poky@lists.yoctoproject.org>
Subject: Re: [poky] Unexpected package version going backwards warnings.
Date: Fri, 9 Dec 2022 17:37:55 +0000 [thread overview]
Message-ID: <939e7589993146c2bbe31336c5fc0b3d@axis.com> (raw)
In-Reply-To: <113bc7de893b394142ee924d27c9c5a716856c8a.camel@linuxfoundation.org>
> -----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
prev parent reply other threads:[~2022-12-09 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 16:02 Unexpected package version going backwards warnings Daniel Squires
2022-12-09 16:11 ` [poky] " Richard Purdie
2022-12-13 9:37 ` Daniel Squires
2022-12-09 16:13 ` Alexander Kanavin
2022-12-09 16:19 ` Richard Purdie
2022-12-09 17:37 ` Peter Kjellerstedt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=939e7589993146c2bbe31336c5fc0b3d@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=alex.kanavin@gmail.com \
--cc=dan@engineeredarts.co.uk \
--cc=poky@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.