[Buildd-tools-devel] Bug#520158: Bug#520158: sbuild: Please document how to avoid changing maintainer/uploader or signing the build

[Simon McVittie]

On Tue, 17 Mar 2009 at 21:16:58 +0000, Roger Leigh wrote:
> On Tue, Mar 17, 2009 at 07:43:13PM +0000, Simon McVittie wrote:
> > In older versions of sbuild, this configuration worked:
> > 
> >     # Don't override the maintainer or uploader name, just the key
> >     # with which to sign the package...
> >     #$maintainer_name='';
> >     #$uploader_name='';
> >     $key_id='0x5530ec76';
> > 
> >     # ... but actually, don't sign the package anyway - I'll use
> >     # debsign
> >     $pgp_options = '-us -uc';

It appears that setting $pgp_options = ['-us', '-uc'] is now the magic rune
to not do signing, and '-us -uc' does not work (and indeed actively breaks
my configuration, since ['-us', '-uc'] is now the default so deleting the
$pgp_options line entirely is sufficient).

Is there a better way than this to use sbuild as a super-debuild, i.e. just
run dpkg-buildpackage without any special options? With my current setup
I can do "sbuild -As foo_bar.dsc" to do any maintainer or sponsored upload.

Perhaps sbuild could even operate like this by default (i.e. when
unconfigured), which would be consistent with dpkg-buildpackage and friends?
I can see that this would make the default configuration wrong for buildds,
which *do* want to override the maintainer, but there are fewer buildds than
Debian developers!

In this respect I think using $ENV{DEBEMAIL} is a bit of a backward step -
as I understand it, buildds want to set $maintainer_name per-machine, and
mere developers like me want to leave it unset so we can sponsor, so taking it
from the environment for each user doesn't seem right for anyone.

(I build all my packages in sbuild as per
<http://www.pseudorandom.co.uk/2008/sbuild-dm/> - if you can suggest a good
man page or readme in the sbuild package where I should explain this, I'm
happy to provide similar text as a patch against sbuild)

Regards,
    S