Extend extra_borg_options with other commands #1103

New issue

Closed

opened 2025-05-29 07:40:23 +00:00 by etkecc · 3 comments

etkecc commented 2025-05-29 07:40:23 +00:00

Copy link

What I'd like to do and why

Hello,

Please support more borg commands in the extra_borg_options dict (I care about borg info specifically).

I'm using rsync.net for borg repositories, and starting from May 16 2025 they require extra args (specifically, --remote-path) to be set when using borgbackup.

Unfortunately, currently borgmatic does not have borg info support in the extra_borg_options dict, and thus my usual flow of repo init/backup/check fails with

May 29 04:33:21 myhost borgmatic[1084854]: Command '('borg', 'info', '--json', 'ssh://user@user.rsync.net/./yourborgbackup')' returned non-zero exit status 81.

Other notes / implementation ideas

Here is an excerpt from rsync.net's alert:

As discussed in previous announcements, we now require a "--remote-path" argument when using borg.

The backups (above) are likely failing at this moment and require minor command adjustments to restore proper functionality.

To fix this:

Adjust your borg command to add a "--remote-path" argument to indicate which branch you want to use, here are some examples:

borg list --remote-path=borg12 user@user.rsync.net:yourborgbackup

'borg12' will call the lastest version we offer in the 1.2.x series (currently 1.2.8)

borg list --remote-path=borg14 user@user.rsync.net:yourborgbackup

'borg14' will call the lastest version we offer in the 1.4.x series (currently 1.4.0)

The full list of 'borg' binaries and the corresponding "--remote-path" argument that may be called is:

--remote-path=borg0 (borg v0.29)
--remote-path=borg12 (1.2.x branch)
--remote-path=borg14 (1.4.x branch)

Please let us know if you have any questions about these changes.

Thank you for your continued business.

-rsync.net Support

### What I'd like to do and why Hello, Please support more borg commands in the `extra_borg_options` dict (I care about `borg info` specifically). I'm using rsync.net for borg repositories, and starting from May 16 2025 they require extra args (specifically, `--remote-path`) to be set when using borgbackup. Unfortunately, currently borgmatic does not have `borg info` support in the `extra_borg_options` dict, and thus my usual flow of repo init/backup/check fails with ``` May 29 04:33:21 myhost borgmatic[1084854]: Command '('borg', 'info', '--json', 'ssh://user@user.rsync.net/./yourborgbackup')' returned non-zero exit status 81. ``` ### Other notes / implementation ideas Here is an excerpt from rsync.net's alert: As discussed in previous announcements, we now require a "--remote-path" argument when using borg. The backups (above) are likely _failing_ at this moment and require minor command adjustments to restore proper functionality. To fix this: Adjust your borg command to add a "--remote-path" argument to indicate which branch you want to use, here are some examples: borg list --remote-path=borg12 user@user.rsync.net:yourborgbackup 'borg12' will call the lastest version we offer in the 1.2.x series (currently 1.2.8) borg list --remote-path=borg14 user@user.rsync.net:yourborgbackup 'borg14' will call the lastest version we offer in the 1.4.x series (currently 1.4.0) The full list of 'borg' binaries and the corresponding "--remote-path" argument that may be called is: --remote-path=borg0 (borg v0.29) --remote-path=borg12 (1.2.x branch) --remote-path=borg14 (1.4.x branch) Please let us know if you have any questions about these changes. Thank you for your continued business. -rsync.net Support

witten commented 2025-05-29 16:33:18 +00:00

Owner

Copy link

Thanks for filing this. To add a remote path to all borg info commands that borgmatic issues, you can just set the existing remote_path option in configuration. If you find that that's not the case, please let me know.

As for fleshing out extra_borg_options, there's already a ticket for that: #427.

Thanks for filing this. To add a remote path to all `borg info` commands that borgmatic issues, you can just set the existing `remote_path` option in configuration. If you find that that's not the case, please let me know. As for fleshing out `extra_borg_options`, there's already a ticket for that: #427.

witten added the

question / support

label 2025-05-29 16:33:24 +00:00

etkecc commented 2025-05-29 19:29:54 +00:00

Author

Copy link

Thank you for the details!

It looks like I've completely missed the existing remote_path config option

Thank you for the details! _It looks like I've completely missed the existing `remote_path` config option_

etkecc closed this issue 2025-05-29 19:29:54 +00:00

witten commented 2025-05-29 20:14:52 +00:00

Owner

Copy link

No worries!

No worries!

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

parallel-borgmatic

command-hook-steps

2.1.7

2.1.6

2.1.5

2.1.4

2.1.3

2.1.2

2.1.1

2.1.0

2.0.13

2.0.12

2.0.11

2.0.10

2.0.9

2.0.8

2.0.7

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

  

breaking

  

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No labels

blocked

breaking

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

Subscribe

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#1103

No description provided.