Package: rubber
Version: 1.1-2
Severity: minor
Hello.
When TeX detects that no output is generated, it does not create or
overwrite the dvi file. This situation can happen because I use a main
file and different \include secondary files, while a background job
runs rubber each second.
If the old dvi file exists, it stays older than the latex file, and
rubber compiles eternally. It does not really hurt.
If no dvi file is present, rubber crashes displaying
--
rubber colles_spe
compiling colles_spe.tex...
Traceback (most recent call last):
File "/usr/bin/rubber", line 9, in ?
sys.exit(Main()(sys.argv[1:]))
File "/usr/share/rubber/rubber/cmdline.py", line 296, in __call__
return self.main(cmdline)
File "/usr/share/rubber/rubber/cmdline.py", line 260, in main
ret = env.final.make(self.force)
File "/usr/share/rubber/rubber/__init__.py", line 237, in make
ret = self.run()
File "/usr/share/rubber/rubber/rules/latex/__init__.py", line 1224, in run
while self.recompile_needed():
File "/usr/share/rubber/rubber/rules/latex/__init__.py", line 1270, in
recompile_needed
if self.deps_modified(getmtime(self.prods[0])):
File "/usr/lib/python2.4/posixpath.py", line 143, in getmtime
return os.stat(filename).st_mtime
OSError: [Errno 2] No such file or directory: 'colles_spe.dvi'
--
and interrupting the process.
Rubber may handle the absence of an output dvi file as a successful
situation (unless latex reports error, that is).
Alternatively, both problems would be solved if rubber could read the
line containing
--
No pages of output.
--
in latex standard output or log file.
Bye.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17-2-k7
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Versions of packages rubber depends on:
ii python 2.4.3-11 An interactive high-level object-o
ii tetex-bin 3.0-19 The teTeX programs
rubber recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
