Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 70340 - Viewing the changelog of portage in CVS gives serveral errors in viewcvs.py
Summary: Viewing the changelog of portage in CVS gives serveral errors in viewcvs.py
Status: RESOLVED FIXED
Alias: None
Product: Websites
Classification: Unclassified
Component: [OLD] Changelog (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Docs Team
URL: http://www.gentoo.org/cgi-bin/viewcvs...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-07 04:32 UTC by Christophe Garault
Modified: 2004-11-07 04:37 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christophe Garault 2004-11-07 04:32:57 UTC
Trying to look at the new portage version changelog, I followed this url (see above) and got an Python error I think you should look at.
Regards.
Christophe Garault

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Actual Results:  
Failure during use of an external program:
The command line was:

enscript --color --language=html --pretty-print=changelog -o - -

Please look at the error log of your webserver for more info.
An Exception Has Occurred
Python Traceback

Traceback (most recent call last):
  File "/var/www/localhost/viewcvs/lib/viewcvs.py", line 3044, in main
    run_viewcvs(server)
  File "/var/www/localhost/viewcvs/lib/viewcvs.py", line 3020, in run_viewcvs
    view_checkout(request)
  File "/var/www/localhost/viewcvs/lib/viewcvs.py", line 2175, in view_checkout
    markup_stream(request, fp, revision, request.mime_type)
  File "/var/www/localhost/viewcvs/lib/viewcvs.py", line 864, in markup_stream
    markup_stream_enscript(lang, fp)
  File "/var/www/localhost/viewcvs/lib/viewcvs.py", line 655, in
markup_stream_enscript
    enscript.write(chunk)
IOError: [Errno 32] Broken pipe
Comment 1 Christophe Garault 2004-11-07 04:37:42 UTC
Wow! Never seen a bug so quickly fixed! I've been trying several time to access the page (in order to be sure it was a bug) and just a few seconds after posting the new bug, it's been solved! Congrats guys... ;-)