Your message dated Sun, 08 May 2011 17:32:23 -0300
with message-id <87k4e1vsq0.fsf@zancas.localnet>
and subject line "fixed"
has caused the Debian Bug report #626028,
regarding bliss: FTBFS: AMD64-specific .symbols
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.)
--
626028: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bliss
Version: 0.71-1
Severity: serious
Justification: fails to build from source
Builds of bliss are failing on nearly all architectures because
debian/libbliss1d.symbols wound up listing as mandatory some symbols
that g++ defines only on AMD64 (including kfreebsd-amd64). Could you
please adjust the packaging to compensate for the variation in
actually defined symbols across architectures? dpkg-gensymbols(1)
mentions a few possible approaches.
Thanks!
--- End Message ---
--- Begin Message ---
Package: bliss
Version: 0.71-2
Until the upstream api stabilizes and/or bliss acquires some rdeps, the
symbols file seems more trouble than it is worth.
d
--- End Message ---
