bin/52448: MKBSDTAR=yes

[coypu%sdf.org@localhost]

>Number:         52448
>Category:       bin
>Synopsis:       MKBSDTAR=yes
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    bin-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 01 00:05:00 +0000 2017
>Originator:     coypu
>Release:        NetBSD 8.99.1
>Organization:
>Environment:
NetBSD loggy 8.99.1 NetBSD 8.99.1 (GENERIC) #82: Thu Jun 22 15:45:33 IDT 2017  fly@loggy:/home/fly/obj/sys/arch/amd64/compile/GENERIC amd64

>Description:
octave-forge failed to work:

octave:1> pkg install -forge signal
bundles of packages are not allowed
error: called from
    install at line 146 column 5
    pkg at line 394 column 9

Fetches:
https://sourceforge.net/projects/octave/files/Octave%20Forge%20Packages/Individual%20Package%20Releases/signal-1.3.2.tar.gz/download?use_mirror=netix&download=

unpacking with netbsd tar:
tar: File extended headers posix ustar archive. Extracting as plain files. Following files might be in the wrong directory or have wrong attributes.

directory contains PaxHeaders.4544 a subdirectory with contents.

package fails octave's sanity checks:

        if (length (dirlist) > 3)
          error ("bundles of packages are not allowed");
        endif

adding bsdtar (from pkgsrc) ahead of netbsd tar in PATH worked.

this looks obvious now, but octave doesn't provide any more output even in verbose mode, the line numbers it mentions are wrong, and it doesn't save temporaries.

why ship a broken tar when we have a working one in base?
>How-To-Repeat:

>Fix: