Re: ViewCVS problems

Christopher Faylor wrote: That and we're just plain mean. Wow. It's been a while. Don't get discouraged. Even the great ones go through a slump now and then. - EMM -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Doc

Re: ViewCVS problems

29 Jan 2003 23:41:56 +0100 >To: [EMAIL PROTECTED], [EMAIL PROTECTED] >Subject: RE: ViewCVS problems > >From: Elfyn McBratney [mailto:[EMAIL PROTECTED]] >> >> > Rolling back cygwin didn't help, but rolling back Python did! >> > (From 2.2.2-4 to 2.2.2-1) >>

RE: ViewCVS problems

Because rebase isn't part of setup yet. Larry Original Message: - From: Marcus Lindblom [EMAIL PROTECTED] Date: Wed, 29 Jan 2003 23:41:56 +0100 To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: RE: ViewCVS problems From: Elfyn McBratney [mailto:[EMAIL PROT

RE: ViewCVS problems

From: Elfyn McBratney [mailto:[EMAIL PROTECTED]] > > > Rolling back cygwin didn't help, but rolling back Python did! > > (From 2.2.2-4 to 2.2.2-1) > > That sounds like it's the culprit. If you rebase your python > dll's that > should fix-up. Did you read the release announcment? > >

Re: ViewCVS problems

> > That sounds like it's the culprit. If you rebase your python dll's > > that should fix-up. > > Marcus must rebase *all* DLLs not just the Python ones. > > Jason Again with my big foot :( Sorry! Regards, Elfyn McBratney [EMAIL PROTECTED] www.exposure.org.uk -- Unsubscribe info: http

Re: ViewCVS problems

On Wed, Jan 29, 2003 at 05:43:24PM -, Elfyn McBratney wrote: > > Rolling back cygwin didn't help, but rolling back Python did! (From > > 2.2.2-4 to 2.2.2-1) > > That sounds like it's the culprit. If you rebase your python dll's > that should fix-up. Marcus must rebase *all* DLLs not just the

Re: ViewCVS problems

> Rolling back cygwin didn't help, but rolling back Python did! > (From 2.2.2-4 to 2.2.2-1) That sounds like it's the culprit. If you rebase your python dll's that should fix-up. Did you read the release announcment? Regards,

RE: ViewCVS problems

> > Since it's thrown on os.fork(), I suspect cygwin is the culprit, but > > that's just my gut feeling. > > There have been some changes in the fork-semantics (?) AFAIKS > in the latest > snapshots. Also what heppens if you roll back to cygwin-1.3.18-1? I didn't know about the possibility of ro

Re: ViewCVS problems

> >> File "/usr/local/viewcvs-0.9.2/lib/popen.py", line 33, in popen > >> pid = os.fork() > >> OSError: [Errno 11] Resource temporarily unavailable > >> -- > >> > >> Since it's thrown on os.fork(), I suspect cygwin is the culprit, but > >> that's just my gut feeling. > > > >There have been so

Re: ViewCVS problems

Christopher Faylor writes: > > On Wed, Jan 29, 2003 at 04:59:43PM -, Elfyn McBratney wrote: > >> File "/usr/local/viewcvs-0.9.2/lib/popen.py", line 33, in popen > >> pid = os.fork() > >> OSError: [Errno 11] Resource temporarily unavailable > >> -- > >> > >> Since it's thrown on os.fork(),

Re: ViewCVS problems

On Wed, Jan 29, 2003 at 04:59:43PM -, Elfyn McBratney wrote: >> File "/usr/local/viewcvs-0.9.2/lib/popen.py", line 33, in popen >> pid = os.fork() >> OSError: [Errno 11] Resource temporarily unavailable >> -- >> >> Since it's thrown on os.fork(), I suspect cygwin is the culprit, but >> th

Re: ViewCVS problems

> File "/usr/local/viewcvs-0.9.2/lib/popen.py", line 33, in popen > pid = os.fork() > OSError: [Errno 11] Resource temporarily unavailable > -- > > Since it's thrown on os.fork(), I suspect cygwin is the culprit, but > that's just my gut feeling. There have been some changes in the fork-sema

ViewCVS problems

Hi! After a regular update session a few weeks ago, ViewCVS stopped working. I noticed this only later and thus do not know exactly what was changed. I've searched on the ViewCVS and Cygwin websites/maillists and Google about this and found nothing helpful. I also posted to the ViewCVS-mailling