Latest Ark of course, v 20.12.0.
It opens regular *tar.zst and *zstd files without any problems, it’s only software packages cause the above error.
The only discussion related to this problem I found so far is dated almost 1 year ago, and what’s interesting is that it was held by @oberon and one of KDE devs who used Arch where there was no such an issue.
Pamac gained the ability to install .pkg.tar.* packages by double clicking on them, via mime-types.
This seem to have changed how the .pkg.tar.zst files are being handled by all applications to see it as an ALPM package, instead of a regular compressed archive.
Maybe @guinux can shed some light on this?
Hi all, as a real dumb bum ‘old man’ trying to get my head around Linux, I cannot for the life of me see why there are so many ways programs are zipped up and each new one causes even more problems for people like me trying to install: portaudio-1_19.7.0-1-x86_64.pkg.tar.zst
Why is it so difficult to attach three lines giving the terminal commands required to install it?
Hi Jack, I renamed the package getting rid of the .PKG to portaudio-1_19.7.0-1-x86_64.tar.zst.
Tried unpacking it with: tar xvfz portaudio-1_19.7.0-1-x86_64.tar.zst but got this response:
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now.
Any other suggestions?
Hi Strit, I tried this pacman -Qi Ark | grep “Version”
error: package ‘Ark’ was not found was the the outcome, but it is installed. Also, portaudio is installed, but not showing in the applications tab. pacman -Qi portaudio | grep “Version”
Version : 1:19.7.0-1
Thanks NGr, I tried that and it worked thanks, it was already showing as installed from AUR, but not in my Applications tab, so cannot run it from there.
There are broader issues I am trying to resolve running speech in python and get about 50 lines of errors about Alsa, Jack and slaves, all of which unfortunately mean nothing to me!