Project

General

Profile

Forums » General »

4.0 to 4.2 upgrade good practices regarding configuration

Added by Ansett San over 7 years ago

Hi.

I'm on Libreelec and I installed the new TVH4.2 service, removed the old one, then copied the old /storage/.kodi/addons/service.multimedia.tvheadend over the new /storage/.kodi/addons/service.tvheadend42 so I wouldn't have to reconfigure all the channels and such.

But then I stumbled upon an issue where I couldn't read the aborted recordings. That's because the "Failed view" flags was off on all access profiles, because indeed this flag didn't exist in the old configuration files.

So is there a way to upgrade more cleanly without losing the current configuration ?


Replies (2)

RE: 4.0 to 4.2 upgrade good practices regarding configuration - Added by Mark Clarkstone over 7 years ago

Renaud Merle wrote:

Hi.

I'm on Libreelec and I installed the new TVH4.2 service, removed the old one, then copied the old /storage/.kodi/addons/service.multimedia.tvheadend over the new /storage/.kodi/addons/service.tvheadend42 so I wouldn't have to reconfigure all the channels and such.

But then I stumbled upon an issue where I couldn't read the aborted recordings. That's because the "Failed view" flags was off on all access profiles, because indeed this flag didn't exist in the old configuration files.

So is there a way to upgrade more cleanly without losing the current configuration ?

Tvheadend once upgraded should migrate the config, however not all situations/config changes are accounted for, thus things like this happen. :(

Please open a bug report.

RE: 4.0 to 4.2 upgrade good practices regarding configuration - Added by Ansett San over 7 years ago

Ok thanks. Nice to know Tvheadend upgrades the config but it's just a bug for this one parameter.

    (1-2/2)