From: Glyn Millington <glyn@millingtons.org>
Subject: Re: update Gnus to 5.10.6 in Debian/unstable
Date: Wed, 11 Feb 2004 08:25:15 +0000 [thread overview]
Message-ID: <87oes66n10.fsf@millingtons.org> (raw)
In-Reply-To: <87r7x2ngyu.fsf@rechner1.ddorf.de>
Fabian Braennstroem <f.braennstroem@gmx.de> writes:
> I have a problem updating Gnus in Debian/unstable. The apt-get
> installation works ok, but starting Gnus I see wrong numbers of unread
> article in my group-buffer. E.G. this group is not even there. Typing L
> I find gnu.emacs.gnus, but I am not able to access the group. I get
> this error-message:
>couldn't request group (no such directory)
Interesting - I've no idea why this is so! While you are waiting for
someone with a Clue to answer .... try unsubscribing the group and then
subscribing again. (For some reason your new Gnus is not finding the
group, so give it a reason to look again!)
> Even sending mails with smtp doesn't work anymore (I forgot the
> error-message).
The error-message would certainly help.
>
> What can I do to upgrade Gnus nicely? Should I compile it from source?
That is easy enough to do. Unpack the tarball into either $HOME/elisp or
somewhere in /usr/local (so that it will not interfere with Debian's
package management). Do the "./configure ; make" routine but don't do
"make install" - just add the relevant directories to your emacs
load-path _early_ (ie before you do anything else about Gnus!) in your
.emacs
eg
8<------8<------8<------8<------8<------8<------8<------8<------8<------
;; for the latest greatest gnus.
(setq load-path (cons (expand-file-name "~/elisp/gnus/lisp") load-path))
(require 'gnus-load)
(require 'info)
(setq Info-directory-list
(cons "~/elisp/gnus/texi" Info-directory-list))
8<------8<------8<------8<------8<------8<------8<------8<------8<------
Glyn
next parent reply other threads:[~2004-02-11 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r7x2ngyu.fsf@rechner1.ddorf.de>
2004-02-11 8:25 ` Glyn Millington [this message]
[not found] ` <874qtxy7pe.fsf@rechner1.ddorf.de>
[not found] ` <wn5lln9r9em.fsf@linhd-2.ca.nortel.com>
[not found] ` <87hdxxpkpk.fsf@rechner1.ddorf.de>
[not found] ` <wn5ad3pr1fr.fsf@linhd-2.ca.nortel.com>
[not found] ` <873c9h8au2.fsf@rechner1.ddorf.de>
2004-02-12 3:27 ` Linh Dang
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=87oes66n10.fsf@millingtons.org \
--to=glyn@millingtons.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).