From: gmane@reliableembeddedsystems.com
To: yocto@yoctoproject.org
Subject: Y-AB automatic updates?
Date: Tue, 11 Oct 2016 11:42:15 +0300 [thread overview]
Message-ID: <97f92f451012b39869a89eaeffbdf1a7@reliableembeddedsystems.com> (raw)
Hi,
With a latest and greatest Yocto Autobuilder I noticed stuff like this
when I restart it:
---
...
Updating PRSERV
remote: Counting objects: 20, done.
remote: Compressing objects: 100% (20/20), done.
remote: Total 20 (delta 17), reused 0 (delta 0)
Unpacking objects: 100% (20/20), done.
From git://git.openembedded.org/bitbake
35927a9..d9713ed master -> origin/master
35927a9..d9713ed 1.32 -> origin/1.32
+ 21defce...09dd499 master-next -> origin/master-next (forced update)
Updating 35927a9..d9713ed
Fast-forward
bin/bitbake | 2 +-
lib/bb/__init__.py | 2 +-
lib/bb/ui/depexp.py | 24 ++++++++++++++++++++++++
3 files changed, 26 insertions(+), 2 deletions(-)
---
This pumps e.g. the bitbake version:
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Tue Oct 11 08:46:35 2016 +0100
bitbake: Update version to 1.32.0
---
Is this really intentionally and what's the purpose?
Say you have a build server for your production software and PRSERV is
being (randomly) updated.
Due to a bug before or after the update the build output might be
different.
So you can't reproduce your images any more.
Some people (including myself) really would like to have reproduce able
builds.
Is there a "non hacky" way to turn these updates off?
Regards,
Robert
next reply other threads:[~2016-10-11 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 8:42 gmane [this message]
2016-10-11 14:39 ` Y-AB automatic updates? Joshua Lock
2016-10-11 15:38 ` gmane
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=97f92f451012b39869a89eaeffbdf1a7@reliableembeddedsystems.com \
--to=gmane@reliableembeddedsystems.com \
--cc=yocto@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 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.