New --extra-borg-options.list option is being ignored on the command line

courtney-rosenthal commented

2025-10-24 17:05:04 +00:00

What I'm trying to do and why

This is followup on issue #427 which was resolved in 2.0.10.

I believe the argument to --extra-borg-options.list is not being passed to the borg command.

Steps to reproduce

# borgmatic list -v 2 --extra-borg-options.list THIS_IS_A_BAD_OPTION

Actual behavior

The list operation runs ignoring --extra-borg-options.list

/etc/borgmatic/config.yaml: BORG_RSH=*** BORG_PASSPHRASE_FD=*** BORG_DEBUG_PASSPHRASE=*** BORG_DISPLAY_PASSPHRASE=*** BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK=*** BORG_USE_CHUNKS_ARCHIVE=*** BORG_EXIT_CODES=*** borg --version --debug --show-rc
/etc/borgmatic/config.yaml: Borg 1.4.1
ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: Running actions for repository
ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: Listing archives
ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: BORG_RSH=*** BORG_PASSPHRASE_FD=*** BORG_DEBUG_PASSPHRASE=*** BORG_DISPLAY_PASSPHRASE=*** BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK=*** BORG_USE_CHUNKS_ARCHIVE=*** BORG_EXIT_CODES=*** borg list --remote-path borg12 --glob-archives {hostname}-* --json ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan
ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: BORG_RSH=*** BORG_PASSPHRASE_FD=*** BORG_DEBUG_PASSPHRASE=*** BORG_DISPLAY_PASSPHRASE=*** BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK=*** BORG_USE_CHUNKS_ARCHIVE=*** BORG_EXIT_CODES=*** borg list --debug --show-rc --remote-path borg12 --glob-archives {hostname}-* ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan
using builtin fallback logging configuration
33 self tests completed in 0.06 seconds
SSH command line: ['ssh', '-i', '/etc/borgmatic/id_rsa', 'xxx@xxx.rsync.net', 'borg12', 'serve', '--debug']
Remote: using builtin fallback logging configuration
Remote: borg selftest disabled via BORG_SELFTEST env variable
Remote: using builtin fallback logging configuration
Remote: Initialized logging system for JSON-based protocol
Remote: Resolving repository path b'/./borg/chinacat.chez-rufus.lan'
Remote: Resolved repository path to '/data1/home/xxx/borg/chinacat.chez-rufus.lan'
Remote: Verified integrity of /data1/home/xxx/borg/chinacat.chez-rufus.lan/index.3028
TAM-verified manifest
security: read previous location 'ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan'
security: read manifest timestamp '2025-10-24T11:09:58.042058'
security: determined newest manifest timestamp as 2025-10-24T11:09:58.042058
security: repository checks ok, allowing access
chinacat-2025-04-19T15:56:59.832629  Sat, 2025-04-19 15:57:00 [fcddb2be9c8362f8a05694e8686465db22e3d3cc8e232e853fdac0176880d5bb]
chinacat-2025-04-30T03:35:01.354041  Wed, 2025-04-30 03:35:03 [968c2506aa9b003bb26b58f17608bc44c2ce94582750dc58d7a3b823a8fed255]
chinacat-2025-05-31T03:35:00.921182  Sat, 2025-05-31 03:35:02 [8282624b505eb5b9b45b410710e480d28b4b409c9a7d57a8a0fa44d3c075043a]
chinacat-2025-06-30T03:35:01.405707  Mon, 2025-06-30 03:35:04 [5ec8dd72fc032cd36e356860f6d49339e732f666977fb63815faa91a82e3c0ae]
chinacat-2025-07-31T03:35:00.545802  Thu, 2025-07-31 03:35:03 [5a2b48544acf3fde1677ece8b8eb45866155ecd31374cbedddc3329b8c710ac3]
chinacat-2025-08-31T03:35:01.086839  Sun, 2025-08-31 03:35:02 [82614f793abd753c02fc4a0fa4a2a71323f796f4e012c1c77fbb9e37de34ebf7]
chinacat-2025-09-14T03:35:00.658883  Sun, 2025-09-14 03:35:02 [06bb009cb17665732bcb116f303d1bb6e5be8024ecf704c882eb6312d84cff7f]
chinacat-2025-09-21T03:35:01.526526  Sun, 2025-09-21 03:35:03 [78dd2a725c540d6641533948c153f45ca3ad228bfb03d438f2d455505e2db85a]
chinacat-2025-09-28T03:35:00.654802  Sun, 2025-09-28 03:35:02 [960218a44a76fc8c077072b193c5ed26e583c7b59420bf44fa2761cd1948dfe4]
chinacat-2025-09-30T03:35:00.792787  Tue, 2025-09-30 03:35:02 [399960e21faa26119a05ea2d3bae5d490c0453d3c9f11e888a0885c7fd895579]
chinacat-2025-10-05T03:35:00.967595  Sun, 2025-10-05 03:35:03 [3fb0081543d3406ace30c41e741b007d9e520d5bc4b87b035bc6727232e25b44]
chinacat-2025-10-12T03:35:51.583997  Sun, 2025-10-12 03:35:57 [e6953ad6c9ecf907fee869db1e63554f42d596492449c15012a8c29034791c0f]
chinacat-2025-10-18T04:07:15.914156  Sat, 2025-10-18 04:07:17 [7568c59d01755d28d263981d84384d49b19c1771c83bc661f6628ab1d47b9ea6]
chinacat-2025-10-19T04:06:54.565851  Sun, 2025-10-19 04:06:56 [a1b556afcd97c576fee3111f6f0bca8017a0b4160692aa7bea925e436e8d931e]
chinacat-2025-10-20T04:06:56.422826  Mon, 2025-10-20 04:06:58 [5085a02bafcb546abddc8d254130b3aa08c68ff13bae2f88620c35778f36ab33]
chinacat-2025-10-21T04:06:59.003694  Tue, 2025-10-21 04:07:00 [cbb37073e95b2176ddf22084e792bdf623f67869a71d494337aef7f792c8fc09]
chinacat-2025-10-22T04:06:57.506399  Wed, 2025-10-22 04:07:00 [3a202ff47a6d3d6a009f16481f856f3b08d533401e9195d867a90897908f306a]
chinacat-2025-10-23T04:06:58.409123  Thu, 2025-10-23 04:06:59 [bbbb5e002a9bc24ac9479738f61eed5f647198269954bf58399c786269b68aaf]
chinacat-2025-10-24T04:06:54.408374  Fri, 2025-10-24 04:06:56 [6ff2c150f4d001b072c69eb435f8a1bc7591c0b1229871d1aebebe27475398f4]
RemoteRepository: 240 B bytes sent, 3.89 kB bytes received, 5 messages sent
terminating with success status, rc 0

summary:
/etc/borgmatic/config.yaml: Loading configuration file
/etc/borgmatic/config.yaml: Successfully ran configuration file

Expected behavior

Similar to this, where an error is thrown by borg:

borgmatic info -v 2 --extra-borg-options.info THIS_IS_A_BAD_OPTION 
/etc/borgmatic/config.yaml: BORG_RSH=*** BORG_PASSPHRASE_FD=*** BORG_DEBUG_PASSPHRASE=*** BORG_DISPLAY_PASSPHRASE=*** BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK=*** BORG_USE_CHUNKS_ARCHIVE=*** BORG_EXIT_CODES=*** borg --version --debug --show-rc
/etc/borgmatic/config.yaml: Borg 1.4.1
ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: Running actions for repository
ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: Displaying archive summary information
ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: BORG_RSH=*** BORG_PASSPHRASE_FD=*** BORG_DEBUG_PASSPHRASE=*** BORG_DISPLAY_PASSPHRASE=*** BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK=*** BORG_USE_CHUNKS_ARCHIVE=*** BORG_EXIT_CODES=*** borg info --remote-path borg12 --glob-archives {hostname}-* --json THIS_IS_A_BAD_OPTION ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan
usage: borg [-V] [-h] [--critical] [--error] [--warning] [--info] [--debug]
            [--debug-topic TOPIC] [-p] [--iec] [--log-json]
            [--lock-wait SECONDS] [--bypass-lock] [--show-version] [--show-rc]
            [--umask M] [--remote-path PATH] [--remote-ratelimit RATE]
            [--upload-ratelimit RATE] [--remote-buffer UPLOAD_BUFFER]
            [--upload-buffer UPLOAD_BUFFER] [--consider-part-files]
            [--debug-profile FILE] [--rsh RSH]
            <command> ...
borg: error: unrecognized arguments: ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan
ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: Error running actions for repository
ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: Command '('borg', 'info', '--remote-path', 'borg12', '--glob-archives', '{hostname}-*', '--json', 'THIS_IS_A_BAD_OPTION', 'ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan')' returned non-zero exit status 2.
/etc/borgmatic/config.yaml: Error running configuration
/etc/borgmatic/config.yaml: An error occurred

summary:
/etc/borgmatic/config.yaml: Loading configuration file
An error occurred
Error running actions for repository
Command '('borg', 'info', '--remote-path', 'borg12', '--glob-archives', '{hostname}-*', '--json', 'THIS_IS_A_BAD_OPTION', 'ssh://XXX@XXX.rsync.net/./borg/chinacat.chez-rufus.lan')' returned non-zero exit status 2.
Error running configuration

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

Other notes / implementation ideas

No response

borgmatic version

2.0.10

borgmatic installation method

pip install

Borg version

borg 1.4.1

Python version

Python 3.13.7

Database version (if applicable)

No response

Operating system and version

NAME="Manjaro Linux" PRETTY_NAME="Manjaro Linux" ID=manjaro ID_LIKE=arch BUILD_ID=rolling ANSI_COLOR="32;1;24;144;200" HOME_URL="https://manjaro.org/" DOCUMENTATION_URL="https://wiki.manjaro.org/" SUPPORT_URL="https://forum.manjaro.org/" BUG_REPORT_URL="https://manjaro.org/help/" PRIVACY_POLICY_URL="https://manjaro.org/privacy-policy/" LOGO=manjarolinux

### What I'm trying to do and why This is followup on issue #427 which was resolved in 2.0.10. I believe the argument to `--extra-borg-options.list` is not being passed to the `borg` command. ### Steps to reproduce ``` # borgmatic list -v 2 --extra-borg-options.list THIS_IS_A_BAD_OPTION ``` ### Actual behavior The `list` operation runs ignoring `--extra-borg-options.list` ``` /etc/borgmatic/config.yaml: BORG_RSH=*** BORG_PASSPHRASE_FD=*** BORG_DEBUG_PASSPHRASE=*** BORG_DISPLAY_PASSPHRASE=*** BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK=*** BORG_USE_CHUNKS_ARCHIVE=*** BORG_EXIT_CODES=*** borg --version --debug --show-rc /etc/borgmatic/config.yaml: Borg 1.4.1 ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: Running actions for repository ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: Listing archives ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: BORG_RSH=*** BORG_PASSPHRASE_FD=*** BORG_DEBUG_PASSPHRASE=*** BORG_DISPLAY_PASSPHRASE=*** BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK=*** BORG_USE_CHUNKS_ARCHIVE=*** BORG_EXIT_CODES=*** borg list --remote-path borg12 --glob-archives {hostname}-* --json ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: BORG_RSH=*** BORG_PASSPHRASE_FD=*** BORG_DEBUG_PASSPHRASE=*** BORG_DISPLAY_PASSPHRASE=*** BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK=*** BORG_USE_CHUNKS_ARCHIVE=*** BORG_EXIT_CODES=*** borg list --debug --show-rc --remote-path borg12 --glob-archives {hostname}-* ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan using builtin fallback logging configuration 33 self tests completed in 0.06 seconds SSH command line: ['ssh', '-i', '/etc/borgmatic/id_rsa', 'xxx@xxx.rsync.net', 'borg12', 'serve', '--debug'] Remote: using builtin fallback logging configuration Remote: borg selftest disabled via BORG_SELFTEST env variable Remote: using builtin fallback logging configuration Remote: Initialized logging system for JSON-based protocol Remote: Resolving repository path b'/./borg/chinacat.chez-rufus.lan' Remote: Resolved repository path to '/data1/home/xxx/borg/chinacat.chez-rufus.lan' Remote: Verified integrity of /data1/home/xxx/borg/chinacat.chez-rufus.lan/index.3028 TAM-verified manifest security: read previous location 'ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan' security: read manifest timestamp '2025-10-24T11:09:58.042058' security: determined newest manifest timestamp as 2025-10-24T11:09:58.042058 security: repository checks ok, allowing access chinacat-2025-04-19T15:56:59.832629 Sat, 2025-04-19 15:57:00 [fcddb2be9c8362f8a05694e8686465db22e3d3cc8e232e853fdac0176880d5bb] chinacat-2025-04-30T03:35:01.354041 Wed, 2025-04-30 03:35:03 [968c2506aa9b003bb26b58f17608bc44c2ce94582750dc58d7a3b823a8fed255] chinacat-2025-05-31T03:35:00.921182 Sat, 2025-05-31 03:35:02 [8282624b505eb5b9b45b410710e480d28b4b409c9a7d57a8a0fa44d3c075043a] chinacat-2025-06-30T03:35:01.405707 Mon, 2025-06-30 03:35:04 [5ec8dd72fc032cd36e356860f6d49339e732f666977fb63815faa91a82e3c0ae] chinacat-2025-07-31T03:35:00.545802 Thu, 2025-07-31 03:35:03 [5a2b48544acf3fde1677ece8b8eb45866155ecd31374cbedddc3329b8c710ac3] chinacat-2025-08-31T03:35:01.086839 Sun, 2025-08-31 03:35:02 [82614f793abd753c02fc4a0fa4a2a71323f796f4e012c1c77fbb9e37de34ebf7] chinacat-2025-09-14T03:35:00.658883 Sun, 2025-09-14 03:35:02 [06bb009cb17665732bcb116f303d1bb6e5be8024ecf704c882eb6312d84cff7f] chinacat-2025-09-21T03:35:01.526526 Sun, 2025-09-21 03:35:03 [78dd2a725c540d6641533948c153f45ca3ad228bfb03d438f2d455505e2db85a] chinacat-2025-09-28T03:35:00.654802 Sun, 2025-09-28 03:35:02 [960218a44a76fc8c077072b193c5ed26e583c7b59420bf44fa2761cd1948dfe4] chinacat-2025-09-30T03:35:00.792787 Tue, 2025-09-30 03:35:02 [399960e21faa26119a05ea2d3bae5d490c0453d3c9f11e888a0885c7fd895579] chinacat-2025-10-05T03:35:00.967595 Sun, 2025-10-05 03:35:03 [3fb0081543d3406ace30c41e741b007d9e520d5bc4b87b035bc6727232e25b44] chinacat-2025-10-12T03:35:51.583997 Sun, 2025-10-12 03:35:57 [e6953ad6c9ecf907fee869db1e63554f42d596492449c15012a8c29034791c0f] chinacat-2025-10-18T04:07:15.914156 Sat, 2025-10-18 04:07:17 [7568c59d01755d28d263981d84384d49b19c1771c83bc661f6628ab1d47b9ea6] chinacat-2025-10-19T04:06:54.565851 Sun, 2025-10-19 04:06:56 [a1b556afcd97c576fee3111f6f0bca8017a0b4160692aa7bea925e436e8d931e] chinacat-2025-10-20T04:06:56.422826 Mon, 2025-10-20 04:06:58 [5085a02bafcb546abddc8d254130b3aa08c68ff13bae2f88620c35778f36ab33] chinacat-2025-10-21T04:06:59.003694 Tue, 2025-10-21 04:07:00 [cbb37073e95b2176ddf22084e792bdf623f67869a71d494337aef7f792c8fc09] chinacat-2025-10-22T04:06:57.506399 Wed, 2025-10-22 04:07:00 [3a202ff47a6d3d6a009f16481f856f3b08d533401e9195d867a90897908f306a] chinacat-2025-10-23T04:06:58.409123 Thu, 2025-10-23 04:06:59 [bbbb5e002a9bc24ac9479738f61eed5f647198269954bf58399c786269b68aaf] chinacat-2025-10-24T04:06:54.408374 Fri, 2025-10-24 04:06:56 [6ff2c150f4d001b072c69eb435f8a1bc7591c0b1229871d1aebebe27475398f4] RemoteRepository: 240 B bytes sent, 3.89 kB bytes received, 5 messages sent terminating with success status, rc 0 summary: /etc/borgmatic/config.yaml: Loading configuration file /etc/borgmatic/config.yaml: Successfully ran configuration file ``` ### Expected behavior Similar to this, where an error is thrown by `borg`: ``` borgmatic info -v 2 --extra-borg-options.info THIS_IS_A_BAD_OPTION /etc/borgmatic/config.yaml: BORG_RSH=*** BORG_PASSPHRASE_FD=*** BORG_DEBUG_PASSPHRASE=*** BORG_DISPLAY_PASSPHRASE=*** BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK=*** BORG_USE_CHUNKS_ARCHIVE=*** BORG_EXIT_CODES=*** borg --version --debug --show-rc /etc/borgmatic/config.yaml: Borg 1.4.1 ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: Running actions for repository ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: Displaying archive summary information ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: BORG_RSH=*** BORG_PASSPHRASE_FD=*** BORG_DEBUG_PASSPHRASE=*** BORG_DISPLAY_PASSPHRASE=*** BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK=*** BORG_USE_CHUNKS_ARCHIVE=*** BORG_EXIT_CODES=*** borg info --remote-path borg12 --glob-archives {hostname}-* --json THIS_IS_A_BAD_OPTION ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan usage: borg [-V] [-h] [--critical] [--error] [--warning] [--info] [--debug] [--debug-topic TOPIC] [-p] [--iec] [--log-json] [--lock-wait SECONDS] [--bypass-lock] [--show-version] [--show-rc] [--umask M] [--remote-path PATH] [--remote-ratelimit RATE] [--upload-ratelimit RATE] [--remote-buffer UPLOAD_BUFFER] [--upload-buffer UPLOAD_BUFFER] [--consider-part-files] [--debug-profile FILE] [--rsh RSH] <command> ... borg: error: unrecognized arguments: ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: Error running actions for repository ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan: Command '('borg', 'info', '--remote-path', 'borg12', '--glob-archives', '{hostname}-*', '--json', 'THIS_IS_A_BAD_OPTION', 'ssh://xxx@xxx.rsync.net/./borg/chinacat.chez-rufus.lan')' returned non-zero exit status 2. /etc/borgmatic/config.yaml: Error running configuration /etc/borgmatic/config.yaml: An error occurred summary: /etc/borgmatic/config.yaml: Loading configuration file An error occurred Error running actions for repository Command '('borg', 'info', '--remote-path', 'borg12', '--glob-archives', '{hostname}-*', '--json', 'THIS_IS_A_BAD_OPTION', 'ssh://XXX@XXX.rsync.net/./borg/chinacat.chez-rufus.lan')' returned non-zero exit status 2. Error running configuration Need some help? https://torsion.org/borgmatic/#issues ``` ### Other notes / implementation ideas _No response_ ### borgmatic version 2.0.10 ### borgmatic installation method pip install ### Borg version borg 1.4.1 ### Python version Python 3.13.7 ### Database version (if applicable) _No response_ ### Operating system and version NAME="Manjaro Linux" PRETTY_NAME="Manjaro Linux" ID=manjaro ID_LIKE=arch BUILD_ID=rolling ANSI_COLOR="32;1;24;144;200" HOME_URL="https://manjaro.org/" DOCUMENTATION_URL="https://wiki.manjaro.org/" SUPPORT_URL="https://forum.manjaro.org/" BUG_REPORT_URL="https://manjaro.org/help/" PRIVACY_POLICY_URL="https://manjaro.org/privacy-policy/" LOGO=manjarolinux

witten commented

2025-10-25 02:50:43 +00:00

Owner

Ugh, thanks for filing this. I think what's going on is that borgmatic is applying extra_borg_options.list when --archive is specified, but not when you omit it. That's because list without --archive is actually considered repo-list under the hood (and so uses the corresponding extra_borg_options), while list with --archive is considered just list (and uses those corresponding extra_borg_options). This nuance is in place because Borg 2 (which you're not using) has completely separate list and repo-list sub-commands, so borgmatic tries to work like that while still supporting Borg 1 list-only semantics.

Anyway, this extra_borg_options behavior with list and repo_list should probably not work like it does now, because it's kind of surprising for Borg 1 users—as you've discovered. I'll look into what I can do about that. (Note to the implementer: This same issue applies to info / repo-info and delete / repo-delete.)

In the meantime, you can try setting your extra Borg options with --extra-borg-options.repo-list on the command-line or extra_borg_options -> repo_list in configuration. That should work whenever --archive is omitted.

Ugh, thanks for filing this. I think what's going on is that borgmatic *is* applying `extra_borg_options.list` when `--archive` is specified, but not when you omit it. That's because `list` without `--archive` is actually considered `repo-list` under the hood (and so uses the corresponding `extra_borg_options`), while `list` with `--archive` is considered just `list` (and uses *those* corresponding `extra_borg_options`). This nuance is in place because Borg 2 (which you're not using) has completely separate `list` and `repo-list` sub-commands, so borgmatic tries to work like that while still supporting Borg 1 `list`-only semantics. Anyway, this `extra_borg_options` behavior with `list` and `repo_list` should probably *not* work like it does now, because it's kind of surprising for Borg 1 users—as you've discovered. I'll look into what I can do about that. (Note to the implementer: This same issue applies to `info` / `repo-info` and `delete` / `repo-delete`.) *In the meantime*, you can try setting your extra Borg options with `--extra-borg-options.repo-list` on the command-line or `extra_borg_options` -> `repo_list` in configuration. That should work whenever `--archive` is omitted.

witten referenced this issue from a commit

2025-10-25 05:57:47 +00:00

Fix for the "list", "info", and "delete" options in "extra_borg_options" being ignored when "--archive" is omitted with Borg 1.x (#1168).

witten commented

2025-10-25 05:59:01 +00:00

Owner

Okay, this is fixed in main and will be part of the next release. At that point, you'll be able to use --extra-borg-options.list with Borg 1.x again even when --archive is omitted.

Thanks again!

Okay, this is fixed in main and will be part of the next release. At that point, you'll be able to use `--extra-borg-options.list` with Borg 1.x again even when `--archive` is omitted. Thanks again!

witten

2025-10-25 05:59:01 +00:00