restic version:
- all modern ones,
- my current one: `restic 0.18.1-dev (compiled manually) compiled with go1.25.4 on linux/amd64
I am studying the source code of restic find and I have already created 3 PRs which address bugs in restic find:
#5310 Bugfix restic find: missing check for mtime --oldest/–newest
#5664 Bugfix: restic find --pack ‘tree-pack’: no output for tree packs
#5666 Bugfix: restic find --json --show-pack-id: suppress text output in JSON mode
I am particularly interested in users who are using the option --show-pack-id combined with any of the options --pack, --tree or --blob. How often are you using it, what is the use case in your environment?
I know it works fine when you are dealing with a single item, but I find the output of options --pack --show-pack-id difficult to read. The information is all there but in my opinion it should be in one place and not in two different sections of the output.
Here is an example:
Found blob aa6da76dc4b3bd8d8cd9d42c5ed6db2e9c3e43cecef7e7ee925a3accab96ad79
… in file /home/wplapper/restic/testdata/0/0/9/0
(tree 6409bed28d08898b849ecc4fdf338cdb0d67358619c99e6f6c3b402b1895baf8)
… in snapshot 774ebacd (2026-01-16 09:01:17)
Found blob bd15c2d9117aa305a0cf99c9cc30359b66ee454b00b897fb1a925c56025f4556
… in file /home/wplapper/restic/testdata/0/0/9/1
(tree 6409bed28d08898b849ecc4fdf338cdb0d67358619c99e6f6c3b402b1895baf8)
… in snapshot 774ebacd (2026-01-16 09:01:17)
… (shortened output)
Object belongs to pack 433d47eae0872558f648f6db0caf36fe703d153750b6a25d594047830dff513a
… Pack 433d47ea: <Blob (data) f534a7fe, offset 58401, length 1146, uncompressed length 16384>
Object belongs to pack 433d47eae0872558f648f6db0caf36fe703d153750b6a25d594047830dff513a
… Pack 433d47ea: <Blob (data) f5a35172, offset 48093, length 1146, uncompressed length 16384>
Could you agree to the following proposed changes?
- move the packID output together with the rest of first section
- integrate the packID into the JSON output, so the packID will always be available
Thanks for your feedback!