Invalid --keep-exclude-tags flag being passed to prune command #728

Closed
opened 2023-07-22 11:39:18 +00:00 by mstarzinger · 5 comments

What I'm trying to do and why

I have a configuration file with the keep_exclude_tags: True option and am trying to run the borgmatic prune command. This leads to Borgmatic passing the invalid command-line flag --keep-exclude-tags to Borg's borg prune command.

Steps to reproduce

Run borgmatic prune with a configuration file containing the keep_exclude_tags: True option.

Actual behavior

Borgmatic is passing the --keep-exclude-tags flag to Borg's prune command.

[XXX@XXX ~]$ borgmatic prune
XXXXXX: Error running actions for repository
Command 'borg prune --keep-exclude-tags True --keep-daily 7 --keep-weekly 4 --keep-monthly 6 ssh://XXXXXX/share/Backup/XXXXXX' returned non-zero exit status 2.
/home/XXX/.config/borgmatic/config.yaml: An error occurred

summary:
/home/XXX/.config/borgmatic/config.yaml: An error occurred
XXXXXX: Error running actions for repository
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: --keep-exclude-tags ssh://XXXXXX/share/Backup/XXXXXX
Command 'borg prune --keep-exclude-tags True --keep-daily 7 --keep-weekly 4 --keep-monthly 6 ssh://XXXXXX/share/Backup/XXXXXX' returned non-zero exit status 2.

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

Expected behavior

Borgmatic should not pass the --keep-exclude-tags flag to the prune command.

Other notes / implementation ideas

No response

borgmatic version

1.8.0

borgmatic installation method

No response

Borg version

borg 1.2.4

Python version

No response

Database version (if applicable)

No response

Operating system and version

No response

### What I'm trying to do and why I have a configuration file with the `keep_exclude_tags: True` option and am trying to run the `borgmatic prune` command. This leads to Borgmatic passing the invalid command-line flag `--keep-exclude-tags` to Borg's `borg prune` command. ### Steps to reproduce Run `borgmatic prune` with a configuration file containing the `keep_exclude_tags: True` option. ### Actual behavior Borgmatic is passing the `--keep-exclude-tags` flag to Borg's `prune` command. ``` [XXX@XXX ~]$ borgmatic prune XXXXXX: Error running actions for repository Command 'borg prune --keep-exclude-tags True --keep-daily 7 --keep-weekly 4 --keep-monthly 6 ssh://XXXXXX/share/Backup/XXXXXX' returned non-zero exit status 2. /home/XXX/.config/borgmatic/config.yaml: An error occurred summary: /home/XXX/.config/borgmatic/config.yaml: An error occurred XXXXXX: Error running actions for repository 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: --keep-exclude-tags ssh://XXXXXX/share/Backup/XXXXXX Command 'borg prune --keep-exclude-tags True --keep-daily 7 --keep-weekly 4 --keep-monthly 6 ssh://XXXXXX/share/Backup/XXXXXX' returned non-zero exit status 2. Need some help? https://torsion.org/borgmatic/#issues ``` ### Expected behavior Borgmatic should not pass the `--keep-exclude-tags` flag to the `prune` command. ### Other notes / implementation ideas _No response_ ### borgmatic version 1.8.0 ### borgmatic installation method _No response_ ### Borg version borg 1.2.4 ### Python version _No response_ ### Database version (if applicable) _No response_ ### Operating system and version _No response_
Owner

Thank you for taking the time to file this! This definitely looks like a regression introduced by 1.8.0, and I've repro'd it locally.

Thank you for taking the time to file this! This definitely looks like a regression introduced by 1.8.0, and I've repro'd it locally.
witten added the
bug
label 2023-07-22 17:15:35 +00:00
Owner

This is now fixed in main and will be part of the next release. Thanks again!

This is now fixed in main and will be part of the next release. Thanks again!
Author

Awesome! Thanks for the quick fix.

Awesome! Thanks for the quick fix.
Owner

Just released in borgmatic 1.8.1!

Just released in borgmatic 1.8.1!
Author

Thanks again! I can confirm that the issue is resolved with the Arch Linux distribution package of the Borgmatic 1.8.1 release.

Thanks again! I can confirm that the issue is resolved with the Arch Linux distribution package of the Borgmatic 1.8.1 release.
Sign in to join this conversation.
No Milestone
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#728
No description provided.