Your message dated Sun, 13 Sep 2015 18:44:39 +0000
with message-id <[email protected]>
and subject line Bug#572829: Removed package(s) from unstable
has caused the Debian Bug report #558867,
regarding Resolve unresolved symbols in shared libraries
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.)
--
558867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558867
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: gsnmp
Version: 0.2.0-2.1
Severity: wishlist
User: [email protected]
Usertags: unresolved-symbols-so
I build all packages some time ago with binutils-gold and your package build
without an hard failure, but I noticed that you seems to provide a library in
a specific library package so other packages can link against it without
problems.... but your shared object has still some unresolved symbols which
the program which links agaomst it must resolve. This isnt a good idea because
when you introduce new dependencies the package previously linked against the
old version will break because it doesnt know about the new dependency.
Maybe you could link against all needed libraries so programs must not link
against libraries which it doesnt need to use.
Maybe it is related to following bugs which hard failed due to unresolved
symbols in programs
http://bugs.debian.org/cgi-bin/[email protected];tag=no-add-needed
More informations can be found at
http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking
dpkg-shlibdeps already showed you the related warnings:
dpkg-shlibdeps: warning: symbol gnet_inetaddr_equal used by
debian/libgsnmp0/usr/lib/libgsnmp.so.0.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol g_malloc0 used by
debian/libgsnmp0/usr/lib/libgsnmp.so.0.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol g_main_loop_new used by
debian/libgsnmp0/usr/lib/libgsnmp.so.0.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol g_main_loop_run used by
debian/libgsnmp0/usr/lib/libgsnmp.so.0.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol g_scanner_input_text used by
debian/libgsnmp0/usr/lib/libgsnmp.so.0.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol gnet_sha_new used by
debian/libgsnmp0/usr/lib/libgsnmp.so.0.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol g_list_last used by
debian/libgsnmp0/usr/lib/libgsnmp.so.0.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol gnet_md5_final used by
debian/libgsnmp0/usr/lib/libgsnmp.so.0.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol g_list_append used by
debian/libgsnmp0/usr/lib/libgsnmp.so.0.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol gnet_md5_new used by
debian/libgsnmp0/usr/lib/libgsnmp.so.0.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: 72 other similar warnings have been skipped (use -v to
see them all).
--- End Message ---
--- Begin Message ---
Version: 0.3.0-2+rm
Dear submitter,
as the package gsnmp has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/572829
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
