#699366 dput-ng: Please, respect ~/.devscripts settings

#699366#5
Date:
2013-01-30 17:51:08 UTC
From:
To:
Dear Maintainer,

it would be good, if dput-ng utilites will respect
~/.devscripts options. For example "export DEBSIGN_KEYID=....",
like debsign does.

Thanks,

Anton

#699366#10
Date:
2013-02-02 20:43:58 UTC
From:
To:
Hi,

we cannot easily support ~/.devscripts because that's a sourced shell
fragment. It's somewhat unfeasible to interpret and parse that in a
third party Python script which is not (directly) related to devscripts.

Having that said, we may honor an exported DEBSIGN_KEYID environment if
people find this to be a common variable to define their default key id
(i.e. agnostic to debsign, like DEBEMAIL for example).

#699366#15
Date:
2013-03-09 09:53:08 UTC
From:
To:
Since version 1.4, dput-ng defines a new option, default_keyid, which
permits to specify which key is to be considered the default.
http://anonscm.debian.org/gitweb/?p=collab-maint/dputng.git;a=commitdiff;h=047ea30199426bf7e3f455af67e24e495c64b38e

#699366#18
Date:
2013-05-05 12:08:36 UTC
From:
To:
* Arno Töll <arno@debian.org>, 2013-02-02, 21:43:

Actually .devscripts syntax is a strict subset of shell syntax, which
was designed to be easily parsable by software not written in shell.
(For example, many devscripts programs are written in Perl).

Here's what a comment of /etc/devscripts.conf reads:

# This file is sourced by /bin/bash, and should only contain
# comment lines (beginning with a '#'), and lines of the form
# VARIABLE=value
# The value must be quoted if there are spaces in it.
# Variables corresponding to switches (on/off; yes/no) must take
# one of the values 'yes' or 'no'.
# The variable names are all of the form PROGNAME_VARNAME,
# or DEVSCRIPTS_VARNAME if they are more generally applicable.

If you wanted, you could easily parse it with the shlex module.

Now, this is a real reason not to parse this file. dput-ng is not a part
of devscripts, so it has no business it reading devscripts'
configuration file.

#699366#21
Date:
2014-09-24 20:14:17 UTC
From:
To:
Re: Jakub Wilk 2013-05-05 <20130505120836.GA6885@jwilk.net>

Those perl programs do very ugly shell calls to do the parsing...

That said, it would be good enough to just read the file and look for
^\s*DEBSIGN_KEYID=(\S+)

I don't see a problem here. dput-ng shouldn't modify the file, but
just reading it wouldn't do any harm.

Also, why not just defer the signing to debsign? No doing that sounds
just like asking for extra work. And don't tell me there's people
uploading things that don't have devscripts installed anyway...

So far my dput-ng experience was pretty disappointing :( (See also
#741966)

Christoph