cannot restore

[alexheretic]

cannot restore

[alexheretic]

The filename is used to indicate the partclone binary name & decompression used in restoring.

{name}-{timestamp}.apt.{partclone_variant}.{z_name}

So the bits after apt shouldn't be changed.

If clones images have been renamed, they can be renamed back again to fix them.

You could also manually decompress & use partclone directly to restore.

[sharicov]

Thanks Alex, is it possible to create a mechanism for descriptions (like separate file)?

…

On Wed, Oct 21, 2020, 11:11 AM Alex Butler ***@***.***> wrote: The filename is used to indicate the partclone binary name & decompression used in restoring. {name}-{timestamp}.apt.{partclone_variant}.{z_name} So the bits after apt shouldn't be changed. If clones images have been renamed, they can be renamed back again to fix them. You could also manually decompress & use partclone directly to restore. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAOYCOT4IRBKSF5NJ4GGSH3SL2JULANCNFSM4SZK3JDQ> .

[alexheretic]

I suppose if you wanted to keep the renames you could keep symbolic links to those renamed files that had correct naming.

[sharicov]

thanks, seems too complicated for daily use.

…

On Wed, Oct 21, 2020, 11:50 AM Alex Butler ***@***.***> wrote: I suppose if you wanted to keep the renames you could keep symbolic links to those renamed files that had correct naming. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAOYCOWXTYTYTVBNBGI47LDSL2OEPANCNFSM4SZK3JDQ> .

[alexheretic]

thanks, seems too complicated for daily use.

Yes I agree. But the simple solution is, not manually renaming the clones to begin with. Can you help me understand why this is necessary?

[sharicov]

sure, thanks for asking. when doing normal backup of windows 10 disk I need to backup efi boot partition, OS partition and recovery partition. since I cannot do it in one batch I am doing it one by one and renaming them accordingly, stating type, size and contents (for OS, like clean install, build 20H2, office and Nvidia drivers). Another concern of mine is that if I will restore it to an empty disk I need to know what partition size I should create before restoring. BTW I am enjoying your program very much! It is very clean and simple to use while fast and reliable, currently trying to integrate your great app into custom gparted live iso. Unfortunately it is not in repository, so need to figure out how to do it properly. Thanks a lot for you support and prompt responses!

…

On Wed, Oct 21, 2020, 2:24 PM Alex Butler ***@***.***> wrote: thanks, seems too complicated for daily use. Yes I agree. But the simple solution is, not manually renaming the clones to begin with. Can you help me understand why this is necessary? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAOYCOWAWC7SELPTN2LO3NTSL3AGLANCNFSM4SZK3JDQ> .

[alexheretic]

Thanks for the details. Maybe you could click "clone" for each and give it a name that way, rather than rerunning the clone.

Or if you do rename, change just the stuff before .apt.ntfs.zst, as long as the end of the filename is unchanged it should work fine.

Regarding the custom iso, there is rpm & deb prebuilt packages included with each release https://github.com/alexheretic/apart-gtk/releases/tag/v0.24 & it's also available in AUR.

[sharicov]

Thank you very much, still think storing description file would be a nice touch, however it is a lot of work to implement...
Regards deb file, I am aware, however ISO building is only working with repositories for some reason.
Would be great if your program would be included in Debian repository!