35 replies to this topic

[Abu Baniaz]

Is there an arm version of opkg tools?

Thanks in advance

[Caught]

Try this one, and please give some feedback.

 

 

Attached Files

•  enigma2-plugin-extensions-opkg-tools_1.4_all.ipk   345.07KB   112 downloads

Edited by Caught, 30 August 2017 - 23:02.

[Abu Baniaz]

Thanks.

I got the following:

root@vusolo4k:~# cd /hdd/ipkg-tools
root@vusolo4k:/media/hdd/ipkg-tools# opkg-unbuild enigma2-plugin-systemplugins-autobouquetsmaker_2.1+git314+fdf5103-r1_vusolo4k.ipk
['/bin/opkg-unbuild', 'enigma2-plugin-systemplugins-autobouquetsmaker_2.1+git314+fdf5103-r1_vusolo4k.ipk']
ar: unrecognized file type
tar: invalid magic
tar: short read
tar: can't open 'enigma2-plugin-systemplugins-autobouquetsmaker_2.1+git314+fdf5103-r1_vusolo4k/data.tar.gz': No such file or directory
tar: can't open 'enigma2-plugin-systemplugins-autobouquetsmaker_2.1+git314+fdf5103-r1_vusolo4k/control.tar.gz': No such file or directory
root@vusolo4k:/media/hdd/ipkg-tools#

[Abu Baniaz]

I was able to un-build another ipk file. Alter the control file and then re-build it. The re-created plugin, list missing picons worked fine on the arm receiver.

As a differnt test...
It seems that the un-build fails at the filetype recognition.
I could not un-build "enigma2-plugin-systemplugins-autobouquetsmaker_2.1+git314+fdf5103-r1_vusolo4k.ipk" which I got from the plugin server with the download command
However, I could un-build "enigma2-plugin-systemplugins-autobouquetsmaker_20170204_armv7ahf-vfp-neon.ipk" which I got from a forum.

I think, anything after the first "." is being treated as the file type, rather than everything after the last "."

Renaming the plugin allowed successful un-building.

from
 

enigma2-plugin-systemplugins-autobouquetsmaker_2.1+git314+fdf5103-r1_vusolo4k.ipk

to

enigma2-plugin-systemplugins-autobouquetsmaker_2_1+git314+fdf5103-r1_vusolo4k.ipk

I can unpack "enigma2-plugin-systemplugins-autobouquetsmaker_2.1+git314+fdf5103-r1_vusolo4k.ipk" using 7zip on my windows PC without a problem.
I tried ipkg-utils on the same ipk using Ubuntu 16.04 desktop, it did not un-build it either.

[Pr2]

Why do you try something complicate? The .ipk extension is just a .tgz (tar gunzip) file, change the extension to .tgz and you can open it up with any decompressor on PC or use:

 

tar -xvzf myipk.tgz

 

Pr2

[Caught]

Well, complicated not at all... 

I did a quick modification last evening to get it work on my HD51 (arm) box, a small test showed un-build/build was ok.

This afthernoon I've tried to un-build the ipk's from Abu Baniaz also succeed.

To build you need to avoid "_" maybe that was the problem I dont know for sure, but if you use the legal characters ([a-z 0-9.+-]) (no underscore) than I guess It works.

Im agree there are other (better) methods   

[betacentauri]

Why do you try something complicate? The .ipk extension is just a .tgz (tar gunzip) file, change the extension to .tgz and you can open it up with any decompressor on PC or use:

tar -xvzf myipk.tgz

Pr2

No. It's an ar archive.
To unpack it just execute this on the box:
ar x file.ipk
Then a control.tar.gz, a data.tar.gz and a debian-binary is generated.

[Abu Baniaz]

Unless someone can give explicit instructions, opkg-tools remains easiest thing to use. The fact the upload in post 2 cannot handle more than one "." is a minor issue.

Using the "ar x file.ipk" instruction works with more than one "." in name of file.

[willy01]

i´ve build one opkg tool ipk for ARM.

intressted?

Edited by willy01, 27 September 2017 - 14:34.

[willy01]

sorry, can´t delete post, don´t work with PLi

[Dimitrij]

create ipk for arm...

commands:

make folder

1)ipk-maker make_dir /tmp/IPK-BUILD

make ipk

2)chown -Rh root:root /tmp/IPK-BUILD
ipk-maker build /tmp/IPK-BUILD

Edited by Dimitrij, 28 September 2017 - 16:11.

[Abu Baniaz]

What about unmake please? I would hope a simple/straightforward process like opkg-tools

[Dimitrij]

examples:
  $program make_dir $IPKDIR
  $program build $IPKDIR
  $program unbuild $IPKDIR /tmp/any-package_0.1_all.ipk

[betacentauri]

To extract an ipk, just put it on a box and call

ar x ipk_name

[SpaceRat]

To extract an ipk, just put it on a box and call

ar x ipk_name

Won't work if build machine is running a decently current Linsuxx:

 

root@quadbox ~ # ar x enigma2_6.1+git24971+71e5aa1-r0_quadbox2400.ipk
ar: unrecognized file type

 

Shittybox-ar is incompatible with current binutils-ar.

[WanWizard]

What is "decently current"?

 

I'm running "GNU ar version 2.27-24.fc26" locally and that has no issue with ipk's generated by our buildservers? My servers run "GNU ar version 2.25.1-22.base.el7" and our buildservers use "GNU ar (GNU Binutils for Ubuntu) 2.26.1", but work fine too.

[SpaceRat]

I think it started with the version coming with Wiibuntu 16.04, not sure which version of Debilian that matches.

The full versions of ar seem to be compatible to each other, just not the busybox-ar to the newer full ars.

[athoik]

I think the problem on busybox ar occurs when you are using the option D on host ar.

  [D]          - use zero for timestamps and uids/gids

Most probably when creating packages under host, it's better to use fakeroot instead of D option.

[mrvica]

I´ve read somwhere that the new tar version can ar too, so ar is no longer needed, can someone confirm that

[Abu Baniaz]

Many thanks for the uploads.

 

Can someone give me step by step instructions (an idiot's guide)  on how to un-build, edit and re-build the ipk?