While moving from running ./frido.py manually to running it from a crontab entry, it was spotted that a few environment variables set in the interactive shell were missing:
DEBEMAIL=mail@address
QUILT_PATCHES=debian/patches
Setting the latter unconditionally is trivial, but the former might be a little less easy: it might be possible to derive this from the configured GPG key, from the git-level identity, from previous git commits, and/or from previous debian/changelog entries. Of course, it could be set in the configuration file but having a key fingerprint means not exposing any mail address in a public repository, so that's been preferred until now.
Initial gut feeling would be:
- maybe mention
~/.gitconfig and/or .git/config (in the git.work_dir directory) in README.md;
- derive the mail address from
git config --get user.email at runtime;
- set
DEBEMAIL accordingly (logging a warning if it's already set, with a different value);
- perform a GPG key lookup based on that mail address and make sure one of the fingerprints matches the configured signing key, for consistency.
While moving from running
./frido.pymanually to running it from a crontab entry, it was spotted that a few environment variables set in the interactive shell were missing:Setting the latter unconditionally is trivial, but the former might be a little less easy: it might be possible to derive this from the configured GPG key, from the git-level identity, from previous git commits, and/or from previous
debian/changelogentries. Of course, it could be set in the configuration file but having a key fingerprint means not exposing any mail address in a public repository, so that's been preferred until now.Initial gut feeling would be:
~/.gitconfigand/or.git/config(in thegit.work_dirdirectory) in README.md;git config --get user.emailat runtime;DEBEMAILaccordingly (logging a warning if it's already set, with a different value);