Re: new reject msg from an arm64 buster install -- /usr/bin/tar executable?

On Tue, 3 Sep 2019 10:50:02 -0400
Nathan Stratton Treadway <[email protected]> wrote:

> > Which simply points amanda to tar:
> > 
> > root@jhegaala:~# which tar
> > /usr/bin/tar  
> 
> Where does this copy of tar come from?  ("dpkg -S /usr/bin/tar" would
> tell you if it's part of a Debian pacakge.)
>
> In my Debian Stretch installation, the "tar" package (version
> 1.29b-1.1 on the system I just checked) puts the executable
> at /bin/tar , and /usr/bin/tar does not exist.

Ack! A Bill the Cat moment! I'm contemplating spitting up a hairball.

If you do a completely new installation of debian 10 (buster), tar shows
up at /usr/bin/tar.

root@jhegaala:/media# which tar
/usr/bin/tar
root@jhegaala:/media# file $( which tar )
/usr/bin/tar: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=6664753ff93e3b42aa8681d7fe0f7f9e5259c54f, stripped
root@jhegaala:/media# 

But if you upgrade from debian 9 (stretch) to 10 (buster), tar show up
at /bin/tar, consistent with Nathan's observation on stretch, above.

root@hawk:~# which tar
/bin/tar
root@hawk:~#

dpkg -S and apt-file both place it at /bin/tar on both machines.

That, of course, makes it hard for Jose to simply drop a correct
version of amanda-security.conf into place. His code would have to edit
it during the installation.

-- 
"When we talk of civilization, we are too apt to limit the meaning of
the word to its mere embellishments, such as arts and sciences; but
the true distinction between it and barbarism is, that the one
presents a state of society under the protection of just and
well-administered law, and the other is left to the chance government
of brute force."
- The Rev. James White, Eighteen Christian Centuries, 1889
Key fingerprint = 38DD CE9F 9725 42DD E29A  EB11 7514 6D37 A332 10CB
https://charlescurley.com