All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Volk <f_l_k@t-online.de>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: unpacking deb packages
Date: Sat, 15 Apr 2017 15:42:46 +0200	[thread overview]
Message-ID: <5cd6ea1e-4818-10f5-7179-0e77f5490706@t-online.de> (raw)
In-Reply-To: <CAJTo0LZdTsHP+hcSM74ELOfLqxhFWmunnr7SLFywCLokmmuKuw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

Thank you for the reply.

It looks like the problem is gone.

i guess this one fixed it

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=283a9b3883083e45bbdaf0488a3c6c76c5b197d7


Am 14.04.2017 um 01:09 schrieb Burton, Ross:
>
> On 10 April 2017 at 14:32, Markus Volk <f_l_k@t-online.de 
> <mailto:f_l_k@t-online.de>> wrote:
>
>     i´m building  for x86_64 using the recent master branch and
>     encounter problems when fetching deb packages.
>     With any .deb file inside SRC_URI the task do_unpack stops with
>     this output:
>
>     ... data.tar.xz && tar --no-same-owner -xpf data.tar.xz && rm
>     data.tar.xz failed with return value 2
>     if i  retry building the same recipe for 1-5 times without any
>     change the task sometime completes without errors
>
>
> My immediate hunch would be that it can't find a xz binary inside the 
> native sysroot as it hasn't been written in there yet.  Can you 
> provide a minimal recipe to test?
>
> Ross


[-- Attachment #2: Type: text/html, Size: 2374 bytes --]

      reply	other threads:[~2017-04-15 13:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10 13:32 unpacking deb packages Markus Volk
2017-04-13 23:09 ` Burton, Ross
2017-04-15 13:42   ` Markus Volk [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=5cd6ea1e-4818-10f5-7179-0e77f5490706@t-online.de \
    --to=f_l_k@t-online.de \
    --cc=ross.burton@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.