severity 343906 minor
stop
On 18.12.05 Braun Gabor (bra...@renyi.hu) wrote:
Hi,
> When rubber intends to post process a dvi file (e.g. with dvips of
> dvipdfm) then it should create a dvi file optimized for the post
> processor. This means that packages (hyperref, graphicx,
> grapphics, color etc.) should use the appropriate driver.
>
Let's test this again. You performed the test for dvips and dvipdfm.
dvips:
hille@sid:~/devel/rubber/bugs $ rubber -o dvips 343906.tex
compiling 343906.tex...
compiling 343906.tex...
hille@sid:~/devel/rubber/bugs $ grep '[Dd]river' 343906.log
Package graphics Info: Driver file: dvips.def on input line 94.
File: dvips.def 2014/10/14 v3.0j Driver-dependent file (DPC,SPQR)
Package color Info: Driver file: dvips.def on input line 142.
File: dvipsnam.def 2014/10/14 v3.0j Driver-dependent file (DPC,SPQR)
Package hyperref Message: Driver (default): hdvips.
File: hdvips.def 2012/11/06 v6.83m Hyperref driver for dvips
Looks OK, AFAICT.
dvipdfm:
hille@sid:~/devel/rubber/bugs $ rubber -o dvipdfm 343906.tex
compiling 343906.tex...
hille@sid:~/devel/rubber/bugs $ grep '[Dd]river' 343906.log
Package graphics Info: Driver file: dvips.def on input line 94.
File: dvips.def 2014/10/14 v3.0j Driver-dependent file (DPC,SPQR)
Package color Info: Driver file: dvips.def on input line 142.
File: dvipsnam.def 2014/10/14 v3.0j Driver-dependent file (DPC,SPQR)
Package hyperref Message: Driver (default): hdvips.
File: hdvips.def 2012/11/06 v6.83m Hyperref driver for dvips
NOK. Another try using dvipdfmx:
hille@sid:~/devel/rubber/bugs $ rubber -o dvipdfmx 343906.tex
compiling 343906.tex...
hille@sid:~/devel/rubber/bugs $ grep '[Dd]river' 343906.log
Package graphics Info: Driver file: dvips.def on input line 94.
File: dvips.def 2014/10/14 v3.0j Driver-dependent file (DPC,SPQR)
Package color Info: Driver file: dvips.def on input line 142.
File: dvipsnam.def 2014/10/14 v3.0j Driver-dependent file (DPC,SPQR)
Package hyperref Message: Driver (default): hdvips.
File: hdvips.def 2012/11/06 v6.83m Hyperref driver for dvips
Same.
Now hard code the driver in the source file:
hille@sid:~/devel/rubber/bugs $ rubber -o dvipdfm 343906.tex
compiling 343906.tex...
/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty: File
/`dvipdfm.def' not found.
/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty:95:
/Emergency stop.
/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty:95:
/leading text: ...ed{ver@\Gin@driver}{\input{\Gin@driver}}{}
AFAICT there is no driver in Debian any more for dvipdfm and
graphics. I hard coded dvipdfmx instead and it worked:
hille@sid:~/devel/rubber/bugs $ grep '[Dd]river' 343906.log
Package graphics Info: Driver file: dvipdfmx.def on input line 94.
File: dvipdfmx.def 2015/09/11 v4.06 LaTeX color/graphics driver for dvipdfmx (T
Package color Info: Driver file: dvipdfmx.def on input line 142.
File: dvipsnam.def 2014/10/14 v3.0j Driver-dependent file (DPC,SPQR)
Package hyperref Message: Driver: hdvipdfm.
File: hdvipdfm.def 2012/11/06 v6.83m Hyperref driver for dvipdfm
So, we have a work around. I'll show that issue to upstream, for now
I lower it to minor.
Hilmar
--
sigmentation fault
