Re: hdup v2.0.3 bug

[On 24 Dec, @ 01:16, GT wrote in "[hdup-user] hdup v2.0.3 bug ..."]
> Hi,
> 
> it seems (at least in the new version 2.0.3) there is a problem
> when using bzip for compression: hdup restore fails with reason "gzip:
> stdin: not in gzip format".
> 
> Solution:
> In function hdup_archive: change the `if' statements to `if', `else
> if' and `else if' and put an `else' in front of the last
> `g_strdup_printf' (which otherwise would always set .gz extension).

Ok, thanks for the fix - will add that for 2.0.4 

> Secondly, hdup does not seem to include directory entries into the
> archive; and I can't find a setting to change that behaviour.

this is a correct observation :)

> Hence, when restoring, all directory information (permissions, owner
> etc.) are missing and default to the user calling hdup (probably
> root).

hmmm, yeah. This is another example of why gnu tar isn't all that
great. If you give tar a include list - which hdup2.x does - it will
use that list to create a tar file. There is only one caveat: if this
list has any directories in it, all files in those directories will be
backed up. This is one of the underlying reasons I had to pull 2.0.1.

I see no solution for this.. Partly this is because I never use hdup
to mass restore a system. I reinstall and then untar/restore some archives
and copy them over to the new directory.

> Third, great tool! Everything I expect from a backup program.
> Though I find the names for the incremental backups a little
> irritating (maybe full, update1, update2 would be more expressive -
> but hey).

hehe :-)) In hdup.c line 21, you can find the definitions - you should
be able to redefine them in what you want. Full - level1 - level2 is
even more standard, but than people are going to expect level3, and
more :-) And that's never going to happen :)

grtz Miek