Re: bsdtar/libarchive change behaviour 9->10

2013-08-19 Thread Jeremie Le Hen
On Mon, Aug 19, 2013 at 01:52:33AM +0200, Eitan Adler wrote: > On Sun, Aug 18, 2013 at 9:39 PM, Tim Kientzle wrote: > > Libarchive 3.x can treat them as extended metadata. > > As a result, bsdtar doesn't see them at all (except as > > additional metadata which can't be restored on FreeBSD). This

Re: bsdtar/libarchive change behaviour 9->10

2013-08-18 Thread Eitan Adler
On Sun, Aug 18, 2013 at 9:39 PM, Tim Kientzle wrote: > Libarchive 3.x can treat them as extended metadata. > As a result, bsdtar doesn't see them at all (except as > additional metadata which can't be restored on FreeBSD). Are there other such examples? > If you are using libarchive directly, yo

Re: bsdtar/libarchive change behaviour 9->10

2013-08-18 Thread Tim Kientzle
On Aug 18, 2013, at 12:04 PM, Boris Samorodov wrote: > Hi All, > > there are two systems which produce different results: > - > % uname -a > FreeBSD int.wart.ru 9.2-BETA2 FreeBSD 9.2-BETA2 #19 r253968: Tue Aug 6 > 04:16:05 SAMT 2013 b...@int.wart.ru:/usr/obj/usr/src/sys/INT i386 > > %

bsdtar/libarchive change behaviour 9->10

2013-08-18 Thread Boris Samorodov
Hi All, there are two systems which produce different results: - % uname -a FreeBSD int.wart.ru 9.2-BETA2 FreeBSD 9.2-BETA2 #19 r253968: Tue Aug 6 04:16:05 SAMT 2013 b...@int.wart.ru:/usr/obj/usr/src/sys/INT i386 % tar --version bsdtar 2.8.5 - libarchive 2.8.5 % tar -tf /usr/ports/dist