Re: handling dependecy on libc6 2.3.5 ?

["Mehul N. Sanghvi" <mehul.sanghvi@gmail.com>]

Roberto C. Sanchez said the following on 9/4/2006 5:25 PM:
> On Mon, Sep 04, 2006 at 05:04:14PM -0400, Mehul N. Sanghvi wrote:
> > 'allo,
> >
> >    One of the things that spidermonkey-bin depends on is (libc6 >= 2.3.5).  
> >    I am assuming that if I do a backport, it is OK to have libc6 = 2.3.2 
> > (sarge) and build against that, yes ?
> That depends.  Does the package depend on (libc6 >= 2.3.5) because the
> source package Build-Depends on that version or because the
> ${shlibs:Depends} was expanded for the binary package when it was built?
> If it is the former, then there must be some feature of the new version
> of the library that is used by the package.  If it is the latter, then
> you should not have to do anything, as recompiling for Sarge will create
> a dependency for the correct version of libc6.
>
> Regards,
>
> -Roberto


It seems to be because of ${shlibs:Depends} so I should be OK as you've pointed 
out.  There are several dependencies though, like debhelper, for which it seems 
to be wanting a specific version ( >= 5.0.37.2 ).  How do I handle those ?  Do 
I have to backport the things needed ?

Here's the output from when I run debuild:

% debuild
dpkg-buildpackage: source package is xulrunner
dpkg-buildpackage: source version is 1.8.0.5-3
dpkg-buildpackage: source maintainer is Mike Hommey <glandium@debian.org>
dpkg-buildpackage: host architecture is powerpc
dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 5.0.37.2) 
python-support (>= 0.3) java-gcj-compat-dev (>= 1.0.56) ecj-bootstrap (>= 
3.1.2-6) dpkg-dev (>= 1.13.19)
dpkg-buildpackage: Build dependencies/conflicts unsatisfied; aborting.
dpkg-buildpackage: (Use -d flag to override.)
debuild: fatal error at line 765:
dpkg-buildpackage failed!



cheers,

        mehul


--
Mehul N. Sanghvi
email: mehul.sanghvi@gmail.com