OZ Package Installation

[jjh]

After successfully installing numerous *.ipk packages, I have a problem installing Portabase version 1.9 (Portabase v1.8 installs without a problem).  I get the following error message: "Cannot find package /mnt/cf/pkgs/portabase_1.9_arm.ipk".  When viewed with the terminal or the file manager the correctly spelled package name appears in the correct file location (/mnt/cf/pkgs/).  Any ideas what the problem is??


OZ 3.2, Zaurus SL-5500
Sandisk 64M CF card

[Teletubbie]

Sometimes you need to pack the ipks in the old tar format, so that ipkg kann find them.
Unpack the package as described here:
http://www.openzaurus.org/oz_website/faq/faq?id=241

And pack it again  as described above. The problem comes now if you have a newer tar, as I have on my debian sarge or on Debian Sid. Then you have too pack it:

tar --format=oldgnu -czvf ....

Before packing again, you could have a look also at the contol file in the package. Sometimes there are stories about blank lines confusing ipkg.

You could also try an other ipkg package, that can handle the portabase. But I dont know, if there is one and which version.

Cheers,
Sam

[jjh]

Thanks, that seemed like a good idea but I still get the same error message.  There don't seem to be any blank lines in the control file either.  Also I have looked for a more current ipkg package before to no avail.

[Teletubbie]

According to the Document, I had the Idea with ipkg Poblems
http://opie.handhelds.org/cgi-bin/moin.cgi/ipkg_20FAQ
Maybe you have to try to download it from somewhere else?
Cheers

[lardman]

I've also had some troubles with a couple of tar.gz ipks - new ones for example the game 'cards' from killefiz.

I'd originally thought that it might be something to do with the contents of the control file, but after stripping a couple of bits out stuff out I still have the same problem (though I've not tried all the possibilities I admit).

Someone recently told me that for the Sharp ROM the control file must be in a ./control directory, I wonder whether this could be causing a problem....?

Try running with the -V switch to get some more debugging output - I'd like to see this solved as I'd thought that the OZ version of ipkg was completely robust (it's still head ans shoulders above the Sharp and pdaXrom ones of course).


Si