Re: hdup2 and older tar versions

Earlier I described some tar warnings and errors I get on restore.

Miek Gieben wrote:
> what does plain tar say about those archives?

It turns out I get those errors even just creating and then extracting
an archive containing sparse files, without hdup involved:

# tar cf test.tar /var/lib/rpm --sparse
tar: Removing leading `/' from member names
# tar -xf test.tartar
tar: var/lib/rpm/__db.003: invalid sparse archive member
tar: Skipping to next header
tar: var/lib/rpm/Sigmd5: invalid sparse archive member
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers
 [etc]

My tar (which is the RPM version of 1.14 shipped with Fedora Core 3)
creates 'gnu' format archives by default.  Adding --format=posix makes
it run without errors.

The manual says that posix format "is the most flexible and feature-rich
format", and it "will be the default format for future versions of GNU
`tar'."  Perhaps hdup should always use this format.  For now I'll add
   tar option = --format=posix
to my hdup.conf and see how that works.

Bng
-- 
Boris Goldowsky <boris-FrUbXkNCsVf2fBVCVOL8/[email protected]>