(2024-04-07, 17:41)zacgates99 Wrote: (2024-04-07, 17:36)ashlar Wrote: (2024-04-07, 17:19)zacgates99 Wrote: First, we have posted over in the support forum. We posted here on the announcement as well to let people know it is NOT a FLAWLESS upgrade from 20.5 and is highly not advised to upgrade from 20.5 because of MAJOR FLAWS in 21.
Could you please indicate what these major flaws are? Caps not necessary, though. Thanks.
I already said it in a post on this thread and even how to replicate it. Please read by previous post on page 1 of this thread and you will have details and can test it for yourself by following the steps I listed in the post.
I actually did something reasonably similar the other day, except in my case the skin was Amber and I'm just using a local database for this machine.
As expected, I got the skin incompatible issue and warning, but in my case everything was functional aside from that (and the other addons which were also incompatible).
All I needed to do was reinstall Nexus onto the machine again, and everything worked fine again.
It sounds like somehow your install screwed up during the database migration, and in doing so messed up both the new database version and the old (Nexus) one, which is very strange as the old one should just be read and not written to at all (the migration is just to convert it to the newer one that Omega uses).
Deliberately the old versions of the database are never removed during install, in case you need to roll back. And all the major versions use a different version number, so in theory anything that you do in the new version shouldn't touch the old one at all.
That's exactly how it did for my downgrade noted above - it just picked up the Nexus version of the databases again and used them, and i manually went in and deleted the Omega versions for now.
If you need reference for which database version is for which major Kodi version, it's in the wiki -
Databases (wiki).
Of course if you've uninstalled fully then everything will be removed and you're back to fresh.
Database migrations going wrong is not unknown (especially with MySQL thrown in the mix), which is another reason why we don't touch the old versions of the database as a fallback.
But usually all you need to do is go in, remove the new (possibly corrupted) version of the databases and try the update again.