From: Reiner Steib <reinersteib+from-uce@imap.cc>
Subject: Re: BBDB and EUDC/LDAP
Date: Wed, 30 Mar 2005 16:12:53 +0200 [thread overview]
Message-ID: <v9br91mdcq.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m2is39l25j.fsf@seki.fr>
On Wed, Mar 30 2005, Sébastien Kirche wrote:
> Le 30 Mar 2005, Reiner Steib a formulé :
>
>> > It just failed to fetch the faq as direct cvs access does not function
>> > from my company network.
>>
>> Oops. This should not happen. I will see how I can fix that.
>
> I though it was known...
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".
> BTW it failed twice (same reason - cvs checkout time-out):
> - at end of the configure script
> - with make install when copying the files
Could you try the following patch (you must re-run configure
afterwards) and report back?
--8<---------------cut here---------------start------------->8---
--- Makefile.in 30 Mar 2005 12:33:27 -0000 6.29.2.6
+++ Makefile.in 30 Mar 2005 14:07:20 -0000
@@ -84,7 +84,7 @@
fi
mv $(REFCARD).pdf $@
-gnus-faq-full-update: gnus-faq-clean gnus-faq.texi
+gnus-faq-full-update: gnus-faq-clean gnus-faq-texi
gnus-faq.xml:
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/gnus \
@@ -93,7 +93,7 @@
{ echo "Update of $@ failed."; : rm $@.tmp; exit 1; }
mv $@.tmp $@
-gnus-faq.texi: gnus-faq.xml xml2texi.sh xml2texi.scm
+gnus-faq-texi: gnus-faq.xml xml2texi.sh xml2texi.scm
./xml2texi.sh $< $@.tmp
@echo
# FIXME: This should be done in xml2texi.scm or gnus-faq.xml should be
--8<---------------cut here---------------end--------------->8---
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2005-03-30 14:12 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 [this message]
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
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=v9br91mdcq.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+from-uce@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).