Michael Schroeder

In this case archive_write_header() returns ARCHIVE_WARN, which is treated as error in rpm2archive. OTOH I don't think libarchive should mess with the file names, maybe it makes sense to set...

Oh, and the error handling in rpm2archive is completely broken...

Btw, it cannot handle UTF8 filenames as well, as it checks the current locale which is not initialized and thus 7 bit ascii...

I find it very surprising that bsdtar's output depends on the current locale, but that seems to be the case: ``` $ echo hello > micro_µ $ bsdtar -cf -...

It's not much work to not use libarchive for writing. The only two formats that can be used for archive writing are cpio and pax (all the others have too...

It just warns about the unknown attribute.

And this is about file names, I think "upstream rpm" treats those pretty much as binary as they are created by the build process and not part of the spec...

Why "legacy"? Does the current code reject non-utf8 file names?

That makes things a bit easier, so we just need to teach libarchive that it should accept utf8. I'll adapt the title of this issue ;-)

I'll open a pull request for this.