opkg install fails with "get_header_tar: Unknown typeflag: 0x78: Success."

dskvr / opkg

Automatically exported from code.google.com/p/opkg

0 stars 0 forks source link

opkg install fails with "get_header_tar: Unknown typeflag: 0x78: Success." #101

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Use openSUSE 12.2 or newer as build system
2. Use OE as toolchain
3. Build an ipk package
4. Try to install this ipk package on the target with 'opkg install'.

The install fails with error

 * get_header_tar: Unknown typeflag: 0x78: Success.

The cause seems to be a change in the default configuration of tar in the host 
operating system. openSUSE has changed the default format from 'gnu' too 
'posix' (see https://bugzilla.novell.com/show_bug.cgi?id=780654 for details).

opkg should be able to handle ipk packages based on posix tar archives.

Original issue reported on code.google.com by sledz@dresearch-fe.de on 17 May 2013 at 2:28

GoogleCodeExporter commented 8 years ago

I'm inclined leave this until after an 0.2.0 release. Then for 0.3.0, rip out 
all manual handling of archive and compression formats (and everything else in 
libbb which is a hideous mess) and replace with a dependency on libarchive 
which appears to be a good, well maintained project.

Don't expect any action on this soon, but I'm thinking about it.

Original comment by paul.betafive on 3 Aug 2013 at 11:11

Changed state: Accepted
Added labels: Type-Enhancement
Removed labels: Type-Defect

GoogleCodeExporter commented 8 years ago

Original comment by paul.betafive on 18 Sep 2013 at 1:15

Added labels: Milestone-0.3

GoogleCodeExporter commented 8 years ago

I have copied OE from gentoo installation to openSUSE and this bug emerged. 
Running 
bitbake tar-replacement-native fixed the problem for me without having to 
recompile whole OE.

Original comment by mde...@gmail.com on 10 Dec 2013 at 8:47

GoogleCodeExporter commented 8 years ago

This should be fixed in the latest git master, could you give it a try please?

Original comment by paul.betafive on 5 Feb 2014 at 6:19

GoogleCodeExporter commented 8 years ago

I've tested this myself now. v0.2.1 fails to handle posix tar files, producing 
the given error message. The latest git master handles the files correctly and 
doesn't produce any errors.

Original comment by paul.betafive on 2 Mar 2014 at 2:05

Changed state: Fixed