generate config - borgmatic 1.7.7.7 - ProxMox 8.3 #1052

New Issue

Closed

opened 2025-04-03 17:39:47 +00:00 by doguibnu · 9 comments

doguibnu commented 2025-04-03 17:39:47 +00:00

Copy Link

What I'm trying to do and why

I installed borg and borgmatic on ProxMox 8.3.

In this version, the command to generate yaml file is:
borgmatic generate config --destination /path/mypath_file.yaml

Error parsing arguments: /usr/bin/borgmatic config generate --destination /mypath/.mypath/file.yaml

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

Steps to reproduce

No response

Actual behavior

Error parsing arguments: /usr/bin/borgmatic config generate --destination /mypath/.mypath/file.yaml

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

Expected behavior

Simply generate file for me do the rest configuration

Other notes / implementation ideas

I try to use the command:
generate-borgmatic-config --destination

But, I believe this command to the borgmatic version 1.7.15

borgmatic version

borgmatic --version 1.7.7

borgmatic installation method

Debian package (apt get install

Borg version

borg --version borg 1.2.4

Python version

No response

Database version (if applicable)

No response

Operating system and version

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm 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 installed borg and borgmatic on ProxMox 8.3. In this version, the command to generate yaml file is: borgmatic generate config --destination /path/mypath_file.yaml Error parsing arguments: /usr/bin/borgmatic config generate --destination /mypath/.mypath/file.yaml Need some help? https://torsion.org/borgmatic/#issues ### Steps to reproduce _No response_ ### Actual behavior Error parsing arguments: /usr/bin/borgmatic config generate --destination /mypath/.mypath/file.yaml Need some help? https://torsion.org/borgmatic/#issues ### Expected behavior Simply generate file for me do the rest configuration ### Other notes / implementation ideas I try to use the command: generate-borgmatic-config --destination But, I believe this command to the borgmatic version 1.7.15 ### borgmatic version borgmatic --version 1.7.7 ### borgmatic installation method Debian package (apt get install ### Borg version borg --version borg 1.2.4 ### Python version _No response_ ### Database version (if applicable) _No response_ ### Operating system and version PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"

witten commented 2025-04-03 17:57:56 +00:00

Owner

Copy Link

I think you've already got your answer in your ticket! borgmatic config generate was added to borgmatic in 1.7.15, but you're using 1.7.7. So you can either upgrade (highly encouraged!) or you can use generate-borgmatic-config instead.

Let me know if I'm missing something here!

I think you've already got your answer in your ticket! `borgmatic config generate` was added to borgmatic in 1.7.15, but you're using 1.7.7. So you can either upgrade (highly encouraged!) or you can use `generate-borgmatic-config` instead. Let me know if I'm missing something here!

witten added the

question / support

label 2025-04-03 17:58:07 +00:00

doguibnu commented 2025-04-03 18:56:17 +00:00

Author

Copy Link

Yes, with command: generate-borgmatic-config ok, its generate the file yaml but the validation command does not works, so I am thinking the problem was the version reading Internet posts. I have others servers with borgmatic and works nice. I will verify the proper indentation again.

Thanks

Yes, with command: generate-borgmatic-config ok, its generate the file yaml but the validation command does not works, so I am thinking the problem was the version reading Internet posts. I have others servers with borgmatic and works nice. I will verify the proper indentation again. Thanks

witten commented 2025-04-03 19:07:24 +00:00

Owner

Copy Link

Are you validating with the same version of borgmatic you're generating with? And yeah, if indentation is off, then validation could be complaining about that. I'm happy to look at any validation error you're seeing.

Are you validating with the same version of borgmatic you're generating with? And yeah, if indentation is off, then validation could be complaining about that. I'm happy to look at any validation error you're seeing.

doguibnu commented 2025-04-04 12:14:03 +00:00

Author

Copy Link

Hello! Yes, I am validating with the same version validate-borgmatic-config --config /path/.path/teste2.yaml and try to config notify with uptime_kuma and after add apprise that I use on other server and works fine.

The error:

Error parsing configuration file
An error occurred while parsing a configuration file at /path/.path/teste2.yaml:
At the top level: Additional properties are not allowed ('uptime_kuma' was unexpected)

Yesterday I tried to fix but, can not. I am thinking that my fault doing the indentation correctly on this version

Hello! Yes, I am validating with the same version `validate-borgmatic-config --config /path/.path/teste2.yaml` and try to config notify with uptime_kuma and after add `apprise` that I use on other server and works fine. The error: ``` Error parsing configuration file An error occurred while parsing a configuration file at /path/.path/teste2.yaml: At the top level: Additional properties are not allowed ('uptime_kuma' was unexpected) ``` Yesterday I tried to fix but, can not. I am thinking that my fault doing the indentation correctly on this version

witten commented 2025-04-06 00:01:01 +00:00

Owner

Copy Link

Uptime Kuma support was added in borgmatic 1.8.13! I'm afraid you'll need to upgrade to a more modern version if you'd like that integration to work.

Uptime Kuma support was added in borgmatic 1.8.13! I'm afraid you'll need to upgrade to a more modern version if you'd like that integration to work.

doguibnu commented 2025-04-09 17:20:11 +00:00

Author

Copy Link

Hello! Is There an easy mode to upgrade borgmatic on ProxMox 8.3. Borgmatic still on 1.7.7 version on ProxMox 8.3

Hello! Is There an easy mode to upgrade borgmatic on ProxMox 8.3. Borgmatic still on 1.7.7 version on ProxMox 8.3

witten commented 2025-04-09 17:26:38 +00:00

Owner

Copy Link

I don't know how borgmatic is installed or integrated with ProxMox, but if you're able to install packages directly, you could try uninstalling the ProxMox version of borgmatic and installing it manually with pipx or via another mechanism to get a more up-to-date version.

I don't know how borgmatic is installed or integrated with ProxMox, but if you're able to install packages directly, you could try uninstalling the ProxMox version of borgmatic and [installing it manually with pipx](https://torsion.org/borgmatic/docs/how-to/set-up-backups/) or via another mechanism to get a more up-to-date version.

❤️ 1

doguibnu commented 2025-04-10 14:53:59 +00:00

Author

Copy Link

Hello!
Very nice!

I follow that you said. Installing manually with pipx
Its installed

pipx install borgmatic
 installed package borgmatic 2.0.2, installed using Python 3.11.2
 These apps are now globally available

I think that now I can do property configuration.

Thank you so much for help and attention.

Hello! Very nice! I follow that you said. `Installing manually with pipx` Its installed ``` pipx install borgmatic installed package borgmatic 2.0.2, installed using Python 3.11.2 These apps are now globally available ``` I think that now I can do property configuration. Thank you so much for help and attention.

witten commented 2025-04-10 15:44:57 +00:00

Owner

Copy Link

Sure thing! I'll close this for now, but please feel free to file another ticket if you have any issues.

Sure thing! I'll close this for now, but please feel free to file another ticket if you have any issues.

witten closed this issue 2025-04-10 15:44:57 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

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

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

No Label

question / support

Milestone

No items

No Milestone

Assignees

Clear assignees

diivi import_bot witten

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#1052

No description provided.