All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] [Bug 5437] New: packaged-staging freezes
Date: Thu, 20 May 2010 14:10:11 -0700	[thread overview]
Message-ID: <4BF5A533.2020908@mentor.com> (raw)
In-Reply-To: <4BF55079.6030905@mentor.com>

Tom Rini wrote:
> Andrea Adami wrote:
>> I had same stall on:
>>
>> NOTE: package stagemanager-native-0.0.1-r12: task do_package_write: 
>> Succeeded
>>
>> There is one patch is shr repo removing one lockfile in
>> packaged-staging.bbclass which helped my rebuild.
>>
>> http://gitorious.org/~jama/angstrom/jama-shr-experimental/commit/1ae868c5f4029f1862555e97a1aba37a8935221c 
>>
>>
>> I think RP could say something about this lock.
> 
> iirc, that's mine or Chris'.  We want to have a lock on installing 
> pstaging otherwise gcc-cross{,-initial,-intermediate} and 
> libc{,-initial} can get done in the wrong order.

OK, reproducing the problem locally and digging again, I can say quite 
confidently that when 3440328ac1ccbd5ca6aeea4a4b6084ecafd6fdda put the 
lock in that the above link takes back out, that was a merge error 
between Poky and oe.dev since Poky is/was missing 
394d321684eec271bc55438e3c01f74825d80988 where that lock got moved for 
the reasons I stated above.  You can add:
Acked-by: Tom Rini <tom_rini@mentor.com>
and merge that gitorious commit into mainline, asap please :)

-- 
Tom Rini
Mentor Graphics Corporation




  reply	other threads:[~2010-05-20 21:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-5437-13@http.bugs.openembedded.org/>
2010-05-20 12:07 ` [oe-commits] [Bug 5437] New: packaged-staging freezes Andrea Adami
2010-05-20 15:08   ` Tom Rini
2010-05-20 21:10     ` Tom Rini [this message]
2010-05-20 18:44   ` Martin Jansa
2010-05-20 19:42   ` Koen Kooi

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=4BF5A533.2020908@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-devel@lists.openembedded.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.