From: Christophe Cuq <christophe@cuq.org>
Cc: christophe@cuq.org
Subject: Re: BBDB and EUDC/LDAP
Date: Wed, 30 Mar 2005 17:06:23 +0200 [thread overview]
Message-ID: <m28y45dvgw.fsf@le-bulb.cuq.org> (raw)
In-Reply-To: <v9br91mdcq.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <reinersteib+from-uce@imap.cc> writes:
> No, the generation of gnus-faq.texi is new. I think what happened is
> that the timestamp of xml2texi.sh and/or xml2texi.scm was newer than
> gnus-faq.texi. As gnus-faq.texi is distributed with Gnus CVS and
> tarballs, fetching the FAQ from sourceforge shouldn't happen unless
> you use "make gnus-faq-full-update".
I had a problem this morning, not with a timeout, but with the
password to connect to cvs (on freshly cvs retrieved gnus) :
,----
| cd texi && make EMACS="emacs" all
| cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/gnus \
| co -p gnus-faq/src/gnus-faq.xml > gnus-faq.xml.tmp
| cvs checkout: cannot find password
| cvs [checkout aborted]: use "cvs login" to log in first
| make[1]: *** [gnus-faq.xml] Error 1
| make: *** [info] Error 2
`----
And I am unable to understand what to do to correct it.
Does your patch correct that problem ?
--
CHC
next prev parent reply other threads:[~2005-03-30 15:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 14:48 Sébastien Kirche
2005-03-29 14:59 ` David S. Goldberg
2005-03-29 15:17 ` Sébastien Kirche
2005-03-29 15:54 ` Reiner Steib
2005-03-29 18:28 ` Sébastien Kirche
2005-03-29 18:50 ` Reiner Steib
2005-03-30 9:16 ` Sébastien Kirche
2005-03-30 12:07 ` Reiner Steib
2005-03-30 13:00 ` Sébastien Kirche
2005-03-30 14:12 ` Reiner Steib
2005-03-30 14:48 ` Sébastien Kirche
2005-03-30 15:41 ` Reiner Steib
2005-03-30 16:06 ` Christophe Cuq
2005-03-30 16:22 ` Christophe Cuq
2005-03-30 15:06 ` Christophe Cuq [this message]
2005-03-30 15:36 ` Reiner Steib
2005-03-30 16:06 ` Christophe Cuq
2005-06-08 23:42 ` Sébastien Kirche
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=m28y45dvgw.fsf@le-bulb.cuq.org \
--to=christophe@cuq.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).