Refresh Rescuezilla lagging Clonezilla interoperability (Last updated in Rescuezilla v2.2 / 2021-06-04)

[shasheene]

Rescuezilla and Clonezilla are both actively developed projects.

The last time I systematically ensured images created by Rescuezilla and Clonezilla are fully-interoperable was way back in Rescuezilla v2.2 (released in June 2021), when the latest release was Clonezilla v2.7.2.

Rescuezilla v2.4 hasn't changed the way backups images are created, so images created with Rescuezilla should still be restorable with Clonezilla (in the same way Clonezilla can restore images create by older Clonezilla releases).

But in the past 14 months, Clonezilla has had a major release, and is now at version 3.0.1-8.

This is almost certainly introducing problems for existing users of modern Clonezilla evaluating Rescuezilla for its interoperability, but hitting problems because Rescuezilla v2.4 doesn't understand changes introduced in more recent versions of Clonezilla.

I have seen #360, #365 on GitHub, but also other internet forum threads claiming issues with Rescuezilla's ability to process Clonezilla images.

The task is to:

1. Ensure Rescuezilla restores images created by modern Clonezilla
2. Ensure Rescuezilla creates images in the same way as modern Clonezilla
   • Rescuezilla unofficially follows semantic versioning
   • If modern Clonezilla images aren't backwards compatible, the changes may cause Rescuezilla to follow Clonezilla and bump the major version to v3.0

There are a bunch of other related tasks around automation (including adding a command-line interface) that will lower the burden of maintaining Rescuezilla that will need to be completed first.

[Iceman248]

For clarification on #365; if I recall correctly and I think I do, this restore error (although it worked) happened using a Rescuezilla created image. Reading this made it sound like it would only happen with Clonezilla, but I can't for certainty if I am recalling this correctly. I was doing too much image testing.