From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: yocto@yoctoproject.org
Subject: Re: [PATCH resend][opkg-utils] opkg.py/opkg-build: fix creation of tar archives
Date: Sat, 10 Nov 2012 09:33:59 +0000 [thread overview]
Message-ID: <509E1F87.4000100@r-finger.com> (raw)
In-Reply-To: <1351077244.22340.90.camel@ted>
On 24/10/12 12:14, Richard Purdie wrote:
> On Wed, 2012-10-24 at 12:53 +0200, Steffen Sledz wrote:
>> Since openSUSE 12.2 the installed tar uses posix instead of gnu encoding
>> by default. This format is not fully supported by opkg and results in
>> ipk packages not installable at the target.
>>
>> Collected errors:
>> * get_header_tar: Unknown typeflag: 0x78: Success.
>> * get_header_tar: Unknown typeflag: 0x78: Success.
>> * get_header_tar: Unknown typeflag: 0x78: Success.
>> * extract_archive: Don't know how to handle /var/lib/opkg/tmp/opkg-mg997m/chicken-bin-fGRvr4/PaxHeaders.17512/.: No such file or directory.
>> * get_header_tar: Unknown typeflag: 0x78: No such file or directory.
>> * get_header_tar: Unknown typeflag: 0x78: No such file or directory.
>> ...
>>
>> Signed-off-by: Steffen Sledz <sledz@dresearch-fe.de>
>> ---
>> opkg-build | 6 +++---
>> opkg.py | 6 +++---
>> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> Merged to master, thanks.
Could this be also applied to the danny branch (and perhaps even denzil)?
Tomas
next prev parent reply other threads:[~2012-11-10 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121023184056.GR3269@jama.jama.net>
[not found] ` <1351076036-25453-1-git-send-email-sledz@dresearch-fe.de>
[not found] ` <1351076036-25453-2-git-send-email-sledz@dresearch-fe.de>
2012-10-24 11:14 ` [PATCH resend][opkg-utils] opkg.py/opkg-build: fix creation of tar archives Richard Purdie
2012-11-10 9:33 ` Tomas Frydrych [this message]
2012-11-26 13:19 ` Burton, Ross
2012-11-26 13:33 ` Burton, Ross
2012-11-30 2:57 ` Scott Garman
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=509E1F87.4000100@r-finger.com \
--to=tf+lists.yocto@r-finger.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.