borgmatic diff uses arguments that borg does not understand #1327
Labels
No labels
blocked
breaking
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No milestone
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
borgmatic-collective/borgmatic#1327
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
I want to diff 2 archives.
I have
exclude_if_present: ['.nobackup']im my borgmatic yaml:After commenting
exclude_if_present:After commenting
exclude_caches: trueandkeep_exclude_tags: truethe command finally runs.Steps to reproduce
Configure
exclude_caches: true,keep_exclude_tags: trueorexclude_if_present: ['something']Actual behavior
No response
Expected behavior
Works without messing with config files first.
Other notes / implementation ideas
No response
borgmatic version
2.1.6
borgmatic installation method
dnf
Borg version
1.4.4
Python version
Python 3.14.6
Database version (if applicable)
No response
Operating system and version
Fedora
Experiencing the same behavior here also with borgmatic 2.1.6. Diff should automatically refrain from adding to the borg diff command line those arguments that borg diff cannot understand. Currently
borgmatic diffis broken with most configurations, but creating the "parameter filter" should fix it, thanks for the tool!@agross thanks for filing this! And thanks to @callegar as well for weighing in. This issue is now fixed in main and will be part of the next release. Let me know if you find any other configuration options that break the
diffaction.. I found and fixed three others as part of this ticket, all of them related to excludes.Released in borgmatic 2.1.7!