Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Trying to use gnus-cloud: what's the pinentry dialog? (and how can I get rid of it?)
Date: Thu, 23 Sep 2021 17:07:08 +0200	[thread overview]
Message-ID: <86mto3gwkj.fsf@dod.no> (raw)
In-Reply-To: <867dfck4g9.fsf@dod.no>

>>>>> Steinar Bang <sb@dod.no>:

>> And trying to "~-RET" on emacs 27.1 on debian bullseye gave me the error
>> message
>> gnus-cloud-decode-data: Invalid base64 data

>> Which, if memory doesn't fail me, is the error message that stopped me
>> from starting to use gnus-cloud in August of 2016...?

The available values for gnus-cloud-storage-method, are:
 - No encoding
 - Base64
 - Base64+gzip
 - EPG (the default)

I have tried Base64+gzip and I have tried "No encoding" and neither of
them works when decoding.

Storing in Base64+gzip gives "Invalid base 64 data" when reading.

Storing wih "No encoding" gives:
 Skipping article 20 because it didn’t match the Gnus Cloud method base64-gzip: (sequence: 16 type: :full storage-method: nil)

(which I don't understand at all because I had set
gnus-cloud-storage-method to "No encoding").

The only format that works, is EPG and that prompts me twice for a code
when saving, which is annoying.

But there is no prompt on load and the sync seems to work.

> Could my problem be a message with a bogus format?

> What happens if I delete all messages from the gnus-sync folder and
> start fresh?  The folder has 15 messages now, but has never actually
> worked, so AFAIK nothing depends on anything there.

Deleting all messages from the Emacs-Cloud nnimap folder seems to work
OK.  The two computers seems to have different ideas of what the
contents are (maybe because both use agent?), but deleting with "B DEL"
on the computer that showed one more article than the other, seemed to
flush the state for both of them.





  reply	other threads:[~2021-09-23 15:07 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-19 13:50 Steinar Bang
2021-09-19 14:16 ` Steinar Bang
2021-09-19 14:30   ` Steinar Bang
2021-09-19 14:47     ` Steinar Bang
2021-09-23 15:07       ` Steinar Bang [this message]
2021-09-23 15:25         ` Steinar Bang
2021-09-23 17:17           ` Steinar Bang
2021-09-23 17:42             ` Steinar Bang
2021-09-23 17:58               ` dick
2021-09-24  8:40                 ` Eric S Fraga
2021-09-24 20:18                   ` Steinar Bang
2021-09-26 15:44                     ` Eric S Fraga
2021-09-26 16:52                       ` Steinar Bang
2021-09-27 14:54                         ` Eric S Fraga
2021-10-02 11:27               ` Steinar Bang
2021-10-02 11:39                 ` Steinar Bang
2021-10-02 14:59                   ` Steinar Bang
2021-10-02 15:49                     ` Eric Abrahamsen
2021-10-02 16:19                       ` Steinar Bang
2021-10-03  8:46                         ` Steinar Bang
2021-10-03 17:30                           ` Steinar Bang
2021-10-04 14:43                             ` Steinar Bang
2021-10-04 18:00                               ` Steinar Bang
2021-10-04 19:19                                 ` Steinar Bang
2021-10-04 19:42                                   ` Steinar Bang
2021-10-04 20:09                                 ` Adam Sjøgren
2021-10-04 21:26                                   ` Steinar Bang
2021-10-05  8:41                                   ` Robert Pluim
2021-10-05 15:02                                     ` Adam Sjøgren
2021-10-05 15:41                                       ` Robert Pluim
2021-10-05 16:20                                         ` Adam Sjøgren
2021-10-05 15:14                                   ` Eric Abrahamsen
2021-10-05 16:17                                     ` Adam Sjøgren
2021-10-05 17:46                                       ` Eric Abrahamsen
2021-10-05 17:52                                         ` Adam Sjøgren
2021-09-23 17:14         ` Steinar Bang

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=86mto3gwkj.fsf@dod.no \
    --to=sb@dod.no \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).