Your message dated Wed, 13 Sep 2006 17:06:09 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in NMU of djvulibre 3.5.17-1.1
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: djvulibre
Version: 3.5.17-1
Severity: serious
FTBFS on alpha, compiling kviewshell/plugins/djvu/libdjvu/GString.cpp.
See #381717. Please compile this file using -O0 on alpha.
--- End Message ---
--- Begin Message ---
Version: 3.5.17-1.1
I've NMUed for this bug (fixing the bug to use versioning instead of the
"fixed" tag, to ease tracking through testing); here's the changelog:
> djvulibre (3.5.17-1.1) unstable; urgency=medium
> .
> * Non-maintainer upload.
> * On alpha, build GString.cpp with -O0 to work around a bug in GCC 4.1/4.2.
> Fixes FTBFS. (Closes: #386032)
/* Steinar */
--
Homepage: http://www.sesse.net/
--- End Message ---
