Jump to content


Photo

Packing / unpacking IPK’s.


  • Please log in to reply
26 replies to this topic

#1 LraiZer

  • Senior Member
  • 101 posts

+19
Neutral

Posted 6 December 2017 - 18:25

 

 

The OE-A bitbake has a dependency on Enigma2. This dependency is not needed. Installing it also updates Enigma2. Building the plugin builds Enigma2 too. Despite numerous attempts to convince my collaborators otherwise, they won't agree to removing it. You can only insatll this on Enigma2 they say!

 

The standlone versions I used to post used to have the dependency removed. Using opkg-tools, I used to unbuild them, edit the control file and remove dependency, rebuild it. Recent changes mean I can no longer use opkg-tools. Despite numerous requests, nobody has provided and idiot's guide on how to do this. I tried modifying the bitbake file and building a shareable one. I was unsuccessful. My abilities do not stretch that far.

 

Please feel free to amend your bitbake file so that it does not depend on E2 and is architecture based instead of machine based.

 

Idiots Guide here ;)

Have you tried editing control by unpacking and repacking with standard linux tools on Ubuntu?

I adapted some old scripts for Ubuntu 16, so it should now be possible to simply right mouse click on an existing ipk and unpack it. You can then modify files and then right mouse click on the ipk again to repack it.

Try dropping these two scripts into the nautilus file browser script folder so they can be run directly from its menu.

Attached Files



Re: Packing / unpacking IPK’s. #2 Abu Baniaz

  • PLi® Contributor
  • 2,499 posts

+64
Good

Posted 11 December 2023 - 19:43

 

 

 

The OE-A bitbake has a dependency on Enigma2. This dependency is not needed. Installing it also updates Enigma2. Building the plugin builds Enigma2 too. Despite numerous attempts to convince my collaborators otherwise, they won't agree to removing it. You can only insatll this on Enigma2 they say!

 

The standlone versions I used to post used to have the dependency removed. Using opkg-tools, I used to unbuild them, edit the control file and remove dependency, rebuild it. Recent changes mean I can no longer use opkg-tools. Despite numerous requests, nobody has provided and idiot's guide on how to do this. I tried modifying the bitbake file and building a shareable one. I was unsuccessful. My abilities do not stretch that far.

 

Please feel free to amend your bitbake file so that it does not depend on E2 and is architecture based instead of machine based.

 

Idiots Guide here ;)

Have you tried editing control by unpacking and repacking with standard linux tools on Ubuntu?

I adapted some old scripts for Ubuntu 16, so it should now be possible to simply right mouse click on an existing ipk and unpack it. You can then modify files and then right mouse click on the ipk again to repack it.

Try dropping these two scripts into the nautilus file browser script folder so they can be run directly from its menu.

 

 

@LraiZer, is there an updated version for Ubuntu 22.03 please?

 

I want to unbuild AutoBouquetsMaker(ABM), different to AutoBouquets 28.2E, remove the dependencies that the build process adds, and then re-build it.


Edited by Abu Baniaz, 11 December 2023 - 19:45.


Re: Packing / unpacking IPK’s. #3 LraiZer

  • Senior Member
  • 101 posts

+19
Neutral

Posted 11 December 2023 - 21:22

I'm sure this updated info has been posted somewhere before..

 

Scripts just need updating to detect tar.xz archives as well as old tar.gz

New .ipk will still be repacked as .gz not .xz

 

Make sure fakeroot is also installed:

sudo apt-get install fakeroot

Then install the two scripts in nautilus script folder as normal, and make the following edit in both the unpack and repack script.

 

CHANGE

for f in *.tar.gz

TO

for f in *.tar.*z


Re: Packing / unpacking IPK’s. #4 LraiZer

  • Senior Member
  • 101 posts

+19
Neutral

Posted 11 December 2023 - 21:49

Also change the file order in repack script so that archive manager in ubuntu can open the ipk. Its fussy that way!
 
FROM
cd $DIRNAME/$IPKNAME && ar -r $BASENAME *.tar.gz debian-binary

TO

cd $DIRNAME/$IPKNAME && ar -r $BASENAME debian-binary *.tar.gz


Re: Packing / unpacking IPK’s. #5 Huevos

  • PLi® Contributor
  • 4,661 posts

+163
Excellent

Posted 11 December 2023 - 21:49

 

 

 

 

The OE-A bitbake has a dependency on Enigma2. This dependency is not needed. Installing it also updates Enigma2. Building the plugin builds Enigma2 too. Despite numerous attempts to convince my collaborators otherwise, they won't agree to removing it. You can only insatll this on Enigma2 they say!

 

The standlone versions I used to post used to have the dependency removed. Using opkg-tools, I used to unbuild them, edit the control file and remove dependency, rebuild it. Recent changes mean I can no longer use opkg-tools. Despite numerous requests, nobody has provided and idiot's guide on how to do this. I tried modifying the bitbake file and building a shareable one. I was unsuccessful. My abilities do not stretch that far.

 

Please feel free to amend your bitbake file so that it does not depend on E2 and is architecture based instead of machine based.

 

Idiots Guide here ;)

Have you tried editing control by unpacking and repacking with standard linux tools on Ubuntu?

I adapted some old scripts for Ubuntu 16, so it should now be possible to simply right mouse click on an existing ipk and unpack it. You can then modify files and then right mouse click on the ipk again to repack it.

Try dropping these two scripts into the nautilus file browser script folder so they can be run directly from its menu.

 

 

@LraiZer, is there an updated version for Ubuntu 22.03 please?

 

I want to unbuild AutoBouquetsMaker(ABM), different to AutoBouquets 28.2E, remove the dependencies that the build process adds, and then re-build it.

 

Why don't you just do that in the build script?



Re: Packing / unpacking IPK’s. #6 Abu Baniaz

  • PLi® Contributor
  • 2,499 posts

+64
Good

Posted 11 December 2023 - 23:56

Why don't you just do that in the build script?

 

Any suggestions how to do that? The libc6 dependency and version number is still added by the build process, as it always has done.  Nothing to do with anything in the bitbake file.

opkg install /root@et8500:~# opkg install /tmp/*/.ipk
Collected errors:
 * calculate_dependencies_for: Cannot satisfy the following dependencies for enigma2-plugin-systemplugins-autobouquetsmaker:
 *      libc6 (>= 2.37) * 
 * opkg_solver_install: Cannot install package enigma2-plugin-systemplugins-autobouquetsmaker.
root@et8500:~# 

Edited by Abu Baniaz, 12 December 2023 - 00:43.


Re: Packing / unpacking IPK’s. #7 Abu Baniaz

  • PLi® Contributor
  • 2,499 posts

+64
Good

Posted 12 December 2023 - 01:11

I am sure that I have done this correctly having reviewed idiot's guide PMs from 2017, but  something is going wrong/ i am making a mistake. Please double check/advise.

 

I right click on the original ipk > scripts > unpack

I then go to the control folder, edit the control file as that is the only change I am making

go back

right click the original ipk > scripts > re-pack

A new ipk_repack folder is created.

I can install the ipk with no issue reported during installation. However, the plugin does not load/install fully on the receiver

 

Slight correction on ubuntu version, I am on 22.04.3

 

user@inspiron:~$ lsb_release -a
No LSB modules are available.
Distributor ID:    Ubuntu
Description:    Ubuntu 22.04.3 LTS
Release:    22.04
Codename:    jammy
user@inspiron:~$

 
root@et8500:~# opkg install /tmp/*.ipk
Installing enigma2-plugin-systemplugins-autobouquetsmaker (3.4+git1049+b7d2824) on root.
Checking for an ABM cache file
No cache file found, continuing.
Configuring enigma2-plugin-systemplugins-autobouquetsmaker.
root@et8500:~# init 4
root@et8500:~# init 3
root@et8500:~#
#!/bin/bash

#DISTRO - Ubuntu 16 LTS
#E2-IPK-REPACKER - LraiZer @ www.ukcvs.net

# ~/
# File browser Ctrl+H to Show hidden files/folders
# copy scripts to folder
# ~/.local/share/nautilus/scripts
# make executable - chmod 755
# right mouse click on target ipk to select script

BASENAME=`basename $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS`
DIRNAME=`dirname $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS`
IPKNAME="ipk_repack"

cd $DIRNAME

mkdir -p $IPKNAME

for f in *.tar.*z; do d=`echo $f | cut -d '.' -f1`; cd $d && fakeroot -- tar -czvf $DIRNAME/$IPKNAME/$d.tar.gz ./* && cd ..; done

cp $DIRNAME/debian-binary $DIRNAME/$IPKNAME/debian-binary
cd $DIRNAME/$IPKNAME && ar -r $BASENAME debian-binary *.tar.gz

if [ ! -f $DIRNAME/$IPKNAME/$BASENAME ]; then
    zenity --error --title "ERROR.: ipk not created!" --text " Did not create ipk!\n Please check it."
    exit 0
else
    zenity --info --title "OK.: ipk created successfully." --text " ipk file created successfully..\n File path: $DIRNAME/$IPKNAME/"
fi

exit 0
#!/bin/bash

#DISTRO - Ubuntu 16 LTS
#E2 IPK UN-PACKER - LraiZer @ www.ukcvs.net

# ~/
# File browser Ctrl+H to Show hidden files/folders
# copy scripts to folder
# ~/.local/share/nautilus/scripts
# make executable - chmod 755
# right mouse click on target ipk to select script

DIRNAME=`dirname $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS`

cd $DIRNAME

ar x *.ipk && for f in *.tar.*z; do d=`echo $f | cut -d '.' -f1`; mkdir -p ./$d && tar -xf $f -C ./$d; done

exit 0

Edited by Abu Baniaz, 12 December 2023 - 01:31.


Re: Packing / unpacking IPK’s. #8 Abu Baniaz

  • PLi® Contributor
  • 2,499 posts

+64
Good

Posted 12 December 2023 - 02:16

Sorry, I found your previous instructions here: https://forums.openp...-2#entry1423290

But situation is the same.



Re: Packing / unpacking IPK’s. #9 s3n0

  • Senior Member
  • 673 posts

+62
Good

Posted 12 December 2023 - 12:45

Hi @Abu Baniaz

 

Again... what exactly isn't working ?

 

You need to add Lib-C library dependencies ?

- file: ${PROJECT_DIR}/CONTROL/control

- variable: Depends: libc6 (>= 2.37)

 

Or are you trying to make a command of shell-script, to automate the process of adding these Lib-C library dependencies into the IPK packages ?

 

The IPK and DEB packages may differ slightly on Linux set-top boxes, as there is no full-fledged Linux in the set-top boxes. Often outdated or unfortunately only universal and insufficient tools are used (BusyBox for example).

 

I use my own shell script on Linux set-top boxes to create IPK + DEB packages. Try to look and maybe it will help you:
https://github.com/s...r_ProjectXYZ.sh


Edited by s3n0, 12 December 2023 - 12:54.


Re: Packing / unpacking IPK’s. #10 Abu Baniaz

  • PLi® Contributor
  • 2,499 posts

+64
Good

Posted 12 December 2023 - 15:26

I am trying to rebuild these two enigma2 ipks and remove the dependencies for enigma2 and libc6. That way people with older/different images can install them on their enigma2 receivers. I am not fussed whether I do it on ubuntu on my build machine or an enigma2 receiver. Hopefully without destroying all data on the hdd like I did last night with opkg -tools.

 

https://www.mediafire.com/folder/umojfuohoa3y9/ABM_2023.12.11
 

 

Package: enigma2-plugin-systemplugins-autobouquetsmaker
Version: 3.4+git1049+b7d2824-r0
Description: systemplugins-autobouquetsmaker
 systemplugins-autobouquetsmaker
Section: base
Priority: optional
Maintainer: oe-alliance team
License: Proprietary
Architecture: cortexa15hf-neon-vfpv4
OE: enigma2-plugin-systemplugins-autobouquetsmaker
Homepage: https://www.world-of-satellite.com
Depends: enigma2, libc6 (>= 2.37)
Source: enigma2-plugin-systemplugins-autobouquetsmaker.bb


Re: Packing / unpacking IPK’s. #11 s3n0

  • Senior Member
  • 673 posts

+62
Good

Posted 12 December 2023 - 18:03

Ah well, OK, I understand.

 

And have you done any debugging ? Any tests ? Or nothing yet ?

 

Where is the problem actually ? Unpacking the files ? Or in their repackaging ? Or have you not found out these details yet ?

 

Unfortunately, I don't have Ubuntu, so I can't test it myself. However, I know that both IPK and DEB in old Linuxes are very sensitive to change :). I myself create a DEB by just adding a space there (see my shell script for making IPK packages), which is quite enough :). I also paid attention to the DEB format, which can also be handled by OPKG (intended for IPK). It's really a vicious circle. Like everything in Linux systems. Everything depends on everything :-D.



Re: Packing / unpacking IPK’s. #12 mrvica

  • Senior Member
  • 1,259 posts

+86
Good

Posted 12 December 2023 - 19:26

if that script uses busybox ar it won´t work, you need full featured ar, here for armhf boxes

 

Attached Files



Re: Packing / unpacking IPK’s. #13 LraiZer

  • Senior Member
  • 101 posts

+19
Neutral

Posted 12 December 2023 - 20:09

@Abu Baniaz
The updated unpack and repack scripts test out just fine for me with ABM.
I unpacked ABM ipk, removed depend line from control, repacked ABM ipk.
Then removed ABM from stb, and installed repacked AMB ipk. New repacked AMB runs ok.
root@xpeedlx3:/tmp# opkg --force-depends remove enigma2-plugin-systemplugins-autobouquetsmaker
Removing enigma2-plugin-systemplugins-autobouquetsmaker (3.3+git1031+41c51a4) from root...
root@xpeedlx3:/tmp# opkg install *.ipk
Installing enigma2-plugin-systemplugins-autobouquetsmaker (3.4+git1049+b7d2824)on root.
Checking for an ABM cache file
No cache file found, continuing.
Configuring enigma2-plugin-systemplugins-autobouquetsmaker.

Here are new updated scripts and Ubuntu prerequisites:

sudo apt-get install binutils fakeroot

Attached Files



Re: Packing / unpacking IPK’s. #14 s3n0

  • Senior Member
  • 673 posts

+62
Good

Posted 12 December 2023 - 22:25

@Abu Baniaz

 

How about this... try the following:

#!/bin/bash


cd /tmp
ls
# p.ipk

ar --version
# BusyBox v1.36.0 () multi-call binary.
# ......

ar -x p.ipk
ls 
# control.tar.gz  data.tar.gz     debian-binary   p.ipk

tar -xzf control.tar.gz ./control                 # extracting the file "CONTROL/control"
ls
# control         control.tar.gz  data.tar.gz     debian-binary   p.ipk

TMP_VAR=$(cat control | grep -i "Depends:")
cat control | grep -i -v "Depends:" > control_; mv -f control_ control; chmod a+x control      # remove the whole line with "Depends:" string, ignoring LOWERCASE/UPPERCASE
echo "$TMP_VAR"           \
  | sed 's@libc6 (.*),@@' \
  | sed 's@libc6 (.*)@@'  \
  | sed 's@libc6,@@'      \
  | sed 's@libc6@@'       \
  | sed 's@enigma2,@@'    \
  | sed 's@enigma2@@'      >> control

gzip -d control.tar.gz                          # extacting "control.tar.gz" -> to -> "control.tar"
tar --delete -f control.tar ./control           # delete old file "control" from archive
tar -uf control.tar ./control                   # update this one "control" file in "control.tar" archive
gzip control.tar                                # compress "control.tar" -> to -> "control.tar.gz"


ar -r p_new.ipk ./debian-binary ./control.tar.gz ./data.tar.gz

 



Re: Packing / unpacking IPK’s. #15 Abu Baniaz

  • PLi® Contributor
  • 2,499 posts

+64
Good

Posted 12 December 2023 - 23:37

Thank you for taking the time to respond. I installed a ubuntu 16.04 vm and used the old scripts prior to the post by LraiZer. It turns out I need to make changes (delete.pyc files and replace them with.py files). However, the ABM binary built on newer environment won't work on python 2 images.

 

The output of your script is below. I had named it as "s3no_ipk.sh". I am sure it will come useful to somebody. There should be a way to unpack an ipk, make changes and then repack. Like how opkg-tools used to allow.

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2023.12.12 22:34:17 =~=~=~=~=~=~=~=~=~=~=~=
 
 
Welcome to OpenViX for vuduo4k
 
openvix 6.4 vuduo4k
 
 
 
vuduo4k login: root
Password: 
Last login: Tue Dec 12 22:33:05 GMT 2023 on pts/0
root@vuduo4k:~# cd /tmp
root@vuduo4k:/tmp# ./s3no_ipk.sh
bcm
bp3
camd.socket
firmware
hotplug.socket
missing-picons_2023-12-12_17-40-38.zip
nxserver_ipc
oscam-emu.pid
p.ipk
proc
s3no_ipk.sh
xstreamity
ar: unrecognized option '--version'
BusyBox v1.36.0 () multi-call binary.
 
Usage: ar x|p|t|r [-ov] ARCHIVE [FILE]...
 
Extract or list FILEs from an ar archive, or create it
 
        x       Extract
        p       Extract to stdout
        t       List
        r       Create
        -o      Restore mtime
        -v      Verbose
bcm
bp3
camd.socket
control.tar.gz
data.tar.xz
debian-binary
firmware
hotplug.socket
missing-picons_2023-12-12_17-40-38.zip
nxserver_ipc
oscam-emu.pid
p.ipk
proc
s3no_ipk.sh
xstreamity
bcm
bp3
camd.socket
control
control.tar.gz
data.tar.xz
debian-binary
firmware
hotplug.socket
missing-picons_2023-12-12_17-40-38.zip
nxserver_ipc
oscam-emu.pid
p.ipk
proc
s3no_ipk.sh
xstreamity
tar: unrecognized option '--delete'
BusyBox v1.36.0 () multi-call binary.
 
Usage: tar c|x|t [-ZzJjahvokO] [-f TARFILE] [-C DIR] [-T FILE] [-X FILE] [LONGOPT]... [FILE]...
 
Create, extract, or list files from a tar file
 
        c       Create
        x       Extract
        t       List
        -f FILE Name of TARFILE ('-' for stdin/out)
        -C DIR  Change to DIR before operation
        -v      Verbose
        -O      Extract to stdout
        -o      Don't restore user:group
        -k      Don't replace existing files
        -Z      (De)compress using compress
        -z      (De)compress using gzip
        -J      (De)compress using xz
        -j      (De)compress using bzip2
        --lzma  (De)compress using lzma
        -a      (De)compress based on extension
        -h      Follow symlinks
        -T FILE File with names to include
        -X FILE File with glob patterns to exclude
        --exclude PATTERN       Glob pattern to exclude
        --overwrite             Replace existing files
        --strip-components NUM  NUM of leading components to strip
        --no-recursion          Don't descend in directories
        --numeric-owner         Use numeric user:group
        --no-same-permissions   Don't restore access permissions
tar: invalid option -- 'u'
BusyBox v1.36.0 () multi-call binary.
 
Usage: tar c|x|t [-ZzJjahvokO] [-f TARFILE] [-C DIR] [-T FILE] [-X FILE] [LONGOPT]... [FILE]...
 
Create, extract, or list files from a tar file
 
        c       Create
        x       Extract
        t       List
        -f FILE Name of TARFILE ('-' for stdin/out)
        -C DIR  Change to DIR before operation
        -v      Verbose
        -O      Extract to stdout
        -o      Don't restore user:group
        -k      Don't replace existing files
        -Z      (De)compress using compress
        -z      (De)compress using gzip
        -J      (De)compress using xz
        -j      (De)compress using bzip2
        --lzma  (De)compress using lzma
        -a      (De)compress based on extension
        -h      Follow symlinks
        -T FILE File with names to include
        -X FILE File with glob patterns to exclude
        --exclude PATTERN       Glob pattern to exclude
        --overwrite             Replace existing files
        --strip-components NUM  NUM of leading components to strip
        --no-recursion          Don't descend in directories
        --numeric-owner         Use numeric user:group
        --no-same-permissions   Don't restore access permissions
ar: can't stat './data.tar.gz': No such file or directory
root@vuduo4k:/tmp# 
 
root@vuduo4k:/tmp# 
 
root@vuduo4k:/tmp# 

Edited by Abu Baniaz, 12 December 2023 - 23:42.


Re: Packing / unpacking IPK’s. #16 s3n0

  • Senior Member
  • 673 posts

+62
Good

Posted 13 December 2023 - 09:08

Hi.

 

The "tar" archiver you use is from BusyBox. That is not good. Please, install a full-fledged or GNU-version of the "tar" archiver. If it is not possible to use / install a full-fledged "tar", then I can, if you want, rewrite this small shell script. The shell script can be completely changed so that it is not necessary to use the "-u" (update) argument in "tar". So that all files will be unpacked and archived again. I can do that too if you want. I assumed that the "tar" you are using is a full version and not the BusyBox version.

 

Also... I don't use the "tar" from BusyBox, but the GNU-version of the "tar":

taroot@vusolose:~# tar --version
tar (GNU tar) 1.34
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by John Gilmore and Jay Fenlason.
root@vusolose:~#

The file "p.ipk" is only for your own understanding or for testing - an temporary IPK-file that contains a "CONTROL/control" file that also contains the line "Depends:".

 

It's just a quickly written shell script that should do what you need. That is find the "CONTROL/control" file in the .ipk file and then other details on the "Depends:" line. After that, multiple login strings should be removed as well (if there are more of these dependencies and not just enigma2 and libc6).

 

Add your IPK file that you need to process... rename it to "p.ipk" name... for testing purposes. The output should be the finished file "p_new.ipk". If it works, you can then modify the shell script according to your needs.


Edited by s3n0, 13 December 2023 - 09:15.


Re: Packing / unpacking IPK’s. #17 Abu Baniaz

  • PLi® Contributor
  • 2,499 posts

+64
Good

Posted 13 December 2023 - 16:16

@s3n0

Thank you for the time you invested in this. I had renamed the ipk to p.ipk, the ls command shows it listed above. I missed the install a fully-fledged ar as provided by mrvica in the instructions, so that explains the other errors I got.

 

I think it would be better to spend time make scripts to replace opkg-tools. So somebody can unpack an ipk, modify it as required, repack it again. Or create an ipk from scratch. This is beyond my abilities. Especially as some components of plugins unpack as .gz and others as .xz. The use case scenario for me (just modify the control file) no longer applies.



Re: Packing / unpacking IPK’s. #18 WanWizard

  • PLi® Core member
  • 70,528 posts

+1,811
Excellent

Posted 13 December 2023 - 16:21

if ipk's are properly build in a bitbake process, all this manually hacking wouldn't be needed.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Packing / unpacking IPK’s. #19 Abu Baniaz

  • PLi® Contributor
  • 2,499 posts

+64
Good

Posted 13 December 2023 - 16:27

if ipk's are properly build in a bitbake process, all this manually hacking wouldn't be needed.

If you can assist me to make the latest ABM files so it works on python 2 images, that would be greatly appreciated.



Re: Packing / unpacking IPK’s. #20 s3n0

  • Senior Member
  • 673 posts

+62
Good

Posted 13 December 2023 - 17:36

@s3n0

Thank you for the time you invested in this. I had renamed the ipk to p.ipk, the ls command shows it listed above. I missed the install a fully-fledged ar as provided by mrvica in the instructions, so that explains the other errors I got.

 

I think it would be better to spend time make scripts to replace opkg-tools. So somebody can unpack an ipk, modify it as required, repack it again. Or create an ipk from scratch. This is beyond my abilities. Especially as some components of plugins unpack as .gz and others as .xz. The use case scenario for me (just modify the control file) no longer applies.

Hi. I personally do not use OPKG-TOOLS. I only use the mentioned shell-script (the sample script is on my GitHub, but you have to modify it according to your own needs) - to create an IPK package. But that is another case. Unpacking is not used there, but only packing. And also working with the prepared plugin code from its creator (in the plugin folder "/usr/lib/enigma2/python/Plugins/Extensions/xxxxxxxx").

 

I know from my own experience that the AR tool, as a kind of "merger" of files, behaves differently when merging and separating files. If you don't use full-fledged AR, it behaves differently in one of the cases (I don't remember whether merging or separating). As @mrvica wrote, if a proper AR tool is not available (on the Enigma2 feed-server), then it is better to use a binary file (from a trusted source of course). I also have both arm and mips binaries for the AR tool.


Edited by s3n0, 13 December 2023 - 17:39.



2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users