mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Matthias Klein" <matthias.klein@optimeas.de>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] PTXdist 2014.02.0: problem with root.tgz
Date: Fri, 28 Feb 2014 12:26:10 +0000	[thread overview]
Message-ID: <em0a0cf9d2-fc06-4bb0-bc77-aa87a79e65a3@nb-mak> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2152 bytes --]

Hello Alex,

thank you for the quick response!


But my problem is, that I have ptxdist 2014.01.0 based targets in the 
field which I want to remote update with ther existing busybox tar and 
the root.tgz file.

In the meantime I have found the problem: it is the --label option. (Jon 
Ringle: image: Create root.tgz with label 
0c30fd38e32126e6b1624a4acdc4a1efcd88c09c)

I tried to copy the old rules/post/image_tgz.make file into my local 
rules directory to override the new one, but then I get the following 
warnings and the new rule inside ptxdist is still used:

/usr/local/lib/ptxdist-2014.02.0/rules/post/image_tgz.make:15: warning: 
overriding commands for target 
`/home/user/bsp/platform-bsp/images/root.tgz'
/home/user/bsp/rules/image_tgz.make:15: warning: ignoring old commands 
for target `/home/user/bsp/platform-bsp/images/root.tgz'

Is there a way to override that rule locally in my bsp?


Best regards,

Matthias

------ Originalnachricht ------
Von: "Alexander Aring" <alex.aring@gmail.com>
An: ptxdist@pengutronix.de; "Matthias Klein" 
<matthias.klein@optimeas.de>
Gesendet: 27.02.2014 23:40:17
Betreff: Re: [ptxdist] PTXdist 2014.02.0: problem with root.tgz
>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
>

[-- Attachment #1.2: Type: text/html, Size: 4346 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2014-02-28 12:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 12:26 Matthias Klein [this message]
2014-02-28 13:21 ` Jon Ringle
2014-02-28 13:33   ` Matthias Klein
  -- strict thread matches above, loose matches on Subject: below --
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

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=em0a0cf9d2-fc06-4bb0-bc77-aa87a79e65a3@nb-mak \
    --to=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