Your message dated Fri, 27 Jul 2012 20:38:01 +0100
with message-id 
<CANNm6Zw88iSyVsO2uYUt9iNMKZ-AwiwPUrO=nsywim3l4qt...@mail.gmail.com>
and subject line Re: rubber: Traceback is printed when compiling tex files that 
include package xparse with the '--warn all' flag
has caused the Debian Bug report #607081,
regarding rubber: Traceback is printed when compiling tex files that include 
package xparse with the '--warn all' flag
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 [email protected]
immediately.)


-- 
607081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607081
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rubber
Version: 1.1-2.4
Severity: normal


If I compile a .tex file that is using \usepackage{xparse}, rubber can
compile
it correctly:

$ rubber bla.tex
compiling bla.tex...
$ echo $?
0

However, if I provide it the '--warn all' argument, the following traceback
is
printed:

$ rubber --warn all bla.tex
compiling bla.tex...
Traceback (most recent call last):
  File "/usr/bin/rubber", line 9, in <module>
    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 282, in main
    refs=self.warn_refs, warnings=self.warn_misc))
  File "/usr/share/rubber/rubber/__init__.py", line 136, in display_all
    for msg in generator:
  File "/usr/share/rubber/rubber/rules/latex/__init__.py", line 416, in
parse
    last_file = self.update_file(line, pos, last_file)
  File "/usr/share/rubber/rubber/rules/latex/__init__.py", line 444, in
update_file
    last = stack[-1]
IndexError: list index out of range
$ echo $?
1

Without the xparse package:
$ rubber --warn all bla.tex
compiling bla.tex...
$ echo $?
0



And here is a sample file:
$ cat bla.tex
\documentclass{article}
\usepackage{xparse}
\begin{document}
Test
\end{document}
$


Best regards,
Pitxyoki


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages rubber depends on:
ii  python                  2.6.6-3+squeeze2 interactive high-level
object-orie
ii  python-support          1.0.10           automated rebuilding support
for P
ii  texlive-latex-base      2009-11          TeX Live: Basic LaTeX packages

rubber recommends no packages.

Versions of packages rubber suggests:
pn  imagemagick                   <none>     (no description available)
pn  sam2p                         <none>     (no description available)
pn  transfig                      <none>     (no description available)

-- no debconf information

--- End Message ---
--- Begin Message ---
Package: rubber
Version: 1.1-2.4

Hello Hillmar,

You are right. I can't reproduce the problem anymore, not even with
the mentioned version, which is now only in stable.
I'm closing this now. thanks for reminding me of this bug.


Best regards,
Pitxyoki

On 27/07/2012, Hilmar Preusse <[email protected]> wrote:
> On 14.12.10 Luís Picciochi Oliveira ([email protected]) wrote:
>
> Hi,
>
>
> http://bugs.debian.org/607081
>
>> If I compile a .tex file that is using \usepackage{xparse}, rubber can
>> compile
>> it correctly:
>>
>> $ rubber bla.tex
>> compiling bla.tex...
>> $ echo $?
>> 0
>>
>> However, if I provide it the '--warn all' argument, the following
>> traceback is printed:
>>
> I couldn't reproduce this using the latest rubber snapshot I've
> uploaded to unstable. Interestingly I couldn't reproduce it either
> when using the version you've reported the bug for.
>
> How to proceed? Do you still see the problem?
>
> Hilmar
> --
> sigfault
>

--- End Message ---

Reply via email to