[arch-general] libarchive - bsdtar producing weird archives?
The result of a makepkg run produced what looked like a totally garbled package, when viewed in mc's virtual file system. That led me to investigate a bit, so I tried packing up a few directories with bsdtar and sometimes got similarly garbled results. However, unpacking worked completely normally, as also did viewing the archives in xarchiver or squeeze. If I use tar instead of bsdtar to do the packing, they appear normally in mc. Does anyone know what's going on here? Is it mc that is getting something wrong, or bsdtar?
Michael Towers wrote:
The result of a makepkg run produced what looked like a totally garbled package, when viewed in mc's virtual file system. That led me to investigate a bit, so I tried packing up a few directories with bsdtar and sometimes got similarly garbled results. However, unpacking worked completely normally, as also did viewing the archives in xarchiver or squeeze. If I use tar instead of bsdtar to do the packing, they appear normally in mc.
Does anyone know what's going on here? Is it mc that is getting something wrong, or bsdtar?
I'd be attributing this to mc given you can extract the files fine and other packages veiw the archive fine. Allan
On Wed, 2009-05-27 at 13:55 +0200, Michael Towers wrote:
The result of a makepkg run produced what looked like a totally garbled package, when viewed in mc's virtual file system. That led me to investigate a bit, so I tried packing up a few directories with bsdtar and sometimes got similarly garbled results. However, unpacking worked completely normally, as also did viewing the archives in xarchiver or squeeze. If I use tar instead of bsdtar to do the packing, they appear normally in mc.
Does anyone know what's going on here? Is it mc that is getting something wrong, or bsdtar?
bsdtar adds some extended attributes to tar files. I think mc can't handle such things.
participants (3)
-
Allan McRae
-
Jan de Groot
-
Michael Towers