Your message dated Fri, 27 Nov 2009 10:36:55 +0000
with message-id <[email protected]>
and subject line Re: Bug#558144 closed by Debian Archive Maintenance
<[email protected]> (Bug#558144: Removed package(s) from
unstable)
has caused the Debian Bug report #555382,
regarding FTBFS with binutils-gold
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 [email protected]
immediately.)
--
555382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555382
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libtelepathy
Version: 0.3.3-2
Severity: minor
User: [email protected]
Usertags: no-add-needed
Tried to build your package and it fails to build with GNU binutils-gold. The
important difference is that --no-add-needed is the default behavior of of GNU
binutils-gold. Please provide all needed libraries to the linker when building
your executables.
More informations can be found at
http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking
/bin/bash ../libtool --tag=CC --mode=link cc -std=gnu99 -Wall
-I/usr/include/telepathy-1.0 -I/usr/include/dbus-1.0 -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/lib/dbus-1.0/include -g -O2 -g -Wall -O2
-o tp-get-connmgr-info tp_get_connmgr_info-tp-get-connmgr-info.o
libtelepathy.la
cc -std=gnu99 -Wall -I/usr/include/telepathy-1.0 -I/usr/include/dbus-1.0
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/lib/dbus-1.0/include
-g -O2 -g -Wall -O2 -o .libs/tp-get-connmgr-info
tp_get_connmgr_info-tp-get-connmgr-info.o ./.libs/libtelepathy.so
/usr/bin/ld: tp_get_connmgr_info-tp-get-connmgr-info.o: in function
print_parameter:tp-get-connmgr-info.c:10: error: undefined reference to
'g_print'
/usr/bin/ld: tp_get_connmgr_info-tp-get-connmgr-info.o: in function
print_parameter:tp-get-connmgr-info.c:19: error: undefined reference to
'g_print'
/usr/bin/ld: tp_get_connmgr_info-tp-get-connmgr-info.o: in function
print_parameter:tp-get-connmgr-info.c:16: error: undefined reference to
'g_print'
/usr/bin/ld: tp_get_connmgr_info-tp-get-connmgr-info.o: in function
print_parameter:tp-get-connmgr-info.c:13: error: undefined reference to
'g_print'
/usr/bin/ld: tp_get_connmgr_info-tp-get-connmgr-info.o: in function
main:tp-get-connmgr-info.c:49: error: undefined reference to
'g_hash_table_foreach'
/usr/bin/ld: tp_get_connmgr_info-tp-get-connmgr-info.o: in function
print_protocol:tp-get-connmgr-info.c:31: error: undefined reference to
'g_hash_table_foreach'
collect2: ld returned 1 exit status
make[5]: *** [tp-get-connmgr-info] Error 1
--- End Message ---
--- Begin Message ---
Version: 0.3.3-2+rm
libtelepathy is no longer in unstable. It'll leave testing when Empathy 2.28
finally migrates.
On Fri, 27 Nov 2009 at 05:36:10 +0000, Debian Bug Tracking System wrote:
> We believe that the bug you reported is now fixed; the following
> package(s) have been removed from unstable:
>
> libtelepathy | 0.3.3-2 | source
> libtelepathy-dbg | 0.3.3-2 | alpha, amd64, armel, hppa, hurd-i386, i386,
> ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
> libtelepathy-dev | 0.3.3-2 | alpha, amd64, armel, hppa, hurd-i386, i386,
> ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
> libtelepathy2 | 0.3.3-2 | alpha, amd64, armel, hppa, hurd-i386, i386,
> ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
>
> ------------------- Reason -------------------
> ROM; superseded upstream
> ----------------------------------------------
[...]
> Packages are usually not removed from testing by hand. Testing tracks
> unstable and will automatically remove packages which were removed
> from unstable when removing them from testing causes no dependency
> problems. The release team can force a removal from testing if it is
> really needed, please contact them if this should be the case.
--- End Message ---
