On Wed, 2005-07-13 at 14:01 +0200, Michael Banck wrote: > Well, only for revisions > 1, right? At least, this is the case here. > Which is what I would expect. Or maybe I misunderstood your concern.
It is expected behaviour for a standard build, but not expected behaviour for a "include full source build" (which is my understanding of the -s flag from the manpage). The use case is as follows. We are building a customised distribution loosely derived from Sarge, as such our package naming scheme is to append "string" + local_rev to the end of the Debian version. So for example the sysvinit package. In sarge the version number is 2.86.ds1-1 for us this would become 2.86.ds1-1crcnet0 (where crcnet is our local string, and 0 is our local revision number). We require a full source package (including .orig.tar.gz) so that debarchiver can import all the required package files into our local repository. The default build (dpkg-buildpackage) of this package does not include source (as expected), however I can force a full source package (which includes the .orig.tar.gz) to be generated by running dpkg-buildpackage -sa. The key to this issue for me, is that I expected sbuild -s to have a direct mapping to dpkg-buildpackage -sa. This is not the current behaviour. I felt it should be and it's a simple patch, so I am hoping to convince you that that should be the case. I'm fully aware that in the 'normal' case a build of a package with version number 2.86.ds1-1crcnet0 or even just 2.86.ds1-1 would not include source. But my interpretation of the sbuild manpage is that the -s option is intended to allow building of a full source package in cases where it would not usually be built. Does this make the situation clearer? Regards -- Matt Brown [EMAIL PROTECTED] Mob +64 275 611 544 www.mattb.net.nz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
