55 replies to this topic

[WanWizard]

As of today, the new OpenPLi 6.1-release image is public.

 

You can find the release notes, with all already known issues, in our wiki: https://wiki.openpli...eleasenotes-6.1

 

For that that:

• run OpenPLi 6.0: you can upgrade via de "Software update" option on the box. This make take 10 minutes or so, there are a lot of packages to update.
• run OpenPLi 6.1-rc: you can upgrade via the new "Flash image" option on the box. Make sure you have local storage, and choose to flash wwth a backup. Or use the old USB flash methode.
• run other images: make a backup using the autobackup plugin, flash the new image the usual way, and choose for restoring the backup on first boot of the new image.

 

Note: especially on slower boxes, and or with a slow internet connection, a "software update" may take a long time, sometimes 15 minutes or more. Don't panic, just let it finish, it will reboot when done.

[Pr2]

Hi,

 

Solo4K still running on OpenPLi 6.0, perform an online update from the menu. It mentions that 444 updates will be performed, everything went fine (at least the Solo4K restart properly) but the boot screen still mention OpenPli 6.0 2017/01/05

 

But the About mention that the Solo4K is in Openpli 6.1-release.

 

So I went again in Software update and there was 13 packages to update. After this, splash screen still mention:  OpenPli 6.0 and nothing more to update.

 

So the "only" bug so far is the splash screen which is not updated to reflect the upgrade to OpenPli 6.1

 

Just for info now that I am in OpenPLi 6.1

root@vusolo4k:~# opkg update
Downloading http://downloads.openpli.org/feeds/openpli-6-release/3rd-party/Packages.gz.
Updated source 'openpli-3rd-party'.
Downloading http://downloads.openpli.org/feeds/openpli-6-release/3rd-party-vusolo4k/Packages.gz.
Updated source 'openpli-3rd-party-vusolo4k'.
Downloading http://downloads.openpli.org/feeds/openpli-6-release/all/Packages.gz.
Updated source 'openpli-all'.
Downloading http://downloads.openpli.org/feeds/openpli-6-release/armv7ahf-neon/Packages.gz.
Updated source 'openpli-armv7ahf-neon'.
Downloading http://downloads.openpli.org/feeds/openpli-6-release/vusolo4k/Packages.gz.

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff}
span.s1 {font-variant-ligatures: no-common-ligatures}
Updated source 'openpli-vusolo4k'.

Is it normal that it still refer to openpli-6-release ?  Shouldn't point to openpli-6.1-release?

 

Pr2

Edited by Pr2, 6 January 2018 - 17:24.

[Pr2]

Hi,

 

Thanks for the quick reaction, splash screen is now fixed with an online update. :-)

 

Here is the log:

root@vusolo4k:~# opkg upgrade
Upgrading openpli-bootlogo from 6.0+20180105-r0.1 to 20180106-r0.8 on root.
Upgrading openpli-bootlogo (20180106) on root.
Downloading http://downloads.openpli.org/feeds/openpli-6-release/armv7ahf-neon/openpli-bootlogo_20180106-r0.8_armv7ahf-neon.ipk.
/dev/dvb/adapter0/video0: Device or resource busy
/dev/dvb/adapter0/video0: Device or resource busy
update-rc.d: /etc/init.d/bootlogo exists during rc.d purge (continuing)
 Removing any system startup links for bootlogo ...
  /etc/rcS.d/S21bootlogo
update-rc.d: /etc/init.d/bootlogo exists during rc.d purge (continuing)
 Removing any system startup links for bootlogo ...
Configuring openpli-bootlogo.
 Adding system startup for /etc/init.d/bootlogo.

Pr2

[WanWizard]

Is it normal that it still refer to openpli-6-release ?  Shouldn't point to openpli-6.1-release?

 

No, there is one single feed for all 6.x releases. Otherwise you will never be able to upgrade.

 

And yes, bootlogo issus should now be addressed. Build finished about 15min ago.

[dolphs]

this ​means 6.2 will be introduced shortly now as BETA while 6.1 will be the only STABLE available, thus 4 EoL and yet 6.0 to be phased out already?

Edited by dolphs, 6 January 2018 - 18:27.

[littlesat]

Develop is now on pyro and likely migrated to rocko. I think next release will be 7.0 and it might take some time. 6.0 is already ‘gone’...

Edited by littlesat, 6 January 2018 - 18:51.

[WanWizard]

this ​means 6.2 will be introduced shortly now as BETA while 6.1 will be the only STABLE available, thus 4 EoL and yet 6.0 to be phased out already?

 

No.

 

Whether or not there will be a 6.2-release (which will then be preceded with a 6.2-rc) will depend on whether or not there will be something to release (before we get to 7.0).

 

EoL only happens on new major releases, so OpenPLi 4 goes EoL when 7.0-release is out, OpenPLi 6.x will go EoL when OpenPLi 8.0-release is out. etc.

[dolphs]

cheers ​for that, was asking because of this article

It seems " 6.2 " ( atm for ARM only ) is quite an improvement under the hood, is part of this code also being used for Pli images and will that be 6.2rc ?

[fidelcastro54]

Is it possibel that's hbbtv is still not working?

Gesendet von meinem SM-T813 mit Tapatalk

Edited by fidelcastro54, 6 January 2018 - 19:18.

[Pr2]

cheers ​for that, was asking because of this article

It seems " 6.2 " ( atm for ARM only ) is quite an improvement under the hood, is part of this code also being used for Pli images and will that be 6.2rc ?

 

You are on OpenPLi site and you give a link to OpenATV.

Those are 2 differents images so please don't mix up images especially when they are from 2 different teams.

 

Pr2

[Erik Slagter]

Is it possibel that's hbbtv is still not working?

There is nothing in the release notes about HbbTV for HD receivers. So you can assume the status is as it was: it needs an update from the manufacturer.

[WanWizard]

cheers ​for that, was asking because of this article

It seems " 6.2 " ( atm for ARM only ) is quite an improvement under the hood, is part of this code also being used for Pli images and will that be 6.2rc ?

 

What exactly is the relation between an OpenATV version and an OpenPLi version?

 

Transition to Rocko (and not Roko) will be for OpenPLi 7. 

[nor50]

Stupid question late night/early morning, but what's the difference from 6.0? What will we see is different...?

[littlesat]

Don’t worry we’re also working on rocko.... develop is already on pyro..

Edited by littlesat, 7 January 2018 - 09:28.

[Erik Slagter]

Stupid question late night/early morning, but what's the difference from 6.0? What will we see is different...?

Release notes?

[Pr2]

Hi,

 

Can you please edit the 1st post to tell people to wait after the 1st reboot for the box to complete properly its first boot, especially for low CPU power boxes where the update can seems to have "crash" the box while it's not.

 

Thanks,

 

Pr2

[abra]

Is the future strategy of the OpenPli image maintenace to offer "software updates" to the new image releases, without the need to flash anymore ? For instance, if 6.1 release is installed on the receiver, the 7.0 release (or any subsequent releases) will be installed by "software update", and all the user settings such as configuration, favorite lists, plugins (third-party or not) and so on are still available in the new release ? As far as I understood, the new "software update" functionality will just actualize drivers, OpenPli image-specific settings, system settings,..., by adding/removing/upgrading/replacing the files from the previous release, is that correct ?

[abra]

Or are the software updates rather intended to be more like "flashing the new image from the remote control instead of the usb device" ?

[mymon]

its more complicated than just replacing drivers/files.. new images are compiled in new environment. Sometimes the differences are tiny (like between 6.1rc and stable) but sometimes significant enough to require clean flash (due to dependencies and libraries difference where simple upgrade would cause a lot of errors/mismatches)

The best way always is to reflash and use autobackup which these days is very flexy and powerfull - you can nearly recover all your settings (except plugins installed from non-PLi feed)

[abra]

Do the plugins (third-party or from the feed) use also other folders than "\usr\lib\enigma2\python\Plugins\Extensions" ?

Is there any wiki "step by step" description available (with screenshots if possible) about how to autobackup, flash and autorestore ?