mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de, Matthias Klein <matthias.klein@optimeas.de>
Subject: Re: [ptxdist] PTXdist 2014.02.0: problem with root.tgz
Date: Thu, 27 Feb 2014 23:40:17 +0100	[thread overview]
Message-ID: <20140227224016.GA7991@x61s.Speedport_W_921V_1_24_000> (raw)
In-Reply-To: <ema55782b9-423f-4ca3-9974-a0175f43d772@nb-mak>

Hi Matthias,

On Thu, Feb 27, 2014 at 10:08:24PM +0000, Matthias Klein wrote:
> Hello,
> 
> we are using the root.tgz file for our software updates.
> But I can't decompress the root.tgz with the tar (busybox) from PTXdist
> 2014.02 on an PTXdist 2014.01.0 target ...
> 
> I always get:
> 
> tar -xvzf root.tgz -C dest/
> invalid tar magic
> Does anyone have an idea ?
> (I can decompress the archive on the host, but not on the target)
> 
> 

First, I would check the checksum if tgz is the same like on your host
system.

Second, I googled a little bit... so it seems there are some options to
have backwards compability (depends on your host tar version if you need
them or not) check out [1].

Maybe BUSYBOX_FEATURE_TAR_OLDGNU_COMPATIBILITY is something which you need.

- Alex

[1] http://lists.busybox.net/pipermail/busybox/2010-September/073298.html

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-02-27 22:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 12:04 [ptxdist] [ANNOUNCE] PTXdist 2014.02.0 released Michael Olbrich
2014-02-27 22:08 ` [ptxdist] PTXdist 2014.02.0: problem with root.tgz Matthias Klein
2014-02-27 22:40   ` Alexander Aring [this message]
2014-02-28 12:26 Matthias Klein
2014-02-28 13:21 ` Jon Ringle
2014-02-28 13:33   ` Matthias Klein

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=20140227224016.GA7991@x61s.Speedport_W_921V_1_24_000 \
    --to=alex.aring@gmail.com \
    --cc=matthias.klein@optimeas.de \
    --cc=ptxdist@pengutronix.de \
    /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