On Wed, Dec 2, 2009 at 6:05 AM, rosea grammostola
<rosea.grammostola@gmail.com> wrote:
dpkg-shlibdeps: warning: dependency on libXext.so.6 could be avoided if
"debian/openoctave/usr/bin/openoctavesequencer
debian/openoctave/usr/bin/openoctave" were not uselessly linked against it
(they use none of its symbols).
dpkg-shlibdeps: warning: dependency on libSM.so.6 could be
avoided if "debian/openoctave/usr/bin/openoctavesequencer
debian/openoctave/usr/bin/openoctave" were not uselessly linked against it
(they use none of its symbols).
dpkg-shlibdeps: warning: dependency on libICE.so.6 could be
avoided if "debian/openoctave/usr/bin/openoctavesequencer
debian/openoctave/usr/bin/openoctave" were not uselessly linked against it
(they use none of its symbols).
How find out which depends packages is this all about?
This shows up because the upstream build system links the binaries
against libraries that they do not use. This could be a bug in the
upstream build system or it could be a bug in another package that
your package builds against. In this case I'm guessing it would
probably be the latter. Try getting help on #debian-mentors on IRC to
work out where the bug is.
ancient-libtool po/gettext-0.10.35-kde/ltconfig
What does this mean and how to fix this?
Please see the lintian-info output for this tag. Also available here:
http://lintian.debian.org/tags/ancient-libtool.html
In this case I'm guessing the upstream package has an embedded code
copy of gettext, I'd suggest asking upstream to remove it and switch
to the standard system gettext.