Andreas Grosche <[EMAIL PROTECTED]> writes: > If you know what caused the "obsolescent base-64 headers" and related errors > shown above in this thread,
The thread doesn't contain enough info to tell. Generally those messages were caused by 'tar' thinking that a block was a header, even though it wasn't. This could have been caused by any number of bugs that have been fixed since then, particularly in parsing sparse-file data. It's possible that you have found a bug in tar 1.13.25 that still isn't fixed; but I think this unlikely, given that tar 1.15.1 works for you. _______________________________________________ Bug-tar mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-tar
