net-fs/coda/files/venus used to have a "checkconfig" function. It appears to have been taken out, but the call to it remains, so the script fails 100%.
Griffon26 told me he has the fixes.
I found a problem in the patch that I submitted. Apparently I diff'd against a wrong version. As a workaround, remove the line with checkconfig. (That's what the diff was supposed to have done anyway.) I'll fix the problem as soon as I am able to.
Heh...already did that...just wanted to let you know. :)
Thanks for the report. A fix should now be in cvs. Could you check if it works so I can close this bug?
I'm sorry...I can no longer test this as I have switched to linux26-headers and coda-client has a dependency on >=sys-kernel/linux-headers-2.4 (perhaps this should be a changed to virtual/os-headers?). I unpacked it and it looks right to me, but that doesn't mean anything. :| Can someone else test it, please?
if it unpacks and compiles theres a good chance its ok. Use emerge -O coda to emerge without dependancies. If that works please let griffon26 know here.
Comments to bug 58702 please.
Ok, I can confirm that "checkconfig" works now. But "/etc/init.d/venus stop" produces an error (" [??] "). Venus does exit, but this error is given nonetheless (so you have to zap it to restart it).
Doh! My bad! I accidentally merged 6.0.3. Standby for update.
No, I take it back. :| 6.0.6 exhibits the same behavior that I described in comment #8.
Well, after restarting it again, that quirk went away. Sorry...I'm really tired. :/ After several trials, it seems to work.
I'll mark this report resolved/fixed, ok? As far as the problem with 6.0.3 is concerned, if you're interested you can keep an eye on bug #26132 for the "venus won't stop" issue.
The init scripts were modified and the problem no longer occurs.