Re: Copy/migrate archives/history with a new key?

[Graham Percival <gperciva@tarsnap.com>]

On 2025-08-30, creed-january-twig@duck.com wrote:
> Setting UTF-8 LANG in crontab fixed it.
> 
> By the way, in my cron/tarsnap setup archives, tarsnap just did octal encoding,
> but I suspect tarsnap-gui had double-encoded the file names.
> 
> I can send the encoded and UTF-8 file names if you need them for debugging.

Thanks for the offer, but not necessary.  While looking into this, I
found libarchive's discussion about this:
https://github.com/libarchive/libarchive/wiki/Filenames
https://github.com/libarchive/libarchive/issues/587
(still open)

Lots of info in there for me to consider.


By the way, did you receive a:
    Pathname in pax header can't be converted to current locale
error message?  We should always be generating that message, as per
https://www.tarsnap.com/faq.html#locale-problems

Granted, finding stderr from cron jobs can be awkward.

Cheers,
- Graham