Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Nasty tar breakage
Date: Fri, 11 Oct 2013 17:15:35 +0100	[thread overview]
Message-ID: <52582427.5000108@communistcode.co.uk> (raw)
In-Reply-To: <1381507693.29912.185.camel@ted>

On 11/10/13 17:08, Richard Purdie wrote:
> On Fri, 2013-10-11 at 16:21 +0100, Jack Mitchell wrote:
>> I upgraded my host distribution today which pulled in tar 1.27 [1] and
>> caused a nasty breakage. Downgrading to tar 1.26 fixed the problem, I
>> would expect this is something we want to fix before 1.5 goes out the door?
>>
>> DEBUG: Executing python function sstate_task_prefunc
>> DEBUG: Python function sstate_task_prefunc finished
>> DEBUG: Executing python function do_populate_sysroot
>> DEBUG: Executing shell function sysroot_stage_all
>> tar: --same-order option cannot be used with -c
>> Try 'tar --help' or 'tar --usage' for more information.
>> tar: This does not look like a tar archive
>> tar: Exiting with failure status due to previous errors
>> WARNING:
>> /home/jack/Work/oe-core.git/test-build/tmp-eglibc/work/x86_64-linux/quilt-native/0.60-r0/temp/run.sysroot_stage_all.21827:1
>> exit 2 from
>>   tar -xf - -C "$dest"
>> DEBUG: Python function do_populate_sysroot finished
>> ERROR: Function failed: sysroot_stage_all (log file is located at
>> /home/jack/Work/oe-core.git/test-build/tmp-eglibc/work/x86_64-linux/quilt-native/0.60-r0/temp/log.do_populate_sysroot.21827)
>>
>> [1] https://lists.gnu.org/archive/html/info-gnu/2013-10/msg00004.html
> Just to be clear, the command is:
>
> tar -cf - -C "$src" -ps . | tar -xf - -C "$dest"
>
> from staging.bbclass. The fix is probably just to drop the s from the
> -ps.
>
> Cheers,
>
> Richard
>

I'm afraid that doesn't work:

Exception: CalledProcessError: Command 'cd
/home/jack/Work/oe-core.git/test-build/tmp-eglibc/work/x86_64-linux/quilt-native/0.60-r0/sysroot-destdir/home/jack/Work/oe-core.git/test-build/tmp-eglibc/sysroots/x86_64-linux;
find . -type d -print | tar -cf - -C
/home/jack/Work/oe-core.git/test-build/tmp-eglibc/work/x86_64-linux/quilt-native/0.60-r0/sysroot-destdir/home/jack/Work/oe-core.git/test-build/tmp-eglibc/sysroots/x86_64-linux
-ps --files-from - | tar -xf - -C
/home/jack/Work/oe-core.git/test-build/tmp-eglibc/sysroots/x86_64-linux'
returned non-zero exit status 2 with output tar: --same-order option
cannot be used with -c
Try 'tar --help' or 'tar --usage' for more information.
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
find: `standard output': Broken pipe
find: write error

Tar command in staging.bbclass

tar -cf - -C "$src" -p . | tar -xf - -C "$dest"







  reply	other threads:[~2013-10-11 16:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11 15:21 Nasty tar breakage Jack Mitchell
2013-10-11 15:55 ` Paul Eggleton
2013-10-11 15:59   ` Mark Hatle
2013-10-11 16:08 ` Richard Purdie
2013-10-11 16:15   ` Jack Mitchell [this message]
2013-10-11 21:47     ` Richard Purdie
2013-10-12  8:14       ` Jack Mitchell
2013-10-12  9:06         ` Jack Mitchell

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=52582427.5000108@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox