Your message dated Tue, 21 Apr 2009 15:34:00 +0100
with message-id <20090421143400.gb8...@enricozini.org>
and subject line Re: Bug#523204: dballe: FTBFS: dvips: ! Couldn't find header 
file cm-super-t1.enc.
has caused the Debian Bug report #523204,
regarding dballe: FTBFS: dvips: ! Couldn't find header file cm-super-t1.enc.
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.)


-- 
523204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dballe
Version: 4.0.2-1
Severity: serious

Hi,

Your package is failing to build with the following error:
Chapter 4.
(./troubleshooting.tex) (./guide.bbl [21] [22]) [23] (./guide.aux)

LaTeX Warning: There were undefined references.

 )
(see the transcript file for additional information)
Output written on guide.dvi (23 pages, 36596 bytes).
Transcript written on guide.log.
TEXINPUTS="".":" dvips guide.dvi -o
This is dvips(k) 5.96.1 Copyright 2007 Radical Eye Software (www.radicaleye.com)
' TeX output 2009.04.06:2243' -> guide.ps
dvips: ! Couldn't find header file cm-super-t1.enc.
Note that an absolute path or a relative path with .. are denied in -R2 mode.
make[3]: *** [guide.ps] Error 1



Kurt




--- End Message ---
--- Begin Message ---
Version: 4.0.10-1

> Source: dballe
> Version: 4.0.2-1
> Severity: serious
> 
> Hi,
> 
> Your package is failing to build with the following error:
> Chapter 4.
[...]
> dvips: ! Couldn't find header file cm-super-t1.enc.
> Note that an absolute path or a relative path with .. are denied in -R2 mode.
> make[3]: *** [guide.ps] Error 1

The error did not make much sense to me, but before investigating it
further I tried to build a new upstream version that I had pending for
upload, and it did not have the bug. I'll then assume that this new
version closes the bug.

I've just (finally) uploaded 4.0.10-1, which apparently I forgot to
upload quite a bit of time ago, so this problem should be solved.


Ciao,

Enrico

-- 
GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini <enr...@debian.org>

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to