yadm (3.0.2-1) unstable; urgency=medium yadm now supports openssl in addition to gpg for encryption. Along with this change, the encrypted archive is now called archive instead of the old name files.gpg. yadm now uses the XDG Base Directory Specification to find its data. For the majority of users, this means data will now be in $HOME/.local/share/yadm/ instead of the old location of $HOME/.config/yadm/. This location is used for the local repository and encrypted archive. The easiest way to adopt these new paths is to use the yadm upgrade command. This command will move your existing repo and encrypted archive to the new directory. Upgrading will also re-initialize all submodules you have added (otherwise they will be broken when the repo moves). For more information about the necessary changes, please see the following link: - https://yadm.io/docs/upgrade_from_2# -- Angel Abad Sun, 31 Jan 2021 10:45:01 +0100 yadm (2.3.0-1) unstable; urgency=medium Beginning with version 2.0.0, yadm introduced a few major changes which may require you to adjust your configurations. If you want to retain yadm’s old behavior until you transition your configurations, you can set the environment variable YADM_COMPATIBILITY=1. Doing so will automatically use the old yadm directory, and process alternates the same as version 1. This compatibility mode is deprecated, and will be removed in future versions. This mode exists solely for transitioning to the new paths and naming of alternates. For more information about the necessary changes, please see the following link: - https://yadm.io/docs/upgrade_from_1 -- Angel Abad Sun, 16 Feb 2020 19:06:33 +0100