borgmatic-collective/borgmatic
borgmatic-collective/borgmatic
Watch
9
74
Fork
You've already forked borgmatic
 57
Code Issues 71 Pull requests 3 Releases 162 Packages 1 Activity Actions 1

borgmatic config generate --source deactivates vital option(s) #1337

New issue
Open
opened 2026-07-27 12:29:27 +00:00 by reibuehl · 1 comment
reibuehl commented 2026-07-27 12:29:27 +00:00
Copy link

What I'm trying to do and why

I have upgraded from Debian 12 to Debian 13. After the upgrade I got warning messages from borgmatic about "Configuration sections (like location:, storage:, retention:, consistency:, and hooks:) are deprecated and support will be removed from a future release.". I tried to upgrade my configuration with the command borgmatic config generate --source config.yaml --destination config-new.yaml
When I run borgmatic with the new config, I get the error message "can not acquire a passphrase: BORG_PASSPHRASE is not set. BORG_PASSCOMMAND is not set. Interactive password query failed." and the whole backup fails.
Closer inspection of the two config files showed that in the old one encryption_passphrase is set but in the new one, encryption_passphrase is commented out.
Is this to be expected and if so, why?

Steps to reproduce

Process the attached sanitized config with borgmatic config generate --source oldconfig.yaml --destination newconfig.yaml

Actual behavior

The resulting newconfig.yaml contains the correct encryption_passphrase but it is commented out:
# encryption_passphrase: secret

Expected behavior

Used options stay active in the configuration unless they are not supported anymore. If they are not supported anymore, a warning message is displayed that directs to a migration documentation for the obsolete configuration line.

Other notes / implementation ideas

No response

borgmatic version

1.9.14

borgmatic installation method

Debian package

Borg version

borg 1.4.0

Python version

Python 3.13.5

Database version (if applicable)

No response

Operating system and version

PRETTY_NAME="Debian GNU/Linux 13 (trixie)" NAME="Debian GNU/Linux" VERSION_ID="13" VERSION="13 (trixie)" VERSION_CODENAME=trixie DEBIAN_VERSION_FULL=13.6 ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"

### What I'm trying to do and why I have upgraded from Debian 12 to Debian 13. After the upgrade I got warning messages from borgmatic about "Configuration sections (like location:, storage:, retention:, consistency:, and hooks:) are deprecated and support will be removed from a future release.". I tried to upgrade my configuration with the command `borgmatic config generate --source config.yaml --destination config-new.yaml` When I run borgmatic with the new config, I get the error message "`can not acquire a passphrase: BORG_PASSPHRASE is not set. BORG_PASSCOMMAND is not set. Interactive password query failed.`" and the whole backup fails. Closer inspection of the two config files showed that in the old one encryption_passphrase is set but in the new one, encryption_passphrase is commented out. Is this to be expected and if so, why? ### Steps to reproduce Process the attached sanitized config with `borgmatic config generate --source oldconfig.yaml --destination newconfig.yaml` ### Actual behavior The resulting newconfig.yaml contains the correct encryption_passphrase but it is commented out: `# encryption_passphrase: secret ` ### Expected behavior Used options stay active in the configuration unless they are not supported anymore. If they are not supported anymore, a warning message is displayed that directs to a migration documentation for the obsolete configuration line. ### Other notes / implementation ideas _No response_ ### borgmatic version 1.9.14 ### borgmatic installation method Debian package ### Borg version borg 1.4.0 ### Python version Python 3.13.5 ### Database version (if applicable) _No response_ ### Operating system and version PRETTY_NAME="Debian GNU/Linux 13 (trixie)" NAME="Debian GNU/Linux" VERSION_ID="13" VERSION="13 (trixie)" VERSION_CODENAME=trixie DEBIAN_VERSION_FULL=13.6 ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"
oldconfig.yaml
739 B
witten commented 2026-08-16 20:33:21 +00:00
Owner
Copy link

That's a reasonable expectation, IMO! It looks like this a bug in old versions of borgmatic that has since been fixed. Apparently it was fixed in 2.0.0, so I recommend upgrading to at least that version. Or better yet, upgrade to a modern release like 2.1.7 if you can.

I realize that Debian stable includes pretty ancient versions of borgmatic (1.9.14 is almost 1.5 years old!), but maybe you can pull borgmatic from Debian testing or use one of the other installation methods.

Hope that helps!

That's a reasonable expectation, IMO! It looks like this a bug in old versions of borgmatic that has since been fixed. Apparently it was fixed in 2.0.0, so I recommend upgrading to at least that version. Or better yet, upgrade to a modern release like 2.1.7 if you can. I realize that Debian stable includes pretty ancient versions of borgmatic (1.9.14 is almost 1.5 years old!), but maybe you can pull borgmatic from Debian testing or use one of the [other installation methods](https://torsion.org/borgmatic/how-to/install-borgmatic/). Hope that helps!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
parallel-borgmatic
command-hook-steps
2.1.7
2.1.6
2.1.5
2.1.4
2.1.3
2.1.2
2.1.1
2.1.0
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.1
2.0.0
1.9.14
1.9.13
1.9.12
1.9.11
1.9.10
1.9.9
1.9.8
1.9.7
1.9.6
1.9.5
1.9.4
1.9.3
1.9.2
1.9.1
1.9.0
1.8.14
1.8.13
1.8.12
1.8.11
1.8.10
1.8.9
1.8.8
1.8.7
1.8.6
1.8.5
1.8.4
1.8.3
1.8.2
1.8.1
1.8.0
1.7.15
1.7.14
1.7.13
1.7.12
1.7.11
1.7.10
1.7.9
1.7.8
1.7.7
1.7.6
1.7.5
1.7.4
1.7.3
1.7.2
1.7.1
1.7.0
1.6.6
1.6.5
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
1.5.24
1.5.23
1.5.22
1.5.21
1.5.20
1.5.19
1.5.18
1.5.17
1.5.16
1.5.15
1.5.14
1.5.13
1.5.12
1.5.11
1.5.10
1.5.9
1.5.8
1.5.7
1.5.7.dev0
1.5.6
1.5.5
1.5.4
1.5.3
1.5.2
1.5.1
1.5.0
1.4.22
1.4.21
1.4.20
1.4.19
1.4.18
1.4.17
1.4.16
1.4.15
1.4.14
1.4.13
1.4.12
1.4.11
1.4.10
1.4.9
1.4.8
1.4.7
1.4.6
1.4.5
1.4.4
1.4.3
1.4.2
1.4.1
1.4.0
1.3.26
1.3.25
1.3.24
1.3.23
1.3.22
1.3.21
1.3.20
1.3.19
1.3.18
1.3.17
1.3.16
1.3.15
1.3.14
1.3.13
1.3.12
1.3.11
1.3.10
1.3.9
1.3.8
1.3.7
1.3.6
1.3.5
1.3.4
1.3.3
1.3.2
1.3.1
1.3.0
1.2.18
1.2.17
1.2.16
1.2.15
1.2.14
1.2.13
1.2.12
1.2.11
1.2.10
1.2.9
1.2.8
1.2.7
1.2.6
1.2.5
1.2.4
1.2.3
1.2.2
1.2.1
1.2.0
1.1.15
1.1.14
1.1.13
1.1.12
1.1.11
1.1.10
1.1.9
1.1.7
1.1.6
1.1.5
1.1.4
1.1.3
1.1.2
1.1.1
1.1.0
1.0.3
1.0.2
1.0.1
1.0.0
0.1.8
0.1.7
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
0.1.0
0.0.7
0.0.6
0.0.5
0.0.4
0.0.3
0.0.2
Labels
Clear labels   
blocked

   
breaking

   
bug

   
data loss

   
design finalized

   
good first issue

   
new feature area

   
question / support

   
security

   
waiting for response
No labels
blocked
breaking
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
borgmatic-collective/borgmatic#1337
No description provided.