TW
I don't want to make transfer more complex than it already is (like by adding archive renaming). The (likely few) users with exceedingly long archive names will have to shorten...
Note: this was created by Junie AI and it would be good if there was some review by someone who is good with css and frontend stuff.
I remember that topic was discussed back then, but it somehow was not considered necessary/important.
borg info is dynamically computed, so yes (if the recreate changed space usage at all).
Yes, a short note for recreate is ok, but just mention `--comment` without example. For multiple recreate ops on same archive, this gets a bit tricky.
@athulpa I don't know if that is an issue with that binary, you could ask bauerj. Also, you could try to reproduce without using the binary, see our docs how...
``` Exception: Could not find crypto lib/headers, please set BORG_OPENSSL_PREFIX or ensure libcrypto.pc is in PKG_CONFIG_PATH. ``` When installing from source (that includes the pip package), you need to first...
@rschuetz Yes, theoretically we could unify some parts of check that need to read all data from all repo objects. As borg 1.x "check" is designed right now, it's difficult...
There is also #8514 and the idea to use flags for each repo object to avoid reading it multiple times.
https://github.com/OpenIndiana/vagrantfiles/issues/8