Skip to content

borg2: check does not support custom output formatting #9411

@tve

Description

@tve

Borg check doesn't seem to follow archive listing formats. I have the following format specs:

BORG_PRUNE_FORMAT='{hostname:10}{archive:>14} {time:%Y-%m-%d %H:%M:%S} {tags}'
BORG_RLIST_FORMAT='{hostname:10}{archive:>14} {time:%Y-%m-%d %H:%M:%S} {tags} {id}{NL}'

and borg repo-list prints what I expect:

tekke         daily-full 2026-02-22 17:01:01  25fb4049931884edfba23f31fb95eaf595987f2c521d3fe11207c818ac6ce38
tekke         daily-full 2026-02-22 17:01:01  2ca9d22f35cca98972a1cd12909a9e8482bb0883370632413307731521d9eb0

but borg check seems to ignore it:

Analyzing archive daily-full 2026-02-22 17:01:01.359832+00:00 2ca9d22f35cca98972a1cd12909a9e8482bb08833706324133077319521d9eb0 (1/2)
Analyzing archive daily-full 2026-02-23 17:01:00.158401+00:00 eb39b1094598ee3b05899d4bfbaf2a481c00c57b84133f7611d79e8ba9a5a024 (2/2)

Borg prune does the right thing (but adds quite some padding to the left, perhaps 'cause some other messages are longer?

Keeping archive (rule: within #1):           tekke         daily-full 2026-02-23 17:01:00               
Keeping archive (rule: within #2):           tekke         daily-full 2026-02-22 17:01:01               
Keeping archive (rule: within #3):           tekke         daily-full 2026-02-22 17:01:01               

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions