xmlto required?

[Matthias Andree]

Clint Adams <schizo at debian.org> writes:

>> Seriously, we currently need xmlto (www.cyberelk.net AFAIR) to reformat
>> from DocBook XML to man format. Again, this is only visible to the
>> maintainer/developer, not to the end user. You'll have to install xmlto
>> and docbook 4.1 XML if you want to compile from CVS. We may need to
>> document this.
>
> Well, in theory one could use docbook-to-man or similar tools.

xmlto is just that. docbook-to-something. something can be man, dvi,
pdf, html and some other related flavours.

-- 
Matthias Andree


Return-Path: <>
Delivered-To: relson at osagesoftware.com
Received: from gluck.debian.org (gluck.debian.org [192.25.206.10])
	by osagesoftware.com (Postfix) with ESMTP id 621D32838C
	for <relson at osagesoftware.com>; Tue, 28 Jan 2003 19:33:22 -0500 (EST)
Received: from mail by gluck.debian.org with local (Exim 3.35 1 (Debian))
	id 18dgAL-0002hW-00; Tue, 28 Jan 2003 17:33:21 -0700
X-Failed-Recipients: schizo at debian.com
From: Mail Delivery System <Mailer-Daemon at gluck.debian.org>
To: relson at osagesoftware.com
Subject: Mail delivery failed: returning message to sender
Message-Id: <E18dgAL-0002hW-00 at gluck.debian.org>
Date: Tue, 28 Jan 2003 17:33:21 -0700
X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.10.2.tst.20030210

This message was created automatically by mail delivery software (Exim).

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  schizo at debian.com
    unknown local-part "schizo" in domain "debian.com"

------ This is a copy of the message, including all the headers. ------

Return-path: <relson at osagesoftware.com>
Received: from osagesoftware.com [216.144.204.42] 
	by gluck.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 18dgAL-0002hC-00; Tue, 28 Jan 2003 17:33:21 -0700
Received: from maple.osagesoftware.com (maple.osagesoftware.com [192.168.1.20])
	by osagesoftware.com (Postfix) with ESMTP id 2F5852838C
	for <schizo at debian.com>; Tue, 28 Jan 2003 19:33:14 -0500 (EST)
Message-Id: <4.3.2.7.2.20030128193045.02b43870 at mail.osagesoftware.com>
X-Sender: relson at mail.osagesoftware.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 28 Jan 2003 19:33:09 -0500
To: Clint Adams <schizo at debian.com>
From: David Relson <relson at osagesoftware.com>
Subject: Re: t.lock2 test failures
In-Reply-To: <20030128235617.GA14007 at dman.com>
References: <4.3.2.7.2.20030128175518.00de7a10 at mail.osagesoftware.com>
 <4.3.2.7.2.20030128175518.00de7a10 at mail.osagesoftware.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 06:56 PM 1/28/03, Clint Adams wrote:

> > The arm architecture was one where test t.lock2 failed.  Go into the
> > bogofilter-0.10.1.2/test directories (whatever it's named) and run the
> > following commands:
>
>Once again, the problem on arm magically disappears.  But I've got more
>problems for you.

t.lock2 is a non-deterministic test.  It runs multiple (10) copies of 
bogofilter - at one time - to see if locking works or fails.  Unfortunately 
system load, the scheduler, and other factors prevent consecutive runs 
being identical to one another.  However, it _is_ an indicator of how well 
database locking works.