Your message dated Tue, 27 Nov 2012 10:48:25 +0100
with message-id <20121127094825.ga27...@preusse-16223.user.cis.dfn.de>
and subject line Re: Bug#484786: rubber: LaTeX beamer requires two compilatons
to regenerate TOC
has caused the Debian Bug report #484786,
regarding rubber: LaTeX beamer requires two compilatons to regenerate TOC
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(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 ow...@bugs.debian.org
immediately.)
--
484786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rubber
Version: 1.1-2.1
Severity: normal
In order to have an updated table of contents in a LaTeX beamer document,
rubber must be run twice.
As rubber detects that the main .tex file has not been modified between
compilation, I also have to 'touch' the .tex file in order to make rubber
compile for the second time.
Thanks a lot,
Lluis
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (250, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to ca_ES.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages rubber depends on:
ii python 2.5.2-1 An interactive high-level object-o
ii tetex-bin 2007-14 TeX Live: teTeX transitional packa
ii texlive-latex-base 2007-14 TeX Live: Basic LaTeX packages
rubber recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On 26.11.12 Lluís (xscr...@gmx.net) wrote:
Hi,
> Sorry, I forgot which document was giving me problems, and I'm unable to
> reproduce the problem now.
>
> I suppose this can be closed.
>
Doing so.
Hilmar
--
sigmentation fault
--- End Message ---
