Testers required for OpenViX Python 3 images

[twol]

Obviously no rush, just thought I'd mention it, just in case.

sent you a message

[white_westie]

Ok - that change all works (I had left a hook in the wizard)
I will post the changes later if not done before by someone


Thanks White_Westie!!


I am assuming it will be backward compatible!

Repeated test on ET8000 running 5.4.012, and it seems work okay!

root@et8000:/media/hdd/backup/tt# which tar
/bin/tar
root@et8000:/media/hdd/backup/tt# ls -l /bin/tar
lrwxrwxrwx    1 root     root            19 May 14 18:16 /bin/tar -> /bin/busybox.nosuid
root@et8000:/media/hdd/backup/tt# tar --version
tar: unrecognized option '--version'
BusyBox v1.31.0 (2021-05-03 12:00:47 UTC) multi-call binary.

Usage: tar c|x|t [-ZzJjahvokO] [-f TARFILE] [-C DIR] [-T FILE] [-X FILE] [--exclude PATTERN]... [FILE]...

Create, extract, or list files from a tar file

root@et8000:/media/hdd/backup/tt# ls -l /tmp/backupimageversion
-rw-r--r--    1 root     root             3 Jun 12 13:43 /tmp/backupimageversion

root@et8000:/media/hdd/backup/tt# rm /tmp/backupimageversion

root@et8000:/media/hdd/backup/tt# tar -xzvf ./z1.tar.gz tmp/backupimageversion -C /
tmp/backupimageversion
root@et8000:/media/hdd/backup/tt# ls -l /tmp/backupimageversion
-rw-r--r--    1 root     root             3 Jun 12 13:43 /tmp/backupimageversion

root@et8000:/media/hdd/backup/tt# rm /tmp/backupimageversion

root@et8000:/media/hdd/backup/tt# tar -C / -xzvf ./z1.tar.gz tmp/backupimageversion
tmp/backupimageversion

root@et8000:/media/hdd/backup/tt# ls -l /tmp/backupimageversion
-rw-r--r--    1 root     root             3 Jun 12 13:43 /tmp/backupimageversion

[twol]

@All - have updated Restorewiz and BackupManager on Git.

https://github.com/OpenViX/vix-core/...7ff7a3b01bcd43
https://github.com/OpenViX/vix-core/...4c7635b83703ef

[ccs]

@All - have updated Restorewiz and BackupManager on Git.

Cheers, but isn't the problem caused by the wrong version of tar (GNU) being built in some images?

Agreed, moving the -C option does no harm, but it's been where it was for 9 years+.

[twol]

Cheers, but isn't the problem caused by the wrong version of tar (GNU) being built in some images?

Agreed, moving the -C option does no harm, but it's been where it was for 9 years+.

Both the builds of my p3 images and my own Git images are built off the same OE-A and on the same PC. So why the difference? - I have no idea & providing it works both ways not an issue.

[ccs]

Both the builds of my p3 images and my own Git images are built off the same OE-A and on the same PC. So why the difference? - I have no idea & providing it works both ways not an issue.

Surely, getting different versions of tar is the issue? What else might be happening?

[ccs]

Just a random google comes up with "BusyBox Tar shows different ownership than GNU Tar".

Might be totally irrelevent.

[BrokenUnusableAccount]

I thought I'd do a quick blind scan to see if any weird feeds had popped up at 28.2°E.
Crash:
Enigma2_crash_2021-07-17_13-04-03.log
Enigma2_debug_2021-07-17_13-03-10.log

[Huevos]

Here is the nfs issue dealt with: https://github.com/oe-alliance/oe-al...df0f50eaf05acb

[white_westie]

Surely, getting different versions of tar is the issue? What else might be happening?

For the record, I did a crosscheck between my P2 and P3 versions for busybox commands, and as far as I can see, it's only the tar command has gone standalone!

[white_westie]

Here is the nfs issue dealt with: https://github.com/oe-alliance/oe-al...df0f50eaf05acb

Thanks for info - I assume we wont see this until the next build?

[ccs]

For the record, I did a crosscheck between my P2 and P3 versions for busybox commands, and as far as I can see, it's only the tar command has gone standalone!

Cheers, here's my P3 /bin non-busybox commands.

ls -l /bin |grep -v busy
lrwxrwxrwx    1 root     root            14 Jul 17 09:34 bash -> /bin/bash.bash
-rwxr-xr-x    1 root     root        822380 Jul 10 11:30 bash.bash
lrwxrwxrwx    1 root     root            10 Jul 17 09:34 editor -> /bin/vi.sh
-rwxr-xr-x    1 root     root          2001 Jul 10 11:50 fake-hwclock
lrwxrwxrwx    1 root     root            20 Jul 17 09:34 false -> /bin/false.coreutils
-rwxr-xr-x    1 root     root         18060 Jul 10 11:37 false.coreutils
lrwxrwxrwx    1 root     root            16 Jul 17 09:34 kill -> /bin/kill.procps
-rwxr-xr-x    1 root     root         18060 Jul 10 11:36 kill.procps
-rwxr-xr-x    1 root     root         96168 Jul 10 11:07 kmod
lrwxrwxrwx    1 root     root            17 Jul 17 09:34 login -> /bin/login.shadow
-rwxr-xr-x    1 root     root         31260 Jul 10 11:22 login.shadow
lrwxrwxrwx    1 root     root            15 Jul 17 09:34 lsmod -> /bin/lsmod.kmod
lrwxrwxrwx    1 root     root             4 Jul 17 09:34 lsmod.kmod -> kmod
-rwsr-xr-x    1 root     root         38952 Jul 10 11:38 mount.util-linux
lrwxrwxrwx    1 root     root            24 Jul 17 09:34 mountpoint -> /bin/mountpoint.sysvinit
-rwxr-xr-x    1 root     root          9784 Jul 11 00:32 mountpoint.sysvinit
lrwxrwxrwx    1 root     root            19 Jul 17 09:34 pidof -> /bin/pidof.sysvinit
-rwxr-xr-x    1 root     root          9776 Jul 10 11:35 pidof.procps
lrwxrwxrwx    1 root     root            14 Jul 17 09:34 pidof.sysvinit -> /sbin/killall5
lrwxrwxrwx    1 root     root            14 Jul 17 09:34 ps -> /bin/ps.procps
-rwxr-xr-x    1 root     root         71636 Jul 10 11:35 ps.procps
lrwxrwxrwx    1 root     root            14 Jul 17 09:34 sh -> /bin/bash.bash
lrwxrwxrwx    1 root     root            14 Jul 17 09:34 su -> /bin/su.shadow
-rwsr-xr-x    1 root     root         27232 Jul 10 11:22 su.shadow
lrwxrwxrwx    1 root     root            19 Jul 17 09:34 true -> /bin/true.coreutils
-rwxr-xr-x    1 root     root         18060 Jul 10 11:37 true.coreutils
-rwxr-xr-x    1 root     root            29 Jul 10 13:04 vi.sh
lrwxrwxrwx    1 root     root            17 Jul 17 09:34 watch -> /bin/watch.procps
-rwxr-xr-x    1 root     root         18328 Jul 10 11:35 watch.procps
root@vuultimo4k:~#

[Huevos]

I thought I'd do a quick blind scan to see if any weird feeds had popped up at 28.2°E.
Crash:
Enigma2_crash_2021-07-17_13-04-03.log
Enigma2_debug_2021-07-17_13-03-10.log

Can you try this please? Goes in Python/Components/Sources.

[BrokenUnusableAccount]

Can you try this please? Goes in Python/Components/Sources.

Excellent.
No crash now.

Thank you.

[birdman]

Looks like parameter position is important now!
Does that make sense ?

It does in that it always was position dependent for GNU tar. It takes effect from where it is on the line, so paths before it do not use it whilst those after it do.
Sometimes you want things to be relative to here first, but relative to there later.

From the man page:

-C, --directory=DIR
Change to DIR before performing any operations. This option is
order-sensitive, i.e. it affects all options that follow.