ipkg confusion

[newestuser]

Hi.  I'm confused about what format the ipkgs are in.


I'm using  http://www.linuxtr.net/oe/feed/tosa/ for my sl6000 with the sharp rom.

I tried ar -x <name>.ipkg and tar zxvf <name>.ipkg.  Both report bad formatting.  I tried it on my zaurus and under cygwin.  I also tried this with different packages.  I'm really trying to install directly from the feed, but I thought I might need to convert to the sharp format first.  Any ideas about how to install these packages?

Thanks!

[Miami_Bob]

So far as I know, IPK files are either ar or tar-gz archives. Could the file have been bunged during download? You might also try viewing the contents with gzip alone and/or tar alone. Some folks have gotten IPKs that somehow were "non standard".

If nothing else works, looking at the raw hex would definitely tell if it is ar, tgz, gz or tar (or not). If you need to do this, let me know.

[Razzle]

Same problem here, I tried downloading libc6 from 3 different computers and neither tar, ar or winrar could extract/open it.

When I downloaded it from a different location, everything worked fine.

Looks like some of the files on this feed are broken..


You asked for the raw data:

Code: [Select]

!
debian-binary/  1098928989  500   100   100644  4         `
2.0
data.tar.gz/    1098928989  500   100   100644  1092119
 
.
.
control.tar.gz/ 1098928989  500   100   100644  617
This is from the beginning and close-to-end of the file where the 3 files seem to be located.

md5 is 5f898879c1b6a8816c5b657b5ee6d939

[Stubear]

I downloaded 3 ipks from the above sight and none of them match the MD5 sums in the package file.

Couldn't get ar or tar to recognize them, although hexdump gives

Code: [Select]

00000000  0d 0a 21 3c 61 72 63 68  3e 0a 64 65 62 69 61 6e  |..!.debian|
Maybe my browser is corrupting them (only tried with firefox on linux)

Stu

[Razzle]

Maybe my browser is corrupting them (only tried with firefox on linux)

I tried wget too, same result.

[Miami_Bob]

H'ok. I'm doing this from memory on the fly, so .......

 That  !<arch> at the start of the file is the signature for an AR archive.

 Debian archives also show this sig (since they are also ar files). There are other differences in their format but they should also open with the ar command.

 There are some other archive types that start similarly (old SUN system, if I recall right), but you are not likely to see any of them as IPK files.

 They should open with the Linux ar (there is a windows/DOS ar that does NOT use the same format & won't work).

 Since Stu says the MD5 sums are not matching (& the other info given), I'd bet the files on the server are bunged.

 The gz header starts with hex 1F 0B. You should NOT see the debian-binary, data.tar or control.tar strings in plain text (its compression encoded).

 The tar files should start with ./  hex 2E 2F & a file name (debian-binary, data.tar.gz or such). You should also see the ustar string about 0100 h bytes down.

 An more details I'd have to dig out my old notes to remember (G).