Online updates: install fail/update issue

[WOIIFTM]

Just did an online update of my Vu+ Duo running the latest VIX. 111 packages were installed but two package keep on being offered for update. I don't know if the install or the update itself fails. The packages are: inadyn-mt and enigma... (sorry the glitch in which the name is shown is just too short). Of course I reboot after every update.

[punisher]

Try doing an offline upgrade

[givecredit]

Same problem here. The offline upgrade does not work either. Keep getting flashing green icon. With 2 upgrades offered.

[punisher]

Try a reflash and then do a full update

[Rob van der Does]

Confirmed the issue: we'll look into it (it has to do with an InaDyn upgrade).

[andyblac]

try this in terminal


opkg update
opkg upgrade --force-depends

let me know

[nzdream]

Hi Andy, I got the following errror when trying to run those commands.

root@vuduo:~# opkg update
Collected errors:
* opkg_conf_load: Could not create lock file /usr/lib/opkg/lock: No space left
on device.
root@vuduo:~# opkg upgrade --force-depends
Collected errors:
* opkg_conf_load: Could not create lock file /usr/lib/opkg/lock: No space left
on device.
root@vuduo:~#

[andyblac]

Hi Andy, I got the following errror when trying to run those commands.

root@vuduo:~# opkg update
Collected errors:
* opkg_conf_load: Could not create lock file /usr/lib/opkg/lock: No space left
on device.
root@vuduo:~# opkg upgrade --force-depends
Collected errors:
* opkg_conf_load: Could not create lock file /usr/lib/opkg/lock: No space left
on device.
root@vuduo:~#

you have filled up your flash some how,

type in terminal:


df

and i bet your rootfs is full

look in /etc/enigma2 to see if there is a crossepg folder there, if there is, you need to:

Press Menu
goto Setup --> System --> EPG --> Settings

and change it your HDD or USB stick, save

then delete the crossepg folder, and re-download your data


andy.

[nzdream]

Hi Andy thanks for your help.
Yes there was a crossepg folder in /etc/enigma2 I have now deleted it and changed it to point at the hdd.
I then issued the following at the command line

root@vuduo:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 120832 107828 13004 89% /
tmpfs 64 4 60 6% /dev
/dev/sda1 1464682108 423289528 1041392580 29% /media/hdd
tmpfs 70680 788 69892 1% /var/volatile
/dev/sdb1 1957600 343552 1614048 18% /media/sdb1
root@vuduo:~# opkg update
ade --force-depends
Collected errors:
* pkg_parse_from_stream_nomalloc: Excessively long line at 6. Corrupt file?
root@vuduo:~# opkg upgrade --force-depends
Collected errors:
* pkg_parse_from_stream_nomalloc: Excessively long line at 6. Corrupt file?
root@vuduo:~#

Then reloaded the box. Now it’s just stuck on the starting vu duo screen. I think I will start a fresh with a reflash and try for there. Thanks for the help.

[nzdream]

Oh further to my last post the box did finally boot up so i tried the commands at the CLI again but got the same issue.

root@vuduo:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 120832 107912 12920 89% /
tmpfs 64 4 60 6% /dev
/dev/sda1 1464682108 423289524 1041392584 29% /media/hdd
tmpfs 70680 660 70020 1% /var/volatile
/dev/sdb1 1957600 343552 1614048 18% /media/sdb1
root@vuduo:~#
root@vuduo:~#
root@vuduo:~#
root@vuduo:~# opkg update
kg upgrade --force-dependsCollected errors:
* pkg_parse_from_stream_nomalloc: Excessively long line at 6. Corrupt file?
root@vuduo:~# opkg upgrade --force-depends
Collected errors:
* pkg_parse_from_stream_nomalloc: Excessively long line at 6. Corrupt file?
root@vuduo:~#

Don’t want to waste your time on this I am happy to just reflash. But I am also happy to fault find if its going to help others.

[Rob van der Does]

Didn't work out:


root@vuduo:~# opkg update
Downloading http://enigma2.world-of-satellite.com/feeds/2.3/release/vuduo/3rdparty/Packages.gz.
Inflating http://enigma2.world-of-satellite.com/feeds/2.3/release/vuduo/3rdparty/Packages.gz.
Updated list of available packages in /var/lib/opkg/openvix-3rdparty.
Downloading http://enigma2.world-of-satellite.com/feeds/2.3/release/vuduo/all/Packages.gz.
Inflating http://enigma2.world-of-satellite.com/feeds/2.3/release/vuduo/all/Packages.gz.
Updated list of available packages in /var/lib/opkg/openvix-all.
Downloading http://enigma2.world-of-satellite.com/feeds/2.3/release/vuduo/mipsel/Packages.gz.
Inflating http://enigma2.world-of-satellite.com/feeds/2.3/release/vuduo/mipsel/Packages.gz.
Updated list of available packages in /var/lib/opkg/openvix-mipsel.
Downloading http://enigma2.world-of-satellite.com/feeds/2.3/release/vuduo/vuduo/Packages.gz.
Inflating http://enigma2.world-of-satellite.com/feeds/2.3/release/vuduo/vuduo/Packages.gz.
Updated list of available packages in /var/lib/opkg/openvix-vuduo.

root@vuduo:~# opkg upgrade --force-depends
Multiple replacers for inadyn, using first one (inadyn-mt).
Not downgrading package inadyn on root from v.02.18.24.1-r3 to v.02.18.24+cvs20100519-r3.
Upgrading openvix-enigma2-image on root from 2.3-r20111122171950-release to 2.3-r20111208171815-release...
Downloading http://enigma2.world-of-satellite.com/feeds/2.3/release/vuduo/all/openvix-enigma2-image_2.3-r20111208171815-release_all.ipk.
Installing inadyn-mt (v.02.18.24+cvs20100519-r3) to root...
Downloading http://enigma2.world-of-satellite.com/feeds/2.3/release/vuduo/mipsel/inadyn-mt_v.02.18.24+cvs20100519-r3_mipsel.ipk.
Removing package inadyn from root...
stopping InaDyn dynamic DNS Client: inadyn... no inadyn found; none killed
You can force removal of packages with failed prerm scripts with the option:
--force-remove
Collected errors:
* pkg_run_script: package "inadyn" prerm script returned status 1.
* opkg_remove_pkg: not removing package "inadyn", prerm script failed
root@vuduo:~#

[andyblac]

try this:


opkg remove inadyn --force-depends

then


opkg upgrade

[Rob van der Does]

Sorry, that doesn't work either:


root@vuduo:~# opkg remove inadyn --force-depends
Removing package inadyn from root...
stopping InaDyn dynamic DNS Client: inadyn... no inadyn found; none killed
You can force removal of packages with failed prerm scripts with the option:
--force-remove
No packages removed.
Collected errors:
* pkg_run_script: package "inadyn" prerm script returned status 1.
* opkg_remove_pkg: not removing package "inadyn", prerm script failed
root@vuduo:~#


Looks like the same error

[andyblac]

Sorry, that doesn't work either:


root@vuduo:~# opkg remove inadyn --force-depends
Removing package inadyn from root...
stopping InaDyn dynamic DNS Client: inadyn... no inadyn found; none killed
You can force removal of packages with failed prerm scripts with the option:
--force-remove
No packages removed.
Collected errors:
* pkg_run_script: package "inadyn" prerm script returned status 1.
* opkg_remove_pkg: not removing package "inadyn", prerm script failed
root@vuduo:~#


Looks like the same error

opkg upgrade --force-remove

[Rob van der Does]

OK, that seems to have worked.

[bongo182]

hello,

i have a similar issue but with dib0700 1.0-r2, show this:

check_data_file_clashes: Package firmware-dvb-usb-dib0700-1.20 wants to install file /lib/firmware/dvb-usb-dib0700-1.20.fw
But that file is already provided by package * v4l-dvb-firmware

the solution for me was desinstall and install again the dib0700 from plugins, then no problem.

this post is for help the people that have the same problem.

Thanks

[WOIIFTM]

I had the same result as Rob on the previous command suggestions.

With opkg upgrade --force-remove this is the result:


root@vuduo:~# opkg upgrade --force-remove
Multiple replacers for inadyn, using first one (inadyn-mt).
Not downgrading package inadyn on root from v.02.18.24.1-r3 to v.02.18.24+cvs20100519-r3.
Upgrading openvix-enigma2-image on root from 2.3-r20111122171950-release to 2.3-r20111208171815-release...
Downloading http://enigma2.world-of-satellite.com/feeds/2.3/release/vuduo/all/openvix-enigma2-image_2.3-r20111208171815-release_all.ipk.
Installing inadyn-mt (v.02.18.24+cvs20100519-r3) to root...
Downloading http://enigma2.world-of-satellite.com/feeds/2.3/release/vuduo/mipsel/inadyn-mt_v.02.18.24+cvs20100519-r3_mipsel.ipk.
Removing package inadyn from root...
stopping InaDyn dynamic DNS Client: inadyn... no inadyn found; none killed
Removing any system startup links for inadyn-daemon ...
usbtunerhelper was autoinstalled and is now orphaned, removing.
Removing package usbtunerhelper from root...
stopped /usr/bin/usbtunerhelper (pid 579)
Removing any system startup links for usbtunerhelper ...
/etc/rc0.d/K20usbtunerhelper
/etc/rc1.d/K20usbtunerhelper
/etc/rc2.d/S20usbtunerhelper
/etc/rc3.d/S20usbtunerhelper
/etc/rc4.d/S20usbtunerhelper
/etc/rc5.d/S20usbtunerhelper
/etc/rc6.d/K20usbtunerhelper
Configuring inadyn-mt.
Configuring openvix-enigma2-image.
Collected errors:
* pkg_run_script: package "inadyn" prerm script returned status 1.
root@vuduo:~#

[andyblac]

I had the same result as Rob on the previous command suggestions.

With opkg upgrade --force-remove this is the result:


just try again

[WOIIFTM]

just try again

Did the trick. :thumbsup:

[wazza_2]

i did an ofline update and my mkv files wouldnt play

[MarsArtis]

I'm suffering a similar issue on 3.0build553:


root@vuduo:~# opkg update
Collected errors:
* parse_from_stream_nomalloc: Excessively long line at 7. Corrupt file?

root@vuduo:~# init 4 && opkg update && opkg upgrade && init 6
Collected errors:
* parse_from_stream_nomalloc: Excessively long line at 7. Corrupt file?

which should be the corrupted file?

could I try the opkg upgrade --force-remove too?
Would you explain what the --force-remove should do?It's not clear for me the -help description: Remove package even if prerm script fails



root@vuduo:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
ubi0:rootfs 104708 54860 49848 52% /
devtmpfs 69072 4 69068 0% /dev
tmpfs 64 0 64 0% /media
/dev/sda1 488232716 276456528 211776188 57% /media/hdd
/dev/sdb1 7848004 376344 7471660 5% /media/usb
tmpfs 69188 96 69092 0% /var/volatile
192.168.1.41:/volumes/500gb/
488384480 457419552 30964928 94% /media/net/500
192.168.1.41:/volumes/160gb/
160836480 33769248 127067232 21% /media/net/160

[MarsArtis]

wow that's weird! My second DUO is affected too (3.0build554)::


root@vuduo-s:~# [6ninit 4 && opkg update && opkg upgrade && init 6
Collected errors:
* parse_from_stream_nomalloc: Excessively long line at 6. Corrupt file?

this time it says at 6.

What's happening with VIX for DUO?