You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently adopted snazzer for keeping my btrfs snapshots.
Since I had several older snapshots that i created by hand, I wanted to import them into the snazzer .snapshotz directory.
These snaphots of course contain neither the .snapshotz directory nor .snapshot_measurements.exclude.
In principle, I could go through all the snapshots and add an empty .exclude file, but
That would be a bit of a hassle because they are read-only snaps
I'd rather not touch these, especially because they are already synced to other machines
Snazzer should be able to deal with a non-existent .exclude file (perhaps by replacing it with an empty dummy file...)
Alternatively, it would be nice to have a command snazzer import to properly import a manual snapshot.
The text was updated successfully, but these errors were encountered:
Thanks @Rollingthunder, snazzer really needs some TLC and I intend to give it some soon :)
Appreciate the report. The measurements feature needs a rewrite, I need to have it just PGP sign a shasum rather than duplicate the work of signing the entire snapshot contents, etc.
I recently adopted snazzer for keeping my btrfs snapshots.
Since I had several older snapshots that i created by hand, I wanted to import them into the snazzer
.snapshotz
directory.These snaphots of course contain neither the
.snapshotz
directory nor.snapshot_measurements.exclude
.In principle, I could go through all the snapshots and add an empty .exclude file, but
Snazzer should be able to deal with a non-existent .exclude file (perhaps by replacing it with an empty dummy file...)
Alternatively, it would be nice to have a command
snazzer import
to properly import a manual snapshot.The text was updated successfully, but these errors were encountered: