On Fri, Feb 25, 2000 at 11:03:21PM +0100, Jordi wrote: > Also, it contains the new upstream source, tarred and unpacked: > amcl-0.7.0 amcl-0.7.0.tar.gz > > With this files, I do a dpkg-buildpackage -rfakeroot from amcl-0.7.0/, which > builds an amcl_0.7.0-1.tar.gz and ends with a: > dpkg-buildpackage: Debian-specific package; upload is full source > > I don't know what's going on with this. My other packages create an > amcl_0.7.0.orig.tar.gz when I build them. The rules in amcl is nearly > identical to those other packages.
.orig.tar.gz isn't built by the tools. You should rename the amcl-0.7.0.tar.gz you downloaded to amcl_0.7.0.orig.tar.gz yourself. dpkg-buildpackage says it's a Debian-specific package because it can't find the .orig.tar.gz. It assumes there is no upstream source, so it builds you a .tar.gz and a .dsc -- instead of the usual .orig.tar.gz, .diff.gz and .dsc combination. > Also, I get this lintian error, which I think is a bug: > E: amcl: manpage-for-x11-binary-in-wrong-directory usr/X11R6/bin/amcl > usr/share/man/man1/amcl.1x.gz > The policy states that _any_ manual goes into share, no /usr/X11R6/man. Am I > right? I don't know. But here's a simple fix -- put your binary in /usr/bin instead of /usr/X11R6/bin. Policy and the FHS do not say that all X clients go in /usr/X11R6, only that the standard components do. I put all of my binaries in /usr/bin, even for X programs. Hamish -- Hamish Moffatt VK3SB. CCs of replies on mailing lists are welcome.
