pali

> Yes, it is certainly a bug for a module to depend on strings being downgraded. I fully agree. And if there is another buggy module, then that should be...

@rurban Do you have information about this problem?

It looks like that GNU tar and BSD tar supports `-o` parameter which should create ustar archive when combined together with `-c`.

Seems that GNU tar `-o` is not same as `--format=ustar`. GNU tar manpage about `-o` says: When creating, same as `--old-archive`. And for `--old-archive`: Same as `--format=v7`. `--format=v7` is documented...

That module is in Core since 5.10. But it does not mean you cannot install it also on previous version. Also it is needed only when creating new distribution release,...

What do you mean by a new responsibilities? It is already ExtUtils::MakeMaker who generates Makefile. And if that generated Makefile is wrong, i.e. cause that `make dist` creates a problematic...

Hi @haarg! > It's not clear to me why Devel::PPPort ended up with PAX headers That is because new version of GNU /usr/bin/tar switched to PAX format by default. >...

That is interesting. Maybe it is really because of something which ustar cannot store. In any case it is happening which means /usr/bin/tar is doing it and therefore Makefile should...

I would suggest too that upstream project https://github.com/exfat-utils/exfat-utils would not be a fork. It should be possible to do that repository transfer via github UI.

See https://metacpan.org/pod/PerlIO::encoding There is variable $PerlIO::encoding::fallback and by default WARN_ON_ERR bit is set. So yes, it is bug as you did not get warning.