I have pyznap deployed on several Arch servers and every few months it stops producing snapshots and sending/pulling because (I think) the files (python? libraries?) it was installed against were updated and are now in newer version, so pyznap just throws an error and quits. Every time that happens, my systems go without snapshots for several weeks/months until by accident I notice the last snapshots are very old.
This is quite dangerous. How can this be prevented? Pehaps pyznap should be (is?) compiled into a flatpak so that everything it needs to work stays static?
I have pyznap deployed on several Arch servers and every few months it stops producing snapshots and sending/pulling because (I think) the files (python? libraries?) it was installed against were updated and are now in newer version, so pyznap just throws an error and quits. Every time that happens, my systems go without snapshots for several weeks/months until by accident I notice the last snapshots are very old.
This is quite dangerous. How can this be prevented? Pehaps pyznap should be (is?) compiled into a flatpak so that everything it needs to work stays static?