Jonas Smedegaard wrote:
> But I would say it was best to regenerate documentation anyway. Should
> I file a separate bug about that?
FWIW, I tried fixing this. The fix is simple: dependency on rubber,
texlive-latex-extra, latex2html and three lines in debian/rules.
However, I bumped into #364420
Tzafrir Cohen wrote:
> On Tue, Jun 02, 2009 at 11:12:11AM +0200, Jonas Smedegaard wrote:
>
>> I noticed that configure checks for, and in a clean build chroot fails
>> to find, the commands "rubber" and "kpsewhich".
>
> However in the released tarballs (which includes betas and RCs) the
> generat
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Wed, Jun 17, 2009 at 12:07:20AM +0300, Tzafrir Cohen wrote:
>On Tue, Jun 02, 2009 at 11:12:11AM +0200, Jonas Smedegaard wrote:
>
>> I noticed that configure checks for, and in a clean build chroot
>> fails to find, the commands "rubber" and "k
On Tue, Jun 02, 2009 at 11:12:11AM +0200, Jonas Smedegaard wrote:
> I noticed that configure checks for, and in a clean build chroot fails
> to find, the commands "rubber" and "kpsewhich".
However in the released tarballs (which includes betas and RCs) the
generated HTML and PDF documentation are
Package: asterisk
Version: 1:1.6.1.0~dfsg-1
Severity: minor
Hi,
I noticed that configure checks for, and in a clean build chroot fails
to find, the commands "rubber" and "kpsewhich".
Both commands are related to LaTeX, so I suspect adding build-dependency
on "rubber" and texlive-base-bin (which
5 matches
Mail list logo
