Using parameter "--repository <LABEL>" print error "Repository <LABEL> found in multiple configuration files" #818
Loading…
x
Reference in New Issue
Block a user
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 defined several configuration files to backup per applications and define multiple repositories, but in each config file the same repo definition (add per include). Now I try to call
borgmatic list --repository repo1
and print the error. message "Repository local found in multiple configuration files".Steps to reproduce
/etc/borgmatic/config.yaml
and list of configuration in/etc/borgmatic.d
)borgmatic list --repository local.repo
Actual behavior
Repository local.repo found in multiple configuration files
summary:
/etc/borgmatic/config.yaml: Loading configuration file
/etc/borgmatic.d/config-2.yaml: Loading configuration file
/etc/borgmatic.d/config-3.yaml: Loading configuration file
Repository local found in multiple configuration files
Need some help? https://torsion.org/borgmatic/#issues
Expected behavior
No error message and command behavior as defined, but print only archives for one repository.
Other notes / implementation ideas
No response
borgmatic version
1.8.6
borgmatic installation method
Fedora package via 'dnf'
Borg version
1.2.7
Python version
3.12.1
Database version (if applicable)
No response
Operating system and version
NAME="Fedora Linux" VERSION="39 (Server Edition)"
Using parameter "--repository <LABEL>" print error "Repository local found in multiple configuration files"to Using parameter "--repository <LABEL>" print error "Repository <LABEL> found in multiple configuration files"Thanks for filing this. I believe the original rationale for the error message you're seeing is that borgmatic can't match the requested
--repository
value to a single repo in a single configuration file, and therefore it gives up. I suppose though that the restriction could be lifted so that it applies each matching configuration file with that one requested repository. I don't know offhand though how possible that is based on the code. I'll look into it!Looks like there was no good reason for this restriction, so I've simply removed it. Thanks again for suggesting this! The change will be part of the next release.
Released in borgmatic 1.8.8!