I have searched the forum for my issue and found nothing related or helpful.
I have checked the Resources category;
I have reviewed the Wiki for relevant information
I have read the the Release Notes and Errata
OpenMandriva Lx version:
Rock 6.0
Desktop
KDE
Running OM from an external 1TB Samsung drive on an ASUS ROG notebook & a NUC. No on either platform.
Description of the issue (screenshots if relevant):
Harrison Mixbus, a DAW available for Linux, installs w/o issue on Manjaro, Debian & Duvuan but will not install on OM. The .run file executes properly but fails when it tries to extract files. This happens w/both version 10 & 11.
Relevant informations (hardware involved, software version, logs or output…):
Files are freely available from Harrison Audio website & can be tested w/o consequences as the software is available as a demo. Link provided upon request.
We will need the error output. If you are running it in a terminal, that should do. It’s probably hard wired for mainstream distro installs and uses their package names to provide dependencies. We can make an effort to help you with it, but we may have limited options if they don’t offer any source code or advanced options in their installer.
Verifying archive integrity . . . 100% MD5 checksums are OK. All good.
Uncompressing Mixbus 100% . . . Extraction failed.
Signal caught, cleaning up
Press return to close this window.
I can reach out to Harrison tech support to see what they’ll share, but I’m not optimistic.
That is probably because we use bsdtar by default not gnutar. @bero or someone else more seasoned than myself will probably be able to help you work around that.
Follow up:
Just checked & the 3 other distros I was able to install to, Manjaro, Devuan & LMDE all typically use gnutar.
Could be the whole issue right there.
Maybe try creating a temporary alias for the purposes of the script. You can install gnutar with sudo dnf in gnutar in a terminal. I have a partial internet outage or I would point you in the right direction.
I rarely use file compression of any sort these days so I can be completely tar-agnostic. I’m considering swapping out one for the other to see what happens.
You will probably remove other things it depends on. If you don’t want to search for how to make a temporary alias for a terminal session to just run the installer, then you can use update-alternatives and change it that way.
Do you suppose both apps could co-exist? I wonder if the installation routine could find what it needs if it were just installed beside the other one. Thoughts?
There’s some ways to do it that are better than update-alternatives (which is a pain to use and affects the entire system instead of just the current user) – e.g. you can mkdir ~/gtar ; ln -s /usr/bin/gtar ~/gtar/tar and then adjust PATH to have ~/gtar ahead of /usr/bin (e.g. export PATH=~/gtar:$PATH)
Bero’s advice might be better. It’s how we deal with the same limitation of Steam. They use an option that is only used in gnutar and not bsdtar instead of using other means to handle that option. There are philosophical reasons not to do what they are doing with gnutar but they probably just want to do something that all of the well known distros will be able to work with.
Sending their support people a message about it might help clarify that we are moving in the correct direction, and that they simplify their tar call so it doesn’t need fancy things.
