handle upgrading repositories initialized with --version=9

As was attempted earlier in the buggy commit 0d2e3058ee

Avoided the bug that had by making the upgrade log be updated after each
upgrade step. So, after upgrade from v8 to v9, the log is updated, and
so Upgrade.V9's timeOfUpgrade check will find that it was upgraded
recently and so won't let it skip ahead to v10.

Sponsored-by: k0ld on Patreon
This commit is contained in:
Joey Hess 2022-09-26 12:55:51 -04:00
parent 8230f4a6f1
commit e05dd70544
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 19 additions and 21 deletions

View file

@ -16,3 +16,4 @@ git config annex.version
10.20220822 Linux
> [[fixed|done]] --[[Joey]]

View file

@ -8,7 +8,7 @@ which was included in version 10.20220822.
I've reverted the commit as a first step. This means repos initialized
at v9 will never autoupgrade to v10, which will need to be fixed
somehow.
somehow. (Update: Fixed that now.)
Gonna need to make a git-annex release ASAP to get this fix out there.
"""]]