Am Montag, den 11.06.2007, 17:34 -0400 schrieb Daniel Schepler: > On Monday 11 June 2007 08:18:48 am Daniel Leidert wrote:
[..] > > 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? > > Just in case my last mail was blocked for being too big, Nope :) There is no relevant limitation. > 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. Well, for me it seems, that this tarball is used for a complete rebuild of the archive. An `apt-cache policy docbook2x' shows me, that the installation candidate is not the official one. Is the docbook2x version, that gets installed, from the Debian archive (reading the build log, I guess yes; but checking the tarball, it seems the answer is no)? If not, can you send me the binary package of docbook2x, that gets installed (to check for differences with the official package). Can you further check, that the slony.xml starts with "0x3C 0x3F 0x78 0x6D" (hexedit or similar). That's the condition, that should hit in /usr/share/perl5/XML/SAX/PurePerl/EncodingDetect.pm. The copy you sent is ok. But maybe it's changed/"fixed" during mail transport (I'm no expert for the question, if this is possible). I checked your log and mine without a result. The only difference is, that I already have fakeroot in the pbuilder chroot and doesn't need to install it. But that cannot be the reason for this issue. The slony.xml are the same. The Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
