From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: registry seems to be saved for 27.0.50 any longer/Gnorb
Date: Thu, 26 Apr 2018 17:15:18 +0200 [thread overview]
Message-ID: <87lgdaj8xl.fsf@mat.ucm.es> (raw)
In-Reply-To: <87efj2drl6.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
>>> "Michael" == Michael Heerdegen <michael_heerdegen@web.de> writes:
> Uwe Brauer <oub@mat.ucm.es> writes:
>> Does anybody suffer the same behavior?
> Yes, I had suffered the same.
> The Gnorb registry was horribly broken at that time. It has now
> been fixed, so you need to upgrade. You probably also need to fix
> your Gnus registry. How that can be done should have been posted to
> this Group (or emacs-dev). Or wait until Eric tells more details.
I just found Eric's message from a month ago where he describes the
problem the fix is, besides using his function, pull and recompile
emacs, which I am doing right now.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]
prev parent reply other threads:[~2018-04-26 15:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 12:52 Uwe Brauer
2018-04-26 13:28 ` Michael Heerdegen
2018-04-26 15:09 ` Uwe Brauer
2018-04-26 15:18 ` Michael Heerdegen
2018-04-26 15:55 ` Uwe Brauer
2018-04-26 16:35 ` [change the default registry names] (was: registry seems to be saved for 27.0.50 any longer/Gnorb) Uwe Brauer
2018-04-26 18:46 ` [change the default registry names] Eric Abrahamsen
2018-04-26 19:19 ` Michael Heerdegen
2018-04-26 19:30 ` Eric Abrahamsen
2018-04-27 9:24 ` Uwe Brauer
2018-04-27 16:59 ` Bob Newell
2018-04-27 18:27 ` Eric Abrahamsen
2018-05-07 8:05 ` Uwe Brauer
2018-05-07 23:43 ` Bob Newell
2018-05-10 8:11 ` Uwe Brauer
2018-05-10 12:38 ` Michael Heerdegen
2018-05-11 17:22 ` Uwe Brauer
2018-05-11 17:28 ` Bob Newell
2018-05-07 8:07 ` [setq does not work] (was: [change the default registry names]) Uwe Brauer
2018-04-26 15:15 ` Uwe Brauer [this message]
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=87lgdaj8xl.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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).