Re: Wrong dependencies for packages on build, how to fix?
On Thu, Oct 25, 2001 at 10:54:21AM +0300, M. Tavasti wrote:
> But sometimes new package get's wrong dependencies. For example
> build xemacs21 depends on libldap2 (>= 2.0.14-1), and libldap2
> installed on system is 2.0.14-0potato. And dependencies are not in
> control file, they come from substvars. And it is generated with some
> debhelper-scripts. Debhelper says to be version 3.0.15potato1, which
> is 3.0.15 ported for potato.
dpkg-shlibdeps generates this based on /var/lib/dpkg/info/*.shlibs,
which are produced by each package that provides shared libraries. If
you're backporting libraries and changing their version numbers, you'll
need to find the part of their build scripts that sets the shared
library dependencies and make sure the version number is appropriate. It
might be written by hand or with the dh_makeshlibs program.
> And should I report this as bug in debhelper? And original debhelper
> or potato-ported?
If anything it would be dpkg-dev, but no. If shared library dependencies
are set by hand then you need to be aware of that when changing the
version number.
Cheers,
--
Colin Watson [cjwatson@flatline.org.uk]
Reply to: