I updated apparently (I don't remember the previous version, but these are the only two in the repo) from
mythtv-0:31.0-20.158.20210711git0680b37c68.fc35.x86_64
to
mythtv-0:32.0-1.36.20220605git7077a824d2.fc35.x86_64
and got the following:
Upgrading.
2022-06-28T17:11:44.366861-07:00 mythbackend[284382]: 2022-06-28 17:11:44.363037 C Upgrading to MythTV schema version 1369
2022-06-28T17:11:44.367315-07:00 mythbackend[284382]: 2022-06-28 17:11:44.363328 E DB Error (Performing MythTV database upgrade):
2022-06-28T17:11:44.367315-07:00 mythbackend[284382]: Query was: ALTER TABLE credits ADD COLUMN priority TINYINT UNSIGNED DEFAULT 0;
2022-06-28T17:11:44.367315-07:00 mythbackend[284382]: Error was: Driver error was [2/1060]:
2022-06-28T17:11:44.367315-07:00 mythbackend[284382]: QMYSQL: Unable to execute query
2022-06-28T17:11:44.367315-07:00 mythbackend[284382]: Database error was:
2022-06-28T17:11:44.367315-07:00 mythbackend[284382]: Duplicate column name 'priority'
2022-06-28T17:11:44.367315-07:00 mythbackend[284382]: 2022-06-28 17:11:44.363338 E Database schema upgrade failed.
2022-06-28T17:11:44.367315-07:00 mythbackend[284382]: 2022-06-28 17:11:44.363776 E Couldn't upgrade database to new schema on master backend.
2022-06-28T17:11:44.368004-07:00 mythbackend[284382]: 2022-06-28 17:11:44.365241 I PowerDBus: Closing interfaces
2022-06-28T17:11:44.368004-07:00 mythbackend[284382]: 2022-06-28 17:11:44.365783 I Exiting
Apparently it had succeed with enough previous schema updates that going back to the old version of mythtv also failed because schema 1368 was too new.
Next, I tried deleting the column manually, which worked but caused the same error with the column 'roleid' which couldn't be deleted.
Since I figured this would be more a game of whack-a-mole than a smart way to approach a fix, I looked and found a somewhat similar error in this forum. I found one (upgrade to schema 1370 problem, not 1369 though) that was fixed by using the newest fixes/32 tagged git source. After building from fixes/32 and installing, I get the same error.
I'm wondering if anyone has a suggestion of what to try next?
Fedora 35, schema update from 1368 failed
Moderator: Forum Moderators
Re: Fedora 35, schema update from 1368 failed
I can show you what gets done in that version here: https://github.com/MythTV/mythtv/blob/f ... .cpp#L3802
Sounds like the table was already ALTERed. If you just cloned the repo, and checked out fixes/32, then git log -1 should show this commit:
2514e9eb4d53d4c0690ebc80f9c4b88405835129 . If the copy of your repo was old, git pull would help (but I'd guess you know that).
You can also DESC credits (and recordedcredits and roles) to see if they currently match what's being done in 1369.
Sounds like the table was already ALTERed. If you just cloned the repo, and checked out fixes/32, then git log -1 should show this commit:
2514e9eb4d53d4c0690ebc80f9c4b88405835129 . If the copy of your repo was old, git pull would help (but I'd guess you know that).
You can also DESC credits (and recordedcredits and roles) to see if they currently match what's being done in 1369.
Re: Fedora 35, schema update from 1368 failed
Thanks!
I ended up finding the commit that added schema 1368. I rolled the source back to that, rebuilt/installed, and that seems to work. I'm a bit of afraid of trying to move it to the most recent fixes/32 again, but plan on trying that when I have some more time.
Thanks again for the quick response!
I ended up finding the commit that added schema 1368. I rolled the source back to that, rebuilt/installed, and that seems to work. I'm a bit of afraid of trying to move it to the most recent fixes/32 again, but plan on trying that when I have some more time.
Thanks again for the quick response!