[Flightgear-devel] CVS log browser broken
The result of trying to view viewmgr.cxx (web page http://cvs.flightgear.org/cgi-bin/viewcvs/viewcvs.cgi/FlightGear/src/Main/viewmgr.cxx?rev=1.18cvsroot=FlightGear-0.7content-type=text/vnd.viewcvs-markup) is the following error: Failure during use of an external program: enscript --color -W html -Ecpp -o - - Python Exception Occurred Traceback (most recent call last): File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 2620, in run_cgi main() File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 2586, in main view_checkout(request) File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 1914, in view_checkout markup_stream(request, fp, revision, request.mime_type) File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 662, in markup_stream markup_stream_enscript(lang, fp) File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 493, in markup_stream_enscript enscript.write(chunk) IOError: [Errno 32] Broken pipe - Julian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CVS log browser broken
It looks like enscript is breaking on viewmgr.cxx It also looks like the behavior of enscript doesn't conform well to it's man page. :-( Does this happen with any other source files or is it just viewmgr.cxx? I don't see anything in viewmgr.cxx that looks particularly different from any other source code file. Curt. [EMAIL PROTECTED] writes: The result of trying to view viewmgr.cxx (web page http://cvs.flightgear.org/cgi-bin/viewcvs/viewcvs.cgi/FlightGear/src/Main/viewmgr.cxx?rev=1.18cvsroot=FlightGear-0.7content-type=text/vnd.viewcvs-markup) is the following error: Failure during use of an external program: enscript --color -W html -Ecpp -o - - Python Exception Occurred Traceback (most recent call last): File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 2620, in run_cgi main() File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 2586, in main view_checkout(request) File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 1914, in view_checkout markup_stream(request, fp, revision, request.mime_type) File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 662, in markup_stream markup_stream_enscript(lang, fp) File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 493, in markup_stream_enscript enscript.write(chunk) IOError: [Errno 32] Broken pipe -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CVS log browser broken
Curtis L. Olson wrote: It looks like enscript is breaking on viewmgr.cxx Is it enscript that is breaking, or the other end of its pipe? The error message says Broken pipe in enscript.write(chunk). Maybe just that the disk is full? Does this happen with any other source files or is it just viewmgr.cxx? That was the only file I had tried. Just now I tried fg_commands.cxx and got the same, so it's probably every file. - Julian [EMAIL PROTECTED] writes: The result of trying to view viewmgr.cxx (web page http://cvs.flightgear.org/cgi-bin/viewcvs/viewcvs.cgi/FlightGear/src/Main/viewmgr.cxx?rev=1.18cvsroot=FlightGear-0.7content-type=text/vnd.viewcvs-markup) is the following error: Failure during use of an external program: enscript --color -W html -Ecpp -o - - Python Exception Occurred Traceback (most recent call last): File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 2620, in run_cgi main() File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 2586, in main view_checkout(request) File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 1914, in view_checkout markup_stream(request, fp, revision, request.mime_type) File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 662, in markup_stream markup_stream_enscript(lang, fp) File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 493, in markup_stream_enscript enscript.write(chunk) IOError: [Errno 32] Broken pipe ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CVS log browser broken
[EMAIL PROTECTED] writes: Is it enscript that is breaking, or the other end of its pipe? The error message says Broken pipe in enscript.write(chunk). Maybe just that the disk is full? By my reading of the error message, python is reporting that enscript died unexpectedly. There is plenty of disk space, and the view command seems to work fine on other files (unless you can point out other files that also don't work.) Does this happen with any other source files or is it just viewmgr.cxx? That was the only file I had tried. Just now I tried fg_commands.cxx and got the same, so it's probably every file. There are several files in there that work just fine though ... For now you could try (as text) rather than (view). I could run enscript manually on the file, but that doesn't necessarily mean anything. Viewcvs is pulling the requested version out of cvs and then feeding that to enscript, so something could be breaking down there as well. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CVS log browser broken
Curtis L. Olson wrote: [EMAIL PROTECTED] writes: Is it enscript that is breaking, or the other end of its pipe? The error message says Broken pipe in enscript.write(chunk). Maybe just that the disk is full? By my reading of the error message, python is reporting that enscript died unexpectedly. I agree, but I think that Broken pipe is the reason why enscript died, rather than just the result of it dying. What is it piping its output into? There is plenty of disk space, and the view command seems to work fine on other files OK, these display (but are not coloured - isn't enscript -color supposed to do syntax highlighting?): f*.hxx (5 files) README runfgfs.bat.in These fail: f*.cxx (5 files) Makefile.am 3dfx.sh ../FDM/JSBSim/FGAerodynamics.cpp ../FDM/JSBSim/FGAerodynamics.h Sometimes the error is different: there is no mention of enscript and it says: Python Exception Occurred Traceback (most recent call last): File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 2620, in run_cgi main() File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 2586, in main view_checkout(request) File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 1914, in view_checkout markup_stream(request, fp, revision, request.mime_type) File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 662, in markup_stream markup_stream_enscript(lang, fp) File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 501, in markup_stream_enscript enscript.close() File /usr/local/viewcvs-0.9.1/lib/popen.py, line 180, in close self.file.close() IOError: [Errno 32] Broken pipe For now you could try (as text) rather than (view). Yes. I don't need to use it at all actually; I was just having a quick look, so you needn't spend time on this problem for my sake. - Julian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CVS log browser broken
[EMAIL PROTECTED] writes: Curtis L. Olson wrote: [EMAIL PROTECTED] writes: Is it enscript that is breaking, or the other end of its pipe? The error message says Broken pipe in enscript.write(chunk). Maybe just that the disk is full? By my reading of the error message, python is reporting that enscript died unexpectedly. I agree, but I think that Broken pipe is the reason why enscript died, rather than just the result of it dying. What is it piping its output into? I'm not a python expert and do not claim to have any knowledge on the subject. But tcl will give very similar errors when a sub program dies. It builds a pipe to the IO of the other process and if it dies it reports a 'broken pipe.' So my best guess is still that enscript is dying, breaking the 'pipe' between it and the viewcvs python script. There is plenty of disk space, and the view command seems to work fine on other files OK, these display (but are not coloured - isn't enscript -color supposed to do syntax highlighting?): f*.hxx (5 files) README runfgfs.bat.in These fail: f*.cxx (5 files) Makefile.am 3dfx.sh ../FDM/JSBSim/FGAerodynamics.cpp ../FDM/JSBSim/FGAerodynamics.h Sometimes the error is different: there is no mention of enscript and it says: Python Exception Occurred Traceback (most recent call last): File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 2620, in run_cgi main() File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 2586, in main view_checkout(request) File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 1914, in view_checkout markup_stream(request, fp, revision, request.mime_type) File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 662, in markup_stream markup_stream_enscript(lang, fp) File /usr/local/viewcvs-0.9.1/lib/viewcvs.py, line 501, in markup_stream_enscript enscript.close() File /usr/local/viewcvs-0.9.1/lib/popen.py, line 180, in close self.file.close() IOError: [Errno 32] Broken pipe For now you could try (as text) rather than (view). Yes. I don't need to use it at all actually; I was just having a quick look, so you needn't spend time on this problem for my sake. Maybe for now I'll just hope the problem goes away when the next version comes out. I don't have a lot of time to deal with it myself right now either. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CVS log browser broken
Curtis L. Olson wrote: I'm not a python expert and do not claim to have any knowledge on the subject. But tcl will give very similar errors when a sub program dies. It builds a pipe to the IO of the other process and if it dies it reports a 'broken pipe.' So my best guess is still that enscript is dying, breaking the 'pipe' between it and the viewcvs python script. OK. I know almost nothing about it, so I expect you are right. Maybe for now I'll just hope the problem goes away when the next version comes out. No problem. - Julian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
