Your message dated Sat, 11 Nov 2006 20:33:59 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381625: multisync0.90 - FTBFS: Ships i386 binaries
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: multisync0.90
Version: 0.90.18-1
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of multisync0.90_0.90.18-1 on debian-31 by sbuild/s390 85
[...]
> gcc -Wall -Werror -I. -O2 -o multisync0.90 main.o gui.o pair.o plugins.o 
> support.o interface.o callbacks.o  -pthread file-sync/.libs/libfile_sync.a 
> -L/usr/lib evolution2_sync/.libs/libevo2_sync.a 
> synce_sync/.libs/libsynce_sync.a /usr/lib/libgnomeui-2.so 
> /usr/lib/libtasn1.so /usr/lib/libjpeg.so /usr/lib/libbonoboui-2.so 
> /usr/lib/libgnome-keyring.so /usr/lib/libgnomecanvas-2.so 
> /usr/lib/libgnome-2.so /usr/lib/libesd.so /usr/lib/libaudiofile.so 
> /usr/lib/libart_lgpl_2.so /usr/lib/libgtk-x11-2.0.so 
> /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so 
> /usr/lib/libgdk_pixbuf-2.0.so /usr/lib/libpangocairo-1.0.so 
> /usr/lib/libpangoft2-1.0.so -lXext -lXinerama -lXi -lXrandr -lXcursor 
> -lXfixes /usr/lib/libpango-1.0.so /usr/lib/libcairo.so -lSM -lICE -lXrender 
> -lpng12 /usr/lib/libfreetype.so -lfontconfig -lX11 /usr/lib/libgnomevfs-2.so 
> /usr/lib/libgnutls.so /usr/lib/libgcrypt.so -lnsl /usr/lib/libgpg-error.so 
> /usr/lib/libavahi-glib.so /usr/lib/libavahi-client.so -ldbus-1 
> /usr/lib/libavahi-common.so -lresolv -lutil /usr/lib/libbonobo-2.so 
> /usr/lib/libgconf-2.so /usr/lib/libbonobo-activation.so 
> /usr/lib/libORBitCosNaming-2.so /usr/lib/libORBit-2.so /usr/lib/libpopt.so 
> /usr/lib/libosengine.so /usr/lib/libopensync.so /usr/lib/libgmodule-2.0.so 
> /usr/lib/libgobject-2.0.so /usr/lib/libgthread-2.0.so /usr/lib/libglib-2.0.so 
> /usr/lib/libsqlite3.so -lpthread /usr/lib/libxml2.so -ldl -lz -lm
> /usr/bin/ld: main.o: Relocations in generic ELF (EM: 3)
> /usr/bin/ld: main.o: Relocations in generic ELF (EM: 3)
> /usr/bin/ld: main.o: Relocations in generic ELF (EM: 3)
> /usr/bin/ld: main.o: Relocations in generic ELF (EM: 3)
> /usr/bin/ld: main.o: Relocations in generic ELF (EM: 3)
> /usr/bin/ld: main.o: Relocations in generic ELF (EM: 3)
> main.o: could not read symbols: File in wrong format
> collect2: ld returned 1 exit status
> make[3]: *** [multisync0.90] Error 1
> make[3]: Leaving directory `/build/buildd/multisync0.90-0.90.18/gui'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/build/buildd/multisync0.90-0.90.18/gui'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/buildd/multisync0.90-0.90.18/gui'
> make: *** [build-stamp] Error 2
> ******************************************************************************
> Build finished at 20060804-1835
> FAILED [dpkg-buildpackage died]


--- End Message ---
--- Begin Message ---
On Sun, Aug 06, 2006 at 01:15:49AM +0200, Bastian Blank wrote:
> There was an error while trying to autobuild your package:

No idea what caused this, but the latest revision seems to have built
fine on all arches, so closing this.  Please reopen with further
information if you think this bug hasn't been addressed yet.


thanks,

Michael

--- End Message ---

Reply via email to