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

Trouble running custom config #687

New Issue
Closed
opened 2023-04-30 21:53:01 +00:00 by Soumik_Dutta · 4 comments
Soumik_Dutta commented 2023-04-30 21:53:01 +00:00
Contributor
Copy Link

What I'm trying to do and why

I am trying to run borgmatic via borgmatic --config=test.yaml

Steps to reproduce (if a bug)

  • Clone borgmatic locally by git clone https://projects.torsion.org/borgmatic-collective/borgmatic
  • Create and activate a virtualenv by
    • virtualenv .venv
    • source .venv/bin/activate
  • Run pip3 install --editable .
  • Create a test config at the root borgmatic folder
  • Run borgmatic --config=test.yaml

Actual behavior (if a bug)

Produces errors:

test.yaml: No valid configuration files found

summary:
test.yaml: Error parsing configuration file
Configuration file schema could not be found
test.yaml: No valid configuration files found

Need some help? https://torsion.org/borgmatic/#issues

Expected behavior (if a bug)

Runs the config file without errors

Other notes / implementation ideas

NA

Environment

borgmatic version: 1.7.13.dev0

borgmatic installation method: Cloned the repo and created a locally editable installation via pip3

Borg version: borg 1.2.3

Python version: 3.10.6

operating system and version: Pop!_OS 22.04 with kernel 6.2.6-76060206-generic x86_64 x86_64 GNU/Linux with all the latest updates as of May 1

#### What I'm trying to do and why I am trying to run borgmatic via `borgmatic --config=test.yaml` #### Steps to reproduce (if a bug) - Clone borgmatic locally by `git clone https://projects.torsion.org/borgmatic-collective/borgmatic` - Create and activate a virtualenv by - `virtualenv .venv` - `source .venv/bin/activate` - Run `pip3 install --editable .` - Create a test config at the root borgmatic folder - Run `borgmatic --config=test.yaml` #### Actual behavior (if a bug) Produces errors: ``` test.yaml: No valid configuration files found summary: test.yaml: Error parsing configuration file Configuration file schema could not be found test.yaml: No valid configuration files found Need some help? https://torsion.org/borgmatic/#issues ``` #### Expected behavior (if a bug) Runs the config file without errors #### Other notes / implementation ideas NA #### Environment **borgmatic version:** 1.7.13.dev0 **borgmatic installation method:** Cloned the repo and created a locally editable installation via `pip3` **Borg version:** borg 1.2.3 **Python version:** 3.10.6 **operating system and version:** `Pop!_OS 22.04` with kernel `6.2.6-76060206-generic x86_64 x86_64 GNU/Linux` with all the latest updates as of May 1
witten commented 2023-04-30 23:01:43 +00:00
Owner
Copy Link

Thanks for filing this, including all the reproduction steps. I did manage to repro the issue when using --editable both in a virtualenv and without one. It does not repro however when installing without --editable.

I'm guessing this issue was introduced by 8cb5a42a9e, which touched the schema-loading code.

Thanks for filing this, including all the reproduction steps. I did manage to repro the issue when using `--editable` both in a virtualenv and without one. It does not repro however when installing *without* `--editable`. I'm guessing this issue was introduced by 8cb5a42a9e156f126faf3797fff55a8bf95f4b61, which touched the schema-loading code.
witten added the
bug
 label 2023-04-30 23:01:50 +00:00
witten commented 2023-04-30 23:25:35 +00:00
Owner
Copy Link

I believe I have a fix checked in now (in main). Please give it a shot when you get a chance and let me know if your copy of borgmatic is able to find the schema. Thanks!

I believe I have a fix checked in now (in main). Please give it a shot when you get a chance and let me know if your copy of borgmatic is able to find the schema. Thanks!
Soumik_Dutta commented 2023-05-01 19:17:44 +00:00
Author
Contributor
Copy Link

Thanks! Now everything is working fine again.

Thanks! Now everything is working fine again.
🎉 1
witten commented 2023-05-16 17:03:43 +00:00
Owner
Copy Link

This was just released in borgmatic 1.7.13!

This was just released in borgmatic 1.7.13!
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#687
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?