Your message dated Fri, 31 Aug 2007 21:11:49 +0200
with message-id <[EMAIL PROTECTED]>
and subject line bug fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: wise
Version: 2.4.0-1
Severity: serious
Justification: no longer builds from source
>From
>http://buildd.debian.org/fetch.cgi?&pkg=wise&ver=2.4.0-1&arch=ia64&stamp=1185436921&file=log:
[snip]
cd docs && dvips wise2.dvi
This is dvips(k) 5.96.1 Copyright 2007 Radical Eye Software (www.radicaleye.com)
' TeX output 2007.07.26:0801' -> wise2.ps
</usr/share/texmf-texlive/dvips/base/tex.pro>
</usr/share/texmf-texlive/dvips/base/texps.pro>
</usr/share/texmf-texlive/dvips/base/special.pro>.
</usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmsy10.pfb>
</usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmtt10.pfb>
</usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmbx12.pfb>
</usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmti10.pfb>
</usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmbx10.pfb>
</usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmr10.pfb>
</usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmr12.pfb>
</usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmr17.pfb>[1] [2] [3] [4]
[5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20
<./genewise21.eps>] [21] [22] [23] [24<./genewise6.eps>] [25] [26] [27] [28]
[29] [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43]
[44]
cd docs && ps2pdf wise2.ps
/bin/sh: line 1: 8993 Bus error ps2pdf wise2.ps
make: *** [build-stamp] Error 135
[snip]
I'm guessing this is due to #428876.
--- End Message ---
--- Begin Message ---
Source: wise
Source-Version: 2.4.0-3
The last workaround for this bug seems to work. I therefore close this
bug.
--
Philipp Benner
--- End Message ---
