borgmatic-collective/borgmatic
borgmatic-collective
/
borgmatic
15
57
Fork 40
Code Issues 54 Pull Requests 1 Actions Packages Releases 121 Activity

Using parameter "--repository <LABEL>" print error "Repository <LABEL> found in multiple configuration files" #818

New Issue
Closed
opened 2024-01-19 22:08:54 +00:00 by borg.haefemeier · 3 comments
borg.haefemeier commented 2024-01-19 22:08:54 +00:00
Copy Link

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

  • define multiple configuration files (default /etc/borgmatic/config.yaml and list of configuration in /etc/borgmatic.d)
  • add in each a repositories section
repositories:
  - path: /path/backup
     label: local.repo
  - path: ssh:user@remote:/path/backup
     label: remote.repo
  • call 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)"

### 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 - define multiple configuration files (default `/etc/borgmatic/config.yaml` and list of configuration in `/etc/borgmatic.d`) - add in each a repositories section ``` repositories: - path: /path/backup label: local.repo - path: ssh:user@remote:/path/backup label: remote.repo ``` - call `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)"
borg.haefemeier changed title from 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" 2024-01-19 22:09:21 +00:00
witten commented 2024-01-22 02:17:25 +00:00
Owner
Copy Link

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!

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!
witten commented 2024-01-22 02:26:46 +00:00
Owner
Copy Link

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.

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.
witten commented 2024-01-31 18:56:17 +00:00
Owner
Copy Link

Released in borgmatic 1.8.8!

Released in borgmatic 1.8.8!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
spot-check
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   
bug

   
data loss

   
design finalized

   
good first issue

   
new feature area

   
question / support

   
security

   
waiting for response
No Label
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#818
No description provided.
Delete Branch "%!s(<nil>)"

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?