Your message dated Sat, 21 May 2011 21:30:53 +0200
with message-id <[email protected]>
has caused the report #627521,
regarding texlive-binaries: dvipdfm requires DVI file to end in .dvi, breaking
some usage
to be marked as having been forwarded to the upstream software
author(s) [email protected]
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
627521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627521
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Dear dvipdfmx developers,
is this the right contact for a bug report?
Henry House <[email protected]> wrote:
> The dvipdfm binary
Couldn't care less if it was only in dvipdfm. But actually it's a
symlink now, and dvipdfmx has the same bug:
> seems to require that the DVI file be named as
> *.dvi, as when passed a filename such as testdvi (an actually existing
> file in DVI format) or testdvi.tmp, it fails with the message
>
> ** ERROR ** Could not open specified DVI file: testdvi.dvi
> or
> ** ERROR ** Could not open specified DVI file: testdvi.tmp.dvi
I didn't test it with latest dvidfmx, texlive 2010 has dvipdfmx-20090708
> etc. I've rated this bug "important" because it may cause printing DVI files
> from Evince to fail with a cryptic error message in the GUI. While this
> clearly
> problem could be worked around within Evince by renaming temporary files to
> ensure a *.dvi extension, the real bug is in dvipdfm, which should accept the
> user's input as given, and not second-guess (at least not without checking for
> existance of the filename as literally given before altering it).
I agree with that. Do you see any chance altering that?
Regards, Frank
--
Frank Küster
Vorstand B90/Grüne OV Miltenberg und Umgebung
VCD Miltenberg, ADFC Aschaffenburg-Miltenberg
Debian Developer (TeXLive)
--- End Message ---
