Le 16/03/2015 00:39, Fernando de Oliveira a écrit :
On 15-03-2015 20:20, Bruce Dubbs wrote:
Fernando de Oliveira wrote:
http://www.linuxfromscratch.org/blfs/view/svn/postlfs/cacerts.html

We have

URL=/certdata.txt &&

Should be probably:

URL=http://anduin.linuxfromscratch.org/sources/other/certdata.txt &&
That what I have now.  Do you have a problem with your local build?

   -- Bruce

Probably:

-rw-rw-r-- 1 fernando fernando 16793 Mar 15 20:30
/home/fernando/public_html/blfs-book-xsl/postlfs/cacerts.html

$ grep URL= /home/fernando/public_html/blfs-book-xsl/postlfs/cacerts.html
<kbd class="command">URL=/certdata.txt &amp;&amp;

$ grep URL= ./postlfs/security/cacerts.xml
    <screen><userinput>URL=&sources-anduin-other-http;/certdata.txt
&amp;&amp;

Hi Fernando,

It looks like it is a problem with the rendering of the book. Maybe the same as
http://lists.linuxfromscratch.org/pipermail/blfs-dev/2014-October/028784.html
To check that, I have a small script:
----
cat > testcase.xml << EOF
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE somedoc [
<!ENTITY a "something">
<!ENTITY b "&a;">
]>

<somedoc>

<somebeacon someattribute="&b;"/>
&a; should appear after colon: &a;
&b; should appear after colon: &a;
&a; should appear after colon: &b;
&b; should appear after colon: &b;
</somedoc>

EOF

xmllint --noent testcase.xml
-----

The right output is:
---------
<!DOCTYPE somedoc [
<!ENTITY a "something">
<!ENTITY b "&a;">
]>
<somedoc>

<somebeacon someattribute="something"/>

something should appear after colon: something
something should appear after colon: something
something should appear after colon: something
something should appear after colon: something

</somedoc>
--------

I know that Debian only corrected the bug (in sid) in January, so if you are 
using Mint, it may be buggy as well.
Solution: downgrade to libxml2-2.9.1 (but this introduces security problems) or 
rebuild 2.9.2 it with the book patch.

Pierre

--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to