Your message dated Sat, 12 Mar 2011 17:49:25 +0000
with message-id <[email protected]>
and subject line Bug#558926: fixed in libtododb 0.11-3
has caused the Debian Bug report #558926,
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.)
--
558926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558926
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libtododb
Version: 0.11-2
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 gpe_error_box used by
debian/libtododb0/usr/lib/libtododb.so.0.0.0 found in none of the libraries.
--- End Message ---
--- Begin Message ---
Source: libtododb
Source-Version: 0.11-3
We believe that the bug you reported is fixed in the latest version of
libtododb, which is due to be installed in the Debian FTP archive:
libtododb-dev_0.11-3_amd64.deb
to main/libt/libtododb/libtododb-dev_0.11-3_amd64.deb
libtododb0-dbg_0.11-3_amd64.deb
to main/libt/libtododb/libtododb0-dbg_0.11-3_amd64.deb
libtododb0_0.11-3_amd64.deb
to main/libt/libtododb/libtododb0_0.11-3_amd64.deb
libtododb_0.11-3.debian.tar.gz
to main/libt/libtododb/libtododb_0.11-3.debian.tar.gz
libtododb_0.11-3.dsc
to main/libt/libtododb/libtododb_0.11-3.dsc
libtododb_0.11.orig.tar.bz2
to main/libt/libtododb/libtododb_0.11.orig.tar.bz2
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Neil Williams <[email protected]> (supplier of updated libtododb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sat, 12 Mar 2011 17:25:28 +0000
Source: libtododb
Binary: libtododb-dev libtododb0 libtododb0-dbg
Architecture: source amd64
Version: 0.11-3
Distribution: unstable
Urgency: low
Maintainer: Moray Allan <[email protected]>
Changed-By: Neil Williams <[email protected]>
Description:
libtododb-dev - library that provides access to gpe-todo's database
[development]
libtododb0 - library that provides access to gpe-todo's database [runtime]
libtododb0-dbg - library that provides access to gpe-todo's database
[debugging]
Closes: 558926
Changes:
libtododb (0.11-3) unstable; urgency=low
.
* Update watch file
* Update outdated build-dep versions.
* Tweak copyright ref to GPL location (lintian)
* Move to source 3 for upstream bz2 support
* update dbg section to avoid override disparity
* Add gpewidget linkage to resolve symbols (Closes: #558926)
* Add symbol versioning support.
Checksums-Sha1:
4f19cea49ffaded5a498051787a987fee3e3e922 1469 libtododb_0.11-3.dsc
44a89eb3aa981a587418e7acd2974e82c7882048 214770 libtododb_0.11.orig.tar.bz2
afd6ec4b6e4a34d1c2780e2669bb3116afd0861a 3245 libtododb_0.11-3.debian.tar.gz
81d603b6d1c2c478c943d5839586982248f94ae3 19148 libtododb-dev_0.11-3_amd64.deb
adce9e132d94fd9ef080fc76f0026ad10e247e03 11342 libtododb0_0.11-3_amd64.deb
7d93e1604aa8f3a0ed767d59fddaca651082ff75 13636 libtododb0-dbg_0.11-3_amd64.deb
Checksums-Sha256:
17281121bdd5c4c50edf3044c8415c9ea9ef55effe20f15ab093aaaaf08280b1 1469
libtododb_0.11-3.dsc
8841680d9de5b30637719f62cf1c45579700e8eadb5d35b3ece5a637ee85d488 214770
libtododb_0.11.orig.tar.bz2
13f5257811b1d742be3f71568cc7a0c7d587c2b72002e29f4b3bf72d80fb7723 3245
libtododb_0.11-3.debian.tar.gz
8589fea35fc77b30b97a3e2e734d8101c57317473b8d8c4c8ae3dc30ec4081a7 19148
libtododb-dev_0.11-3_amd64.deb
ad22edf89de1241c751396aaa55720555b2555371128c3d8a2d76a61077a7ce4 11342
libtododb0_0.11-3_amd64.deb
d75536634152610d5add3c28e6bafcc3a809f0d87397dd79e2e10e8a6e848a92 13636
libtododb0-dbg_0.11-3_amd64.deb
Files:
a438c0d22aef01c7c776009601a355fd 1469 libs optional libtododb_0.11-3.dsc
d3fa3b6093eefdb374a78f0fa5d2eb9a 214770 libs optional
libtododb_0.11.orig.tar.bz2
a6870fcffe7543d29a2b548b9c63436a 3245 libs optional
libtododb_0.11-3.debian.tar.gz
07c20b0106f8f3ed7926f3467c6afc0a 19148 libdevel optional
libtododb-dev_0.11-3_amd64.deb
fd54053727da3112fd83e5873ac56cc6 11342 libs optional
libtododb0_0.11-3_amd64.deb
95bf9951294a33a750fde2a7becf6e8b 13636 debug extra
libtododb0-dbg_0.11-3_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk17rp4ACgkQiAEJSii8s+NpoACfbcwJPHx7/oflsN6DpnzApvRV
aaAAoL83XLm+IjqzlWZb8f2m/U17o+GV
=sbDP
-----END PGP SIGNATURE-----
--- End Message ---
