Tvheadend

Ok, but is it a transitional situation created by recent builds or it is normal that such collision can appear? I didn't play with configuration files (coping files from one config/backup to others or stuff like this...).

It's one time issue. The problem is that tvh didn't load some epggrab files before, thus may create duplicates, because the uuids were not tracked. In this case, the previously untracked files create issues.

skipping with a message would have been better than crashing.

The problem is that it's universal routine and I don't feel that it should continue if this configuration problem rises. Simply, I cannot decide which configuration is valid at this point.

Jaroslav Kysela wrote:

The problem is that it's universal routine and I don't feel that it should continue if this configuration problem rises. Simply, I cannot decide which configuration is valid at this point.

Why not a middle ground, exit with an error?

I'm not sure to understand. Can these conflicts exist coming from a stable installation? It is not acceptable that new stable release to crash after the upgrade.

See http://tvheadend.org/issues/3387
Upgraded from 4.1.563 to 4.1.1163. Stable configuration, after upgrade crash due to conflict in /dvr

+1 for database-based config