21 replies to this topic

[kalehrl]

I just updated this morning and enigma2 disappeared.

The receiver doesn't boot any more.

I successfully logged in using telnet and ftp but enigma2 no longer starts:

root@et6x00:~# enigma2
-sh: enigma2: not found
root@et6x00:~#

[ims]

and what doing: /usr/bin/enigma2

[kalehrl]

root@et6x00:~# /usr/bin/enigma2
-sh: /usr/bin/enigma2: not found
root@et6x00:~#                 

This is the last ipkgupgrade.log:

Upgrading enigma2-plugin-pli-softcamsetup from 1.0+git185+58ea7ae-r8.0 to 1.0+git187+d9a4d9d-r8.0 on root.
Downloading http://downloads.pli-images.org/feeds/openpli-4/mips32el/enigma2-plugin-pli-softcamsetup_1.0+git187+d9a4d9d-r8.0_mips32el.ipk.
Upgrading enigma2-plugin-extensions-backupsuite from 20+git105+20d06d4-r0.0 to 20+git107+e6f3a20-r0.0 on root.
Downloading http://downloads.pli-images.org/feeds/openpli-4/mips32el/enigma2-plugin-extensions-backupsuite_20+git107+e6f3a20-r0.0_mips32el.ipk.
Upgrading enigma2-plugin-extensions-vcs from 1.0-rc8 to 1.9 on root.
Downloading http://downloads.pli-images.org/feeds/openpli-4/3rd-party/enigma2-plugin-extensions-vcs_1.9_all.ipk.
enigma2 was autoinstalled and is now orphaned, removing.
Removing package enigma2 from root...
Removing obsolete file /usr/lib/enigma2/python/Plugins/Extensions/VCS/VCS.pot.
Upgrading tuxbox-common from 1+git419+6f5d64c-r0.0 to 1+git420+0030c84-r0.0 on root.
Downloading http://downloads.pli-images.org/feeds/openpli-4/all/tuxbox-common_1+git420+0030c84-r0.0_all.ipk.
Not upgrading package enigma2 which is marked replace (flags=0x184).
Configuring enigma2-plugin-pli-softcamsetup.
Configuring enigma2-plugin-extensions-backupsuite.
Configuring enigma2-plugin-extensions-vcs.
Configuring tuxbox-common.

Edited by kalehrl, 31 July 2016 - 08:43.

[kalehrl]

All fine after:

opkg install enigma2

[WanWizard]

Something wrong in the vcs package?

[goldeneye]

These enormous "goof-ups" were my reason to stop with OpenPli years ago.....
Had some stiff arguments with devs and users alike and will spare all these conversations..
OpenPli's argument: make backup before updating/flashing (a pity dFlash did not work anymore at that time so creating an NFI backup was impossible)
OpenPli's second argument: you don't need to upgrade if everything works fine..
My argument:
Why not test the result of a new build?
Why a nightly build/update if everything works fine?
Why simply 'punish' users for upgrading simply because they want to stay updated?

Only thing 'won' was the appearance of a warning text stating that OpenPli is based on beta's and updating is at own risk...

Again, I will NO LONGER participate in any heated arguments regarding this issue....

[kalehrl]

Something wrong in the vcs package?

The plugin works fine but I'm not sure about the internals.

[Taapat]

Something wrong in the vcs package?

 

If we compare the control file in the 1.0-RC8 and 1.9, we can see that in the dependencies have been removed enigma2.

If in the image is not in any other package that depend on enigma2 (which is weird), then it is logical that enigma2 is removed after vsc update.

I would recommend temporarily remove enigma2-plugin-extensions-vcs_1.9_all.ipk from feed.

[Tech]

These enormous "goof-ups" were my reason to stop with OpenPli years ago.....
Had some stiff arguments with devs and users alike and will spare all these conversations..
OpenPli's argument: make backup before updating/flashing (a pity dFlash did not work anymore at that time so creating an NFI backup was impossible)
OpenPli's second argument: you don't need to upgrade if everything works fine..
My argument:
Why not test the result of a new build?
Why a nightly build/update if everything works fine?
Why simply 'punish' users for upgrading simply because they want to stay updated?

Only thing 'won' was the appearance of a warning text stating that OpenPli is based on beta's and updating is at own risk...

Again, I will NO LONGER participate in any heated arguments regarding this issue....

So it is prooven this has nothing to do with OpenPLI at all and could happen with every image, it is a third-party plugin which removed enigma2.

[Dimitrij]

It is a strange event.

Package depend enigma2 it goes along with the default image.

That is only possible to switch off manually.

I removed the dependence on enigma2 in dozens of plugins and had no problems before.

[Dimitrij]

see

Package depend enigma2 it goes along with the default image

 

 

 

So this is not a plugin problem.

 

[Pr2]

Hi,

 

My question:

- Why does plugin need to mention the dependency on enigma2, they are plugin for enigma2 so why should they mention it as dependency?

 

I think that having some plugin mentionning enigma2 as dependency lead to the fact that each time enigma2 is updated then the plugin are updated too even if they didn't change at all.

 

Suppressing the dependency to enigma2 in every plugins will, I think, reduce the number of packages updated during online updates.

 

Pr2

[Dimitrij]

We're trying to do it.

[mirakels]

Hi,

 

My question:

- Why does plugin need to mention the dependency on enigma2, they are plugin for enigma2 so why should they mention it as dependency?

 

I think that having some plugin mentionning enigma2 as dependency lead to the fact that each time enigma2 is updated then the plugin are updated too even if they didn't change at all.

 

Suppressing the dependency to enigma2 in every plugins will, I think, reduce the number of packages updated during online updates.

 

Pr2

 

That should not be the case. The dependency just states it needs enigma2 in order to function. And an enigma-pugin needs enigma2 to run doesn't it?

A dependency does not mean that if one is upgraded the other needs to be upgraded too  (unless you specify something about required versions of a package)

[Taapat]

Superficially watching I did not find that any of the enigma2 plugins depend from enigma2, also plugins from enigma2-plugins not depend.

Enigma2 is installed in the image from openpli-enigma2-image.bb and feel that a clean image does not have any package that depends from enigma2.

 

If we install such plugin, who first depend from enigma, but in which later this dependency is removed, then enigma2 also be removed when update such plugin.

Of course this does not happen if you have installed another package that depends from enigma2.

Edited by Taapat, 1 August 2016 - 15:12.

[Dimitrij]

https://github.com/O...ma2-feed.bb#L13

DEPENDS += "enigma2"

maybe this?

Edited by Dimitrij, 1 August 2016 - 15:14.

[blzr]

openpli-enigma2-image.bb:

DEPENDS += " \
	enigma2 \
	enigma2-pliplugins \
	enigma2-plugins \
"

[Taapat]

On my Zgemma H.S with original openpli-4:

root@h3:~# opkg whatdepends enigma2
Root set:
  enigma2
What depends on root set
root@h3:~#

As I write on clean image does not have any package that depends from enigma2.

[Taapat]

But normally, if enigma2 not installed by dependence, it should stay at opkg upgrade --autoremove.
I assume that the user has made some manipulation with enigma2 package.

[Pr2]

I just test the command you mention on my ET-9000 and Solo4K and I have the same result as you mention, so indeed no plugin is linked with enigma2 (but I just install the few plugin that I need).