[poky] [PATCH 0/1] check if lockfile is writable (bug 606 patch V2)

[Saul Wold]

On 12/29/2010 01:54 AM, Yu Ke wrote:
> I've sent a patch for bug 606 before, which add sanity check for $DL_DIR.
>
> After digging more, the root cause is hidden in bb.utils.lockfile(), so it
> is more general to add check there. hence comes out the V2 patch for bug606.
> please discard my V1 patch.
>
Ke,

I still wonder about this.  If the DL_DIR is read-only, since it is a 
shared environment (as example), when a fetch occurs, it may be for 
different reasons.

A couple of examples are:
1) an upstream fetch was missed (world build, but different hardware)
2) a developer changed the version information

In cases like this we really do want to do the fetch, so how can we 
handle that issue correctly, and not just fail and force the user to 
re-download all the packages (which may not be possible).

One option I can think of is to add a "WRITABLE_DL_DIR" (losy name but 
you get the idea) or something like that which if the DL_DIR is 
read-only could be written to for the lock file and ultimately the fetch 
of the missing upstream package.

Thoughts?

Sau!

> Pull URL: git://git.pokylinux.org/poky-contrib.git
>    Branch: kyu3/bug606-v2
>    Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kyu3/bug606-v2
>
> Thanks,
>      Yu Ke<ke.yu at intel.com>
> ---
>
>
> Yu Ke (1):
>    bb.utils: check if lock file is writable, to fix bug 606
>
>   bitbake/lib/bb/utils.py |    4 ++++
>   1 files changed, 4 insertions(+), 0 deletions(-)
>
> _______________________________________________
> poky mailing list
> poky at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>