From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: RaspberryPi Kernel - sometimes it works, sometimes it doesn't
Date: Tue, 12 Jun 2012 12:26:52 +0100 [thread overview]
Message-ID: <334879383.0TimNBShEg@helios> (raw)
In-Reply-To: <4FD6EE8A.2040101@r-finger.com>
On Tuesday 12 June 2012 08:23:54 Tomas Frydrych wrote:
> Over years of working with Poky I have developed this sort of a normal
> work flow:
>
> bitbake -c devshell <package>
> < do some tweaking >
> bitbake -c compile -f <package>
> bitbake <package> <---- this pulls package from sstate!!!
> scp ...
> < test, repeat>
>
> This no longer works, even after a forced recompile, Poky just pulls a
> package out of sstate. It seems the only reliable way to force a package
> rebuild is either to cleansstate or bump the PR, neither of which is
> viable an option in the above scenario. What am I missing? Is this
> really intended?
I was surprised because this was not behaviour I would expect either, however
that is indeed what it does here when I try that sequence. I'm not sure why it
is behaving this way but I think it is a bug.
FWIW, we will be looking at fixing this exact workflow pretty soon although it
may involve an extra explicit step to invalidate the stamps.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-06-12 11:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 11:30 RaspberryPi Kernel - sometimes it works, sometimes it doesn't Chris Tapp
2012-06-11 7:29 ` Tomas Frydrych
2012-06-11 7:58 ` Chris Tapp
2012-06-11 13:53 ` Khem Raj
2012-06-11 16:29 ` Paul Eggleton
2012-06-12 7:23 ` Tomas Frydrych
2012-06-12 11:26 ` Paul Eggleton [this message]
2012-06-12 11:30 ` Gary Thomas
2012-06-13 13:17 ` Paul Eggleton
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=334879383.0TimNBShEg@helios \
--to=paul.eggleton@linux.intel.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.