Bug#682892: Patch

2012-08-10 Thread Benj. Mako Hill
>> > > Yes, there could be, like dvipdfm.py, dvips.py, vtex.py, > > > mpost.py. But there shouldn't be many. I'd wait for the next > > > FTBFS bugs rolling in and then fix it. > > > > Please upload now to fix these two bugs. rubber will currently not > > work at all, in a very difficult to diag

Bug#682892: Patch

2012-08-10 Thread Hilmar Preusse
On 09.08.12 Benj. Mako Hill (m...@atdot.cc) wrote: > Hi, > > Yes, there could be, like dvipdfm.py, dvips.py, vtex.py, > > mpost.py. But there shouldn't be many. I'd wait for the next > > FTBFS bugs rolling in and then fix it. > > Please upload now to fix these two bugs. rubber will currently

Bug#682892: Patch

2012-08-09 Thread Benj. Mako Hill
> Yes, there could be, like dvipdfm.py, dvips.py, vtex.py, mpost.py. > But there shouldn't be many. I'd wait for the next FTBFS bugs > rolling in and then fix it. Please upload now to fix these two bugs. rubber will currently not work at all, in a very difficult to diagnose way, for any document

Bug#682892: Patch

2012-08-09 Thread Hilmar Preusse
On 08.08.12 Benj. Mako Hill (m...@atdot.cc) wrote: Hi, Many thanks for the patch! > There may be other places in the rubbery source code affected by this > bug. It's not clear to me how I would search for these > systematically. :-/ > Yes, there could be, like dvipdfm.py, dvips.py, vtex.py, mpo

Bug#682892: Patch

2012-08-08 Thread Benj. Mako Hill
Control: tags 682892 + patch So, the problem with this bug does have to do with the same issue in #684228 (namely, the move to paranoid mode through the "openout_any = p" configuration). As I said in #684228, I'm not an expert with this. But the attached patch seems to fix the issue on my systems