Last modified: 2008-01-20 05:26:32 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 12695 - texvc sends dvips output into the webserver error log
texvc sends dvips output into the webserver error log
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.11.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-19 20:30 UTC by CBM
Modified: 2008-01-20 05:26 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description CBM 2008-01-19 20:30:57 UTC
On systems where dvips generates output by default, the dvips output that comes from texvc will show up in apache error logs. For example, I checked my log, and it has things like this:

This is dvips(k) 5.96.1 Copyright 2007 Radical Eye Software (www.radicaleye.com)
' TeX output 2007.08.13:1013' -> 
</usr/share/texmf-texlive/dvips/base/tex.pro>
</usr/share/texmf-texlive/dvips/base/texps.pro>. 
</usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmsy10.pfb>[1]

Adding the -q option to dvips in the first line of render.ml should fix this.
Comment 1 Brion Vibber 2008-01-20 05:26:32 UTC
Done in r29964.

dvipng is used preferentially if it's present, and appears to give clean output. Added -q option to dvips when it is used.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links