Le 06/10/2010 00:48, Christopher Browne a écrit :
> A bunch of stuff is busted in the documentation right now; the root of
> it seems to be the changes in commit
> d40f0bfe8ea8fe398fc1aa89a45412a028daaa29, which restructured lots of
> stuff but, I suspect, without verification that the docs were building.
> 
> I committed some changes that rectify *some* of it; there were a lot
> more problems.  Still a ways to go with the documentation.
> 
> postgres at cbbrowne [06:31:21] [~/slony1-engine.master/doc/adminguide] [REL_2_0_STABLE *]
> -> % make html
> make: Circular HTML.index <- html dependency dropped.
> LC_ALL=C /usr/bin/perl /usr/bin/collateindex.pl -f -g -i 'bookindex' -o bookindex.sgml HTML.index
> Processing HTML.index...
> 97 entries loaded...
> 0 entries ignored...
> Done.
> openjade:slonyupgrade.sgml:51:19:E: character data is not allowed here

<para> While that approach has been found to be easier and safer,
nothing prevents one from carefully copying &slony1; components for
the new version into place to overwrite the old version as
the <quote>install</quote> step.  That might <emphasis>not</emphasis>
work on <trademark>Windows</trademark> if it locks library files that
are in use.</para> It is also important to make sure that any connections
to the database are restarted after the new binary is installed.

The </para> tag is badly placed. The text "It is also..." is not inside
a para tag. Can't work.

> openjade:slonik.sgml:2:21:E: document type does not allow element "REFENTRY" here; assuming missing "ARTICLE" start-tag

Don't know why but slonik is referenced two times in filelist.sgml. I
don't think that what causes you trouble here, but I don't see the point
of having it twice.

> openjade:slonik_ref.sgml:1:10:E: character data is not allowed here

<article> id="slonikref">

You should get rid of the > right after article, the id is part of it.

> openjade:slony.sgml:119:9:E: end tag for element "CHAPTER" which is not open

Actually, it's open. I think you got this error because of the previous one.

> openjade:monitoring.sgml:314:9:X: reference to non-existent ID "SLONWATCHDOG"
> openjade:faq.sgml:160:23:X: reference to non-existent ID "THREADPATCH"
> openjade:slonyupgrade.sgml:186:38:X: reference to non-existent ID "TRIGGERS"
> openjade:monitoring.sgml:95:54:X: reference to non-existent ID "BESTPRACTICES"
> openjade:faq.sgml:1838:53:X: reference to non-existent ID "BESTPRACTICES"
> openjade:firstdb.sgml:173:32:X: reference to non-existent ID "MKSLONCONF"
> openjade:slonik_ref.sgml:2444:13:X: reference to non-existent ID "COMPLEXFAILOVER"
> openjade:slonik.sgml:69:32:X: reference to non-existent ID "SLONIKREF"
> openjade:slonyupgrade.sgml:172:36:X: reference to non-existent ID "SLONIKCONFDUMP"
> openjade:slonyupgrade.sgml:227:36:X: reference to non-existent ID "SLONIKCONFDUMP"
> openjade:slonik_ref.sgml:337:46:X: reference to non-existent ID "PLAINPATHS"
> openjade:monitoring.sgml:313:39:X: reference to non-existent ID "LAUNCHCLUSTERS"
> openjade:faq.sgml:855:20:X: reference to non-existent ID "GENSYNC"
> openjade:firstdb.sgml:169:32:X: reference to non-existent ID "ALTPERL"
> openjade:firstdb.sgml:374:25:X: reference to non-existent ID "ALTPERL"
> openjade:addthings.sgml:69:53:X: reference to non-existent ID "ALTPERL"
> openjade:slonik_ref.sgml:2173:41:X: reference to non-existent ID "LOCKING"
> openjade:slonik_ref.sgml:2312:41:X: reference to non-existent ID "LOCKING"
> openjade:slonik_ref.sgml:2522:61:X: reference to non-existent ID "LOCKING"
> openjade:faq.sgml:1634:9:X: reference to non-existent ID "LOCKING"
> openjade:monitoring.sgml:366:60:X: reference to non-existent ID "TESTBED"
> openjade:partitioning.sgml:12:46:X: reference to non-existent ID "TESTBED"
> openjade:faq.sgml:328:41:X: reference to non-existent ID "EXTRACTSCHEMA"
> openjade:faq.sgml:1092:47:X: reference to non-existent ID "FAILOVER"
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'ALTPERL'
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'MKSLONCONF'
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'ALTPERL'
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'BESTPRACTICES'
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'LAUNCHCLUSTERS'
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'SLONWATCHDOG'
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'TESTBED'
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'TESTBED'
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'SLONIKCONFDUMP'
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'TRIGGERS'
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'SLONIKCONFDUMP'
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'PLAINPATHS'
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'COMPLEXFAILOVER'
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'EXTRACTSCHEMA'
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'GENSYNC'
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'FAILOVER'
> make: *** [html] Error 1
> postgres at cbbrowne [06:44:00] [~/slony1-engine.master/doc/adminguide] [REL_2_0_STABLE *]
> -> %

I would have built a patch if I could have a way to build the
documentation. I don't understand why the makefile tries to create a
database to build the documentation...


-- 
Guillaume
 http://www.postgresql.fr
 http://dalibo.com