On Monday 11 June 2007 08:18:48 am Daniel Leidert wrote:
> Am Sonntag, den 10.06.2007, 14:17 -0400 schrieb Daniel Schepler:
> > Here's the output of `docbook2x-man --debug slony.xml' from
> > doc/adminguide, in case it gives any clue what's going wrong:
> > ...
> > frobnitz:/tmp/buildd/slony1-1.2.9/doc/adminguide# docbook2x-man --debug
> > slony.xml /usr/bin/xsltproc --nonet --debug
> > http://docbook2x.sourceforge.net/latest/xslt/man/docbook.xsl slony.xml
> > docbook2man://[EMAIL PROTECTED]'missingoids']: Erroneous request for title
> > for this element docbook2man://[EMAIL PROTECTED]'missingoids']: Erroneous
> > request for title for this element
>
> These messages are not the reason, that it fails. So the bug report
> title is not well chosen :)
>
> > Unable to recognise encoding of this document at
> > /usr/share/perl5/XML/SAX/PurePerl/EncodingDetect.pm line 96. Document
> > requires an element [Ln: 1, Col: 0]
>
> Can you please attach the slony.xml from your package build? You can
> also send it via PM. The issue seems to be related to docbook2x, which I
> care about. But the issue you report should have been fixed some time
> ago. So I'm wondering, why you still observe it.
>
> > I don't know enough about Docbook/XML stuff to know if #405186 might be
> > affecting this.  But given that libxml-sax-expat-perl was also installed,
> > I wonder why it was using the pure Perl version instead...
>
> I cannot reproduce the issue you describe - even not in a i386 pbuilder.
> On which architecture are you working? Can you post/attach the complete
> pbuilder build log, so I can compare it to mine?
>
> Regards, Daniel

Just in case my last mail was blocked for being too big, I put up 
slony1-build-log, slony.xml, and slony.xsltprocd (the output of 
docbook2x-man --nonet http://.../docbook.xsl slony.xml) at 
http://people.debian.org/~schepler/ .  I also put up my pbuilder base.tgz in 
case having the exact same one I used to reproduce the problem will help you 
reproduce it as well.
-- 
Daniel Schepler



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to