Bug#688319: devscripts: Please consider including the 'yodack' tool

[Gergely Nagy]

Luca Capello <luca at pca.it> writes:

> On Fri, 28 Sep 2012 15:07:47 +0200, Gergely Nagy wrote:
>> FWIW, since the example given in the bug report is fairly verbose, and
>> that tends to put off some people, I'd like to mention that yodack does
>> not need the verboseness, that is merely an option.
>>
>> The following command does exactly the same thing that the example I
>> originally posted:
>>
>> $ yodack ftp-master dm algernon at madhouse-project.org \
>>          allow dh-exec ivykis deny eglibc bash
>
> IMHO this relies too much on the debian-keyring package, which is not
> always in sync with the real situation:

Oh, right. I haven't thought of that. Thanks for the patch, I'll review
& apply in a bit!

[...]
> $ git diff
> [attached below]
> $ USER=gismo ./yodack ftp-master dm 31455D17 keyring ~/.gnupg/pubring.gpg allow bacula
> [verification and GnuPG stuff]
> Upload to 'ftp-master', how to I know not.
> [no exit error code]

Hrm, it should exit with a non-zero code there. I'll fix that too,
thanks for noticing it!

> BTW, is there any reason not to use dput/dcut for upload, but instead a
> custom curl command?

Because when the tool was originally written, neither dput nor dcut were
happy about .dak-command files for one, and because for uploading a
single file, they both seemed like overkill to begin with.

(In all honesty, a longer-term plan is to improve yodack to the point
where it can replace dcut alltogether.)

-- 
|8]