Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: [BUG]: Can't send news after upgrading Gnus
Date: Wed, 14 Jan 2004 09:14:22 +0900	[thread overview]
Message-ID: <b9yhdyzpesh.fsf@jpl.org> (raw)
In-Reply-To: <ilubrp78klz.fsf@latte.josefsson.org>

>>>>> In <ilubrp78klz.fsf@latte.josefsson.org>
>>>>>	Simon Josefsson <jas@extundo.com> wrote:

> Xavier Maillard <zedek@gnu-rox.org> writes:

>> My problem is that I have 2 different sha1 package here:
>>
>> * one in flim/
>> * and one installed by Gnus Makefile in /opt/share/emacs/site-lisp
>>
>> Is this normal ?

> Either use FLIM from CVS or, better, make Gnus be before FLIM in
> load-path.

An easy way to do that is to put the following line in your
.emacs or .gnus.el file:

(push (file-name-directory (locate-library "gnus")) load-path)

The problem may be the version of FLIM containing new sha1-el.el
has not been released yet, though.
-- 
Katsumi Yamaoka <yamaoka@jpl.org>



  reply	other threads:[~2004-01-14  0:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 23:53 Xavier Maillard
2004-01-14  0:00 ` Simon Josefsson
2004-01-14  0:14   ` Katsumi Yamaoka [this message]
2004-01-14  6:42     ` Xavier Maillard
2004-01-14  6:45   ` Xavier Maillard

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=b9yhdyzpesh.fsf@jpl.org \
    --to=yamaoka@jpl.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).