Re: How do I deal with this file?

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

chflags doies the job, thanks.

It appears /usr/bin/tar has changed between 8.99.50 and 8.99.51:
----------
 8.99.50# /usr/bin/tar xzpvf TeXmacs-1.99.5-src.tar.gz
TeXmacs-1.99.5-src/misc/autotroll/autotroll.m4
tar: File extended headers posix ustar archive. Extracting as plain
files. Following files might be in the wrong directory or have wrong
attributes.
TeXmacs-1.99.5-src/misc/autotroll/autotroll.m4
tar: ustar vol 1, 7064 files, 64158720 bytes read, 0 bytes written in
1 secs (64158720 bytes/sec)
8.99.50# unlink TeXmacs-1.99.5-src/misc/autotroll/autotroll.m4

So in 8.99.50 /usr/bin/tar doesn't understand the extended headers. In
8.99.51 I get:

8.99.51# /usr/bin/tar xjvpf
/usr/pkgsrc/distfiles/TeXmacs-1.99.5-src.tar.gz
TeXmacs-1.99.5-src/misc/autotroll/autotroll.m4
x TeXmacs-1.99.5-src/misc/autotroll/autotroll.m4
8.99.51# ls -ol TeXmacs-1.99.5-src/misc/autotroll/autotroll.m4
-rw-r--r-- 1 xtest 17453 Apr 22  2015
TeXmacs-1.99.5-src/misc/autotroll/autotroll.m4
8.99.51# unlink TeXmacs-1.99.5-src/misc/autotroll/autotroll.m4
unlink: Operation not permitted
8.99.51# chflags nouchg  TeXmacs-1.99.5-src/misc/autotroll/autotroll.m4
8.99.51# unlink TeXmacs-1.99.5-src/misc/autotroll/autotroll.m4

so here the new /usr/bin/tar knows and restores them. In both
occasions /usr/bin/tar is a soft link to /bin/tar, the two /bin/tar
commands appear to be completely different:
8.99.50# ls -l /bin/tar
-r-xr-xr-x  3 root  wheel  166192 Jul  7 15:25 /bin/tar
8.99.50# ldd /bin/tar
/bin/tar:
        -lutil.7 => /lib/libutil.so.7
        -lc.12 => /lib/libc.so.12
8.99.50# /bin/tar --version
tar: unknown option -- version
usage: tar [-]{crtux}[-befhjklmopqvwzHJOPSXZ014578] [archive] [blocksize]
           [-C directory] [-T file] [-s replstr] [file ...]

....
8.99.51# ls -l /bin/tar
-r-xr-xr-x 1 root wheel 82272 Jul 28 17:51 /bin/tar
8.99.51# ldd /bin/tar
/bin/tar:
        -larchive.4 => /usr/lib/libarchive.so.4
        -lbz2.1 => /usr/lib/libbz2.so.1
        -lc.12 => /lib/libc.so.12
        -lcrypto.14 => /lib/libcrypto.so.14
        -lcrypt.1 => /lib/libcrypt.so.1
        -lexpat.2 => /usr/lib/libexpat.so.2
        -llzma.2 => /lib/liblzma.so.2
        -lpthread.1 => /usr/lib/libpthread.so.1
        -lz.1 => /lib/libz.so.1
8.99.51# /bin/tar --version
bsdtar 3.4.0 - libarchive 3.4.0 zlib/1.2.10 liblzma/5.2.4 bz2lib/1.0.8

Somehow in my own builds of -current I have:
.....
8.99.51# tar xpzvf
/home/sysbuild/release/amd64/binary/sets/base.tar.xz ./bin/tar
./bin/cpio
x ./bin/cpio
x ./bin/tar
8.99.51# ./bin/tar --version
bsdtar 3.4.0 - libarchive 3.4.0 zlib/1.2.10 liblzma/5.2.4 bz2lib/1.0.8

So the usual /bin/tar has been replaced with bsdtar, which apparently
is aware of the extended flags. The same from yesterdays' -current on
releng shows the usual /bin/tar.

I have no idea how this has happened, I certainly haven't done it deliberately.

So it is both the TeXmacs distribution contains these extended flags
of a single file *and* I have got bsdtar in place of the usual one.

On Tue, 30 Jul 2019 at 14:09, Joerg Sonnenberger <joerg%bec.de@localhost> wrote:
>
> On Tue, Jul 30, 2019 at 10:51:11AM +0100, Chavdar Ivanov wrote:
> > GNU tar reports the extended header and does not restore it by default - the
> > file can be unlinked:
> > ...
> > # gtar xjvpf a1.tar.bz2
> > autotroll1/
> > gtar: Ignoring unknown extended header keyword 'SCHILY.fflags'
> > autotroll1/autotroll.m4
> > gtar: autotroll1: time stamp 2019-07-30 11:17:46 is 1935.436904375 s
> > in the future
>
> As it says, GNU tar simply doesn't know what the keyword means and
> therefore skips it.
>
> Joerg



-- 
----