Incorrect release notes - TVHEADEND CHANGES

marc.bau · November 23, 2017 at 9:25 PM

Quote

Unfortunately Tvheadend does not provide an automatic upgrade or configuration export/import process so 4.0 users must perform a new installation of Tvheadend 4.2. This is inconvenient, but there is no other option.

This information seems incorrect from my point of view. I have found out that a migration is possible and not difficult. With thousands of channels and a complex configuration people should not get told there is no way to upgrade if this works.

Please see How to migrate tvheadend settings from 4.0 to 4.2? for a how-to. I'm not sure why you document this incorrectly. Can you fix this incorrect information or explain what is not working if I may missed something serious, please?

**chewitt** · November 24, 2017 at 4:58 AM Official Post

People that develop Tvheadend have advised that they do not support migration. I trust they know what they are talking about.

marc.bau · November 24, 2017 at 11:04 PM

Thanks for feedback. Good to know.

Maybe just not tested. I can assure it works without issues on my system with a DVB-S2 card.

**CvH** · November 25, 2017 at 12:45 AM Official Post

Quote from marc.bau

I can assure it works without issues on my system with a DVB-S2 card.

The huge problem is that it can created really weird issues (2/100 channels not working and such not easily debug able stuff), this was already seen frequently before. There is NO clean upgrade path - also you don't get all DB features due an upgrade (that alone is a nogo at RPi(x).