New Package Developer Needs A Little Help
I've been given the go ahead to bundle up Crafty -- a very strong,
free chess program. It's my first package, and I have two minor
problems, and I thought this might be the place to get some advice.
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)'
dpkg-shlibdeps: warning: unknown output from ldd on 'Crafty':
/libc.so.5 => lib/libc.so.5 (0x40014000)'
dpkg-shlibdeps: warning: ldd on 'Crafty' gave nothing on standard
output
dpkg: --search needs at least one file name pattern argument
I've been able to get around this (for testing purposes) by just hard
coding the libc5 "Depends:" to what my system uses thereby avoiding a
call to dpkg-shlibdeps. I don't think this is portable enough
though.
Has someone else seen this error before?
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"?
The best I've been able to do is to invoke dpkg-gencontrol with
"-v11.23-1". This seems to work, but only when doing "debian/rules
binary". It has no effect on dpkg-source -b.
I'd like to say I'm having no trouble building the binary packages
using "dpkg --build <package>". It's just the source packages, and
any help would be greatly appreciated.
Thanks
Paul Serice
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: