Re: Trying to backport valgrind to lenny
Carsten Aulbert schrieb am Thursday, den 27. May 2010:
> Hi Alex (and Jordan)
>
> On Thursday 27 May 2010 15:13:31 Alexander Wirt wrote:
> > > ../../backport -l3.3.1 -c base.lenny.amd64 valgrind_3.5.0-3.dsc
> > > gpgv: keyblock resource `/root/scarsten/.gnupg/trustedkeys.gpg': general
> > > error gpgv: Signature made Tue Nov 17 17:03:13 2009 CET using DSA key ID
> > > B29396EB gpgv: Can't check signature: public key not found
> > > dpkg-source: warning: failed to verify signature on
> > > ./valgrind_3.5.0-3.dsc dpkg-source: info: extracting valgrind in
> > > valgrind-3.5.0
> > > dpkg-source: info: unpacking valgrind_3.5.0.orig.tar.gz
> > > dpkg-source: info: applying valgrind_3.5.0-3.diff.gz
> > > parsechangelog/debian: warning: 'since' option specifies non-existing
> > > version parsechangelog/debian: warning: use newest entry that is smaller
> > > than the one specified
> > > dch warning: new version (1:3.5.0-3~bpo50+1) is less than
> > > the current version number (1:3.5.0-3).
> > > Running pdebuild --buildresult .. --pbuilder cowbuilder --debbuildopts -d
> > > - v3.3.1 -- --basepath /var/cache/pbuilder/base.lenny.amd64.cow
> > > W: /root/scarsten/.pbuilderrc does not exist
> > >
> > > -> using cowbuilder as pbuilder
> > >
> >
> > ^^^^^ HU? unmet build dependencys. The "script" should stop here.
> >
> > > dpkg-buildpackage: warning: using a gain-root-command while being root
> >
> > unfortunatly is doesn't. check your build dependencys.
>
> I did (see rest of my original email), all build deps are available satisfying
> the version requirements.
>
> But you may be right, I'll try it by hand...
> > > dpkg-checkbuilddeps: Unmet build dependencies: autotools-dev dpatch (>>
> > > 2.0.0) gdb libc6-dev-i386 (>> 2.3.0)
> > > W: Unmet build-dependency in source
Ok, let me see:
libc6-dev-i386: libc6-dev-i386 | 2.7-18lenny1 | stable | amd64
2.7 is smaller than 2.3.0 so this won't work with lenny.
dpatch: dpatch | 2.0.30 | stable | source, all
bigger than 2.0.0
so I guess libc6-dev-i386 is the problem.
Alex
Reply to: