secret key needs to be abstracted out.

[morgajel]

I haven't dug into this that much, but the fact that it's hardcoded to sign as you makes me think that perhaps something is hardcoded that perhaps shouldn't be.

That said, you may want to make a note in the readme that people can create a package without signing it via "debuild -i -us -uc -b" (I know I don't have any signing keys set up as this is my first time using debuild).

dpkg-deb: building package `minutor' in `../minutor_2.0.1_amd64.deb'.
 dpkg-genchanges  >../minutor_2.0.1_amd64.changes
dpkg-genchanges: including full source code in upload
 dpkg-source --after-build minutor
dpkg-buildpackage: full upload; Debian-native package (full source is included)
Now running lintian...
W: minutor source: ancient-standards-version 3.9.3 (current is 3.9.6)
E: minutor: helper-templates-in-copyright
W: minutor: binary-without-manpage usr/bin/minutor
Finished running lintian.
Now signing changes and any dsc files...
 signfile minutor_2.0.1.dsc Sean kasun <sean@seancode.com>
gpg: skipped "Sean kasun <sean@seancode.com>": secret key not available
gpg: /tmp/debsign.ZG5G8p0b/minutor_2.0.1.dsc: clearsign failed: secret key not available
debsign: gpg error occurred!  Aborting....
debuild: fatal error at line 1295:
running debsign failed

[mrkite]

I believe if you change the maintainer in the debian/control file, it'll prompt you to sign with your own key.

But yes, you can just tell it not to sign the .deb file, which is fine for personal use.