TW
Done for 1.4-maint branch. TODO: check master branch.
Did you follow the upgrade hints at top of the 1.2.6 changelog?
I'll reopen this ticket to make it more visible for a while - guess more people might stumble over this.
@DataBeaver sorry for the inconvenience! "more information about what's going on" - well, that's a bit much for an error msg as there can be 3 reasons for this issue....
@ndarwincorn uh, that's strange / unexpected. I checked the code and considering you have the ignore_invalid_archive_tam workaround active, it might mean that it has some issue with unexpected data types...
An archive having a valid TAM signature proves that the creator had access to the borg key. Having an invalid or no TAM signature does not prove this and borg...
I added the "bug" label - it is a bug if you see this exception **after** following the upgrade instructions.
@kljohann thanks for updating on this with tracebacks enabled, very helpful. You seem to use `borg create` with `--stats` and the stats code iterates over **all** archives in the manifest...
@kljohann OK, great that this is resolved. Just to make sure it all works as expected: Did you run `borg upgrade --archives-tam ...` on that repo? Or did you skip...
@ndarwincorn I guess you might have encountered the same issue as @kljohann - see solution above.