Your message dated Tue, 26 Jul 2011 21:28:28 +0200
with message-id <20110726192828.ga17...@x61.home>
and subject line Bugs have been fixed in syncevolution 1.1.994+ds1-1
has caused the Debian Bug report #615263,
regarding syncevolution: FTBFS: libsmltk.so.0: could not read symbols: Invalid
operation
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.)
--
615263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: syncevolution
Version: 1.1+ds1-5
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110313 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> /usr/bin/ld: note: 'smlStartMessageExt@@VER_1.0' is defined in DSO
> //usr/lib64/libsmltk.so.0 so try adding it to the linker command line
> //usr/lib64/libsmltk.so.0: could not read symbols: Invalid operation
> collect2: ld returned 1 exit status
The full build log is available from:
http://people.debian.org/~lucas/logs/2011/03/13/syncevolution_1.1+ds1-5_lsid64.buildlog
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
Hi,
your bugs have been fixed in syncevolution 1.1.99.4+ds1-1, please see
the changelog:
http://packages.debian.org/changelogs/pool/main/s/syncevolution/current/changelog
Regards,
Tino
--- End Message ---
