From: Sebastian Lipp <bacuh@riseup.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] gpg-options.rb: how to set always_trust
Date: Tue, 25 Jan 2011 15:32:56 +0100 [thread overview]
Message-ID: <1295964928-sup-1373@fly> (raw)
In-Reply-To: <AANLkTimTV+qSRrVzMd=u7Z1egi2njbiHf2qqQDqOChqY@mail.gmail.com>
Excerpts from Hamish D's message of Mo Jan 24 11:34:28 +0100 2011:
> * your gpg key type, including whether you have a separate sub key for
> signing. If your key is on public keyservers then the key ID could also be
> useful.
A750401F
> * whether you use the gpgkey option in .sup/config.yaml
Yes, I do. I tried to delete this option and moved all my GPG-related
hooks out of sup's reach. The last thing I just tried was pulling again.
Nothing helped.
In my last mail I told that I can't sign. That's not true (anymore). I
can sign but when I choose sign and encrypt there is no signature. Can't
say whether this was a misinformation by me or is related to the latest
pull.
All I can tell is that it worked like a charm since I use sup. It might
be related to the change to GPGME.
--
basti
Die Zwingburg des Privateigentums wird fallen und auf ihren Trümmer wird
sich der Tempel des Kommunismus erheben.
Alle Festungen des Staates werden kapitulieren müssen, und in herrlicher
Gestalt wird sich zeigen der Genius der Anarchie.
Wer diesen Idealen zuzuschreiten entschlossen ist, der reiche uns die
Hände!
-- Johann Most
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-01-25 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 8:25 Sebastian Lipp
2011-01-23 12:17 ` Michael Stapelberg
[not found] ` <AANLkTimJZiRE31R5KJBdqZv5L17qhKeLjbO4fWM5LfD2@mail.gmail.com>
2011-01-23 22:09 ` Sebastian Lipp
2011-01-24 9:15 ` Shadowfirebird
[not found] ` <AANLkTimrPK4Bt7z+uN5AkShp3uJSw3OdbR2A-R0p4RoA@mail.gmail.com>
[not found] ` <AANLkTimB43mBbe-3EvRxZHCK_n9-Xy0mL1MHRGSO6MTf@mail.gmail.com>
2011-01-24 10:34 ` Hamish D
2011-01-25 14:32 ` Sebastian Lipp [this message]
2011-01-30 23:04 ` Hamish
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1295964928-sup-1373@fly \
--to=bacuh@riseup.net \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox