From: "Daniel Squires" <dan@engineeredarts.co.uk>
To: poky@lists.yoctoproject.org
Subject: Unexpected package version going backwards warnings.
Date: Fri, 9 Dec 2022 16:02:34 +0000 [thread overview]
Message-ID: <CAC+ji7EOT6D35madOZvx6tS8Nj43Tiq-cg06WYO8xue8MnBhiQ@mail.gmail.com> (raw)
[-- 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 --]
next reply other threads:[~2022-12-09 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 16:02 Daniel Squires [this message]
2022-12-09 16:11 ` [poky] Unexpected package version going backwards warnings 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
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=CAC+ji7EOT6D35madOZvx6tS8Nj43Tiq-cg06WYO8xue8MnBhiQ@mail.gmail.com \
--to=dan@engineeredarts.co.uk \
--cc=poky@lists.yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).