mirror of
https://github.com/borgbackup/borg.git
synced 2026-09-01 14:13:19 +02:00
9ff9eb436fborg called platformdirs with the appname only, so on Windows the appauthor component defaulted to the appname and all default directories ended up under a doubled AppData\...\borg\borg path. Pass appauthor=False everywhere (no vendor directory level; on Linux/macOS the appauthor is unused, so nothing changes there) and roaming=True for the config dir, restoring the layout the CHANGES upgrade notes had documented as intended all along: - config (incl. keys): C:\Users\<user>\AppData\Roaming\borg (follows the user's roaming profile in domain environments) - data (incl. security state): C:\Users\<user>\AppData\Local\borg - cache: C:\Users\<user>\AppData\Local\borg\Cache - runtime: C:\Users\<user>\AppData\Local\Temp\borg This matches what comparable tools do on Windows (pip, rclone and kopia keep the configuration in the roaming AppData and machine state/caches in the local AppData, all without a vendor directory). The cache keeps platformdirs' opinionated "Cache" subdir so the CACHEDIR.TAG written into the cache root stays out of the data dir. Only Windows is affected. The first Windows binary was only released with 2.0.0b23, so beta users needing to migrate should be rare: move the keys from the old %LOCALAPPDATA%\borg\borg\keys to the new location (or set the BORG_* dir env vars to the old paths); cache and security state are recreated as needed. Docs: update the environment help topic (and the generated environment.rst.inc), FAQ, key/transfer usage docs and CHANGES. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| archive-specification.rst.inc | ||
| config.rst.inc | ||
| date-time.rst.inc | ||
| environment.rst.inc | ||
| file-metadata.rst.inc | ||
| file-systems.rst.inc | ||
| logging.rst.inc | ||
| positional-arguments.rst.inc | ||
| repository-locations.rst.inc | ||
| repository-urls.rst.inc | ||
| resources.rst.inc | ||
| return-codes.rst.inc | ||
| units.rst.inc | ||