Adam D. Barratt writes: > On Wed, 2020-10-28 at 15:03 +0000, halfdog wrote: > > According to Debian Bullseye manpage "debsign" should handle the > > "DEBSIGN_PROGRAM" environment variable as follows: > > > > DEBSIGN_PROGRAM > > Setting this is equivalent to giving a -p option. > > Well... not really. > > The sentences just before that quote say (emphasis mine): > > "The two configuration files /etc/devscripts.conf and ~/.devscripts are > sourced in that order to set configuration variables. Command line > options can be used to override configuration file settings. > **Environment variable settings are ignored for this purpose.** The > currently recognised variables are: " > > So debsign ignoring the setting of that variable in the environment is > behaving precisely as documented. This is common across almost all > variables for almost all tools in devscripts. > > Regards, > > Adam
Sorry, my fault. I did wishful, sloppy reading, hoping that environment variables only cannot override settings already in the devscripts.conf instead of every time. The reason why I was trying the most obscure ways to change the gpg program is, that there seems no way to create a "gbp buildpackage" command line, that changes DEBSIGN_PROGRAM without the need to have root privileges. "gbp buildpackage" calls "debbuild" with controllable arguments (via "--git-builder" option". Is there any way known to influence "debsign" via "debuild" command line arguments without touching the file system?
