All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: Andrea Galbusera <gizero@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: meta-toolchain-sdk fails in edison with package_ipk
Date: Thu, 17 May 2012 13:01:02 -0700	[thread overview]
Message-ID: <4FB558FE.80308@linux.intel.com> (raw)
In-Reply-To: <CAC+thW1-ir4bmjFn56h3mgCxi5=HQW64zOswZrbSigkzGnRVSA@mail.gmail.com>

On 17/05/12 12:34, Andrea Galbusera wrote:
> Hi Joshua,
>
> On Thu, May 17, 2012 at 8:01 PM, Joshua Lock<josh@linux.intel.com>  wrote:
>> Hello Andrea,
>>
>>
>> On 17/05/12 01:21, Andrea Galbusera wrote:
>>>
>>> Hello,
>>> Is there any known problem when building meta-toolchain-sdk target
>>> with PACKAGE_CLASSES = "package_ipk" ?
>>>
>>> I have deterministic failure in do_populate_sdk with latest edison
>>> metadata and default local.conf (other than changing PACKAGE_CLASSES
>>> to ipk).
>>> Don't have a denzil tree at hand, but I'm going to check if this is
>>> reproducible with 1.2 too.
>>>
>>> To me it seem the failing task is trying to access host files on my
>>> build system. Here is the first error I can see:
>>>
>>>> Installing libtelepathy-dbg (0.3.3-r3) to root...
>>>> Downloading
>>>> file:/scratch/gizero/edison-build-raid.orig/tmp/deploy/ipk/i586/libtelepathy-dbg_0.3.3-r3_i586.ipk.
>>>> touch: cannot touch `/etc/shells': Permission denied
>>>> mkdir: cannot create directory `/var/lib/opkg/alternatives': Permission
>>>> denied
>>>
>>>
>>> Here you can see the full log (few lines stripped to satisfy pastebin
>>> size limits...):
>>>
>>> http://pastebin.com/Gim3DacX
>>>
>>> Build works when I switch to rpm instead of ipk, but I want ipk for my
>>> target and, at moment, I need to switch back and forth the two formats
>>> when I need to update either my images or my sdk. Is there a smarter
>>> way to stay with rpm for the sdk and with ipk for the target images?
>>
>>
>> I've discovered that this is fixed in Denzil
>
> Thank you for your investigation! I ran out of time and could not test
> with denzil today, but you anticipated results... ;-)
>
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=1869
>>
>> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=c4de612298266653130dd2e5b8378f62dda77e9f
>>
>> I tested here and can report that the issue is resolved with that patch
>> applied.
>>
>> This patch has been applied to my josh/edison branch of the poky-contrib
>> repository and should make it into the main edison branch, and a point
>> release, in the near future.
>>
>> Thanks for the report,
>
> Glad to hear edison too will benefit of the fix! I noticed another
> strange behavior while experimenting with different configurations of
> PACKAGE_CLASSES: but I'd prefer repeating my tests before reporting
> issues.

I'm currently working with Edison to provide an update with various bug 
fixes so please do report your findings here or at bugzilla.yoctoproject.org

Regards,
Joshua
-- 
Joshua Lock
         Yocto Project
         Intel Open Source Technology Centre


      reply	other threads:[~2012-05-17 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17  8:21 meta-toolchain-sdk fails in edison with package_ipk Andrea Galbusera
2012-05-17 18:01 ` Joshua Lock
2012-05-17 19:34   ` Andrea Galbusera
2012-05-17 20:01     ` Joshua Lock [this message]

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=4FB558FE.80308@linux.intel.com \
    --to=josh@linux.intel.com \
    --cc=gizero@gmail.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.