Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Megatog615 on June 14, 2007, 04:37:21 pm
-
Title says it all.
-
cvs [version aborted]: unrecognized auth response from warpcore.org: cvs pserver: cannot open /home/fs2source/cvsroot/CVSROOT/config: Permission denied
Error, CVS operation failed
It takes less than five seconds to copy and paste the actual error. Please, show a little courtesy next time.
-
cvs [update aborted]: unrecognized auth response from warpcore.org: cvs pserver: cannot open /home/fs2source/cvsroot/CVSROOT/config: Permission denied
-
Hi there !
The last CVS version give me a "segmentation fault" after I accept a mission (after the briefing) and I lost my cursor (under Linux).
So I checked several times the CVS and I got the same message as above :)
Do you think we could change checkout path or module ?
Or do we have only to wait until it's repaired :)
Btw thanks a lot for your great job :)
-
Hello and :welcome:, Kervala
Hi there !
The last CVS version give me a "segmentation fault" after I accept a mission (after the briefing) and I lost my cursor (under Linux).
I get this SEGFAULT, too...
So I checked several times the CVS and I got the same message as above :)
Same here!
I'm checking out CVS every day ;)
Do you think we could change checkout path or module ?
I don't think so...
Or do we have only to wait until it's repaired :)
I think that this is the right choice...
Does someone know, what's up with CVS?
Btw thanks a lot for your great job :)
And a BIG THX from me, too ;)
-
Thanks a lot for the welcome :)
-
Try using the fs2_open_3_6_9 branch.
-
*Curses Fedora*.
It's fixed, *again*. Sorry.
-
*Curses Fedora*.
SELinux? That was my theory before, but it's never been confirmed. I was just curious. :)
It's fixed, *again*. Sorry.
Not a problem, and thanks for getting it all worked out. :D
-
*Curses Fedora*.
SELinux? That was my theory before, but it's never been confirmed. I was just curious. :)
Yes, SELinux. Every time an upgrade happens it completely resets the SELinux permissions.
We thought we had found a fix for that and forgot to make the fix permanent.
It shouldn't happen again, but I don't trust SELinux.