Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 44354 invoked by uid 500); 11 Dec 2002 14:17:05 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 44333 invoked from network); 11 Dec 2002 14:17:04 -0000 Received: from fep02.tuttopmi.it (HELO fep02-svc.flexmail.it) (212.131.248.101) by daedalus.apache.org with SMTP; 11 Dec 2002 14:17:04 -0000 Received: from apache.org ([80.204.154.181]) by fep02-svc.flexmail.it (InterMail vM.5.01.05.09 201-253-122-126-109-20020611) with ESMTP id <20021211141658.VUOU17436.fep02-svc.flexmail.it@apache.org>; Wed, 11 Dec 2002 15:16:58 +0100 Message-ID: <3DF74885.4050503@apache.org> Date: Wed, 11 Dec 2002 15:15:33 +0100 From: Nicola Ken Barozzi Reply-To: nicolaken@apache.org Organization: Apache Software Foundation User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126 X-Accept-Language: en-us, en MIME-Version: 1.0 To: fop-dev@xml.apache.org CC: forrest-dev@xml.apache.org Subject: Re: src/documentation/README References: <1039598916.14477.961.camel@fztig938.bank.dresdner.net> In-Reply-To: <1039598916.14477.961.camel@fztig938.bank.dresdner.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Keiron Liddle wrote: > On Tue, 2002-12-10 at 19:17, Victor Mote wrote: > >>OK, I see now that I misunderstood your "Sorry, yes" answer to Keiron. If >>http://forrestbot.cocoondev.org/site/xml-fop should be reflecting changes no >>more than an hour old made to xml-fop/src/documentation, then it is not >>working. I just looked for changes that were made about 24 hours ago, and >>they are not there. Also, as I mentioned, it shows a publish date of 12-7. >>So I suspect that something is not working. We have one document with a >>non-standard DTD (my fault, in fact that is what I am trying to work on) >>that might be messing up the flow. How do I go about troubleshooting this? > > > Judging by the log it might be a DISPLAY problem. > > The compliance doc should only cause a broken link. > > Who is in charge of the cocoondev site, could they work out what the > problem is? forwarding to forrest. Here is the relevant part of the last log: [java] Exception in thread "main" java.lang.InternalError: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable. -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) ---------------------------------------------------------------------