pharo-project
What happens when a new keyfile repo is created at the same path?
Bug description
During loading a GitHub project an error appears when I click to the red cross button in the loading bar:
I'm with a limited and not stable connexion, that's why I think this is not releated to the project because I succeed to load in an other way.
This problem appears after this error:
Version information:
- OS: Windows 10 Pro
- Version VM: 10.3.0.0
- Pharo-12.0.0+SNAPSHOT.build.1521
It seems to be handled correctly, though, and the correct key is used. (Does it test all existing keyfiles until one is found that fits?)
IIRC, the repo ID is used to identify the right key. And when generating the key filename, it uses a new name, even the repo path is the same.
We could also store the repo key under REPOID.key or so, maybe that would smell less like a problem.
I renamed the keyfile, and borg found it anyway, so it really seems to try all files in there.