Re: New Package Developer Needs A Little Help
> On May 15, Paul Serice wrote
> > I have the latest dpkg-dev, but my dpkg-shlibdeps gives me an error
> > every time it's run -- even when it's run from "good" packages like
> > hello and tar.
> > The error is as follows:
> > dpkg-shlibdeps: warning: unknown output from ldd on 'Crafty':
> > /libm.so.5 => lib/libm.so.5 (0x4000b000)'
> Are you sure you are using the latest dpkg and dpkg-dev (220.127.116.11)? The
> latest versions are in project/experimental, not in unstable.
> According to dpkg's changelog, dpkg handles the new ldd output from 18.104.22.168
> > The second problem is controlling which Debian version number gets
> > slapped on the end to .deb, .dsc, .diff.gz, and .orig.tar.gz. When I
> > run "dpkg-source -b crafty-11.23" I get the following error:
> > "dpkg-source: warning: source directory ./crafty-11.23' is not
> > <sourcepackage>-<upstreamversion> 'Crafty-11.23.1' ".
> > For some reason it wants to slap on a ".1" when I need it slap on a
> > "-1". Can someone tell me how I tell it that the upstream version is
> > "11.23" instead of "11.23.1"?
> (I'm not sure if it is relevant, but just in case: I use debmake for my
> packages). Probably you've done something like 'dch -v 11.23.1' instead of
> 'dch -v 11.23', and now the version number in debian/changelog is wrong.
> Just editing this file should fix it then.
Right again. I had a typo in debian/changelog.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .