Not working on OSX about unrarall HOT 8 CLOSED

Hi,

I'm afraid I don't have a machine with OSX on to test unrarall. You are probably right when you say the problem is bash differences. I don't think you are invoking it correctly though.

$ sh unrarall -c -v

Will probably break because I believe /bin/sh is not proper bash. It might be bash emulating simplier "sh" behaviour. If you're running a bash shell you should invoke as

$ /path/to/script/unrallall -c -v

or to explicitly run it do

$ /bin/bash /path/to/script/unrarall -c -v

If that does not fix problems please tell us your bash version

$ /bin/bash --version

and in the script change the first line to

#!/bin/bash -x

Now when you run the script you will see every command executed. It's a little like debugging output. That will help us/you determine what's going wrong.

from unrarall.

I'm having the same problem and running bash version 3.2.48(1)-release (x86_64-apple-darwin12).

As I'm a beginner when it comes bash scripting, I was able to fix it but – I think – not in the right way.
The problem is the string 7z is being interpreted as a number. I changed it to sevenzip and replaced "7z" from all the script.

After that I had another problem regarding the "declare" statement.
-A is not a recognized option but -a (not capitalized) is.

Maybe that helps you guys...

from unrarall.

@leods92 . The use of "-A" rather than "-a" is deliberate. It is for associative arrays (as opposed to indexed arrays) which was introduced in Bash 4 I think.

@leods92 @peol I've created a new branch "old-bash-fix" ( https://github.com/arfoll/unrarall/tree/old-bash-fix ) that has some fixes in it that avoids the use associative arrays. Please try it. If it fixes your issues I'll merge the changes into master.

Thanks for trying out unrarall!

from unrarall.

Hi, sorry for the late response. I'll try it out and let you know :)

Thanks for taking the time to solve this!

from unrarall.

@delcypher The fixes in old-bash-fix seems to do the trick, worked like a charm. Thanks again for taking the time and fix this.

from unrarall.

@delcypher I've also tried and it worked perfectly.

I didn't know Apple was shipping such an old version of bash.
A little bit off-topic: do you know the reason for that? I mean, updating it would break many system features or they just don't care?

And thank YOU for letting us use unrarall as well as maintaining and supporting it.

from unrarall.

@leods92 bash4 moved to GPLv3 whilst bash3 is GPLv2. A lot of embedded vendors also dislike shipping bash4 because of this. I'd recommend keeping /bin/sh to use bash3 to make sure you don't break anything but then move to bash4 for /bin/bash. That way nothing should break and you can make sure scripts such as these use bash4 by using #!/bin/bash

@delcypher I'm really not bothered about bash3 compat, then again since we have OSX users maybe these should be merged...

from unrarall.

The changes have been merged (with a few tweaks) into master and the version has been bumped to 0.3

from unrarall.