Skip to content

Repos added later should take higher priority.

Warning: While it would be good to cherry-pick this into 0.102.3 as a hotfix, it will bump the DB version to 68. This will mean if the user eventually updates to 0.103 then it will skip the 67 migration. If we do it the otherway, where we change the DB version on the stable branch to 67 and change the new index stuff in 0.103 to 68, then the user upgrading from 0.103-alpha1 to 0.103-alpha2 will have the migration run again (i.e. it ran as 67 for 0.103-alpha1 and then 68 for 0.103-alpha2). For this reason I propose just putting this in master.

This fix inverts the repo priority calculation, so that repos added later on in the list of repositories take a higher priority. My testing shows that it fixes the Orbot problem identified in #909 (closed).

Fixes #909 (closed) (hopefully)

Merge request reports