Included replies to Bruce and Ken.
Em 15-07-2015 11:03, Ken Moffat escreveu:
On Tue, Jul 14, 2015 at 08:52:27PM -0500, Bruce Dubbs wrote:
Fernando de Oliveira wrote:
index.xml:125: element sect2: validity error : Element sect2 content
does not follow the DTD, expecting (sect2info? , (title , subtitle? ,
titleabbrev?) , (toc | lot | index | glossary | bibliography)* ,
(((calloutlist | glosslist | bibliolist | itemizedlist | orderedlist |
segmentedlist | simplelist | variablelist | caution | important | note |
tip | warning | literallayout | programlisting | programlistingco |
screen | screenco | screenshot | synopsis | cmdsynopsis | funcsynopsis |
classsynopsis | fieldsynopsis | constructorsynopsis | destructorsynopsis
| methodsynopsis | formalpara | para | simpara | address | blockquote |
graphic | graphicco | mediaobject | mediaobjectco | informalequation |
informalexample | informalfigure | informaltable | equation | example |
figure | table | msgset | procedure | sidebar | qandaset | task | anchor
| bridgehead | remark | highlights | abstract | authorblurb | epigraph |
indexterm | beginpage)+ , (refentry* | sect3* | simplesect*)) |
refentry+ | sect3+ | simplesect+) , (toc | lot | index | glossary |
bibliography)*), got (title segmentedlist variablelist varlistentry )
I've been there a lot of times.
Yeah, me too, but it was only one page.
This morning, I remembered to just comment out the pages in a process
similar to bisecting, and quicly discovered the fault. Your reformat and
coment below helped a lot, decreasing even more the time needed for that.
Thanks a lot.
Let me reformat for you:
index.xml:125: element sect2: validity error :
Element sect2 content does not follow the DTD,
expecting
(sect2info? , (title , subtitle? , titleabbrev?) ,
(toc | lot | index | glossary | bibliography)* ,
(
(
(
calloutlist | glosslist | bibliolist | itemizedlist | orderedlist |
segmentedlist | simplelist | variablelist | caution | important |
note | tip | warning | literallayout | programlisting |
programlistingco | screen | screenco | screenshot | synopsis |
cmdsynopsis | funcsynopsis | classsynopsis | fieldsynopsis |
constructorsynopsis | destructorsynopsis | methodsynopsis |
formalpara | para | simpara | address | blockquote | graphic |
graphicco | mediaobject | mediaobjectco | informalequation |
informalexample | informalfigure | informaltable | equation |
example | figure | table | msgset | procedure | sidebar | qandaset
| task | anchor | bridgehead | remark | highlights | abstract |
authorblurb | epigraph | indexterm | beginpage
)+ ,
(refentry* | sect3* | simplesect*)
) | refentry+ | sect3+ | simplesect+
) ,
(toc | lot | index | glossary | bibliography)*
),
got (title segmentedlist variablelist varlistentry )
----------
The varlistentry is out of place in the sect2. It's likely a misplaced
</variablelist> tag.
-- Bruce
The error messages for new pages are usually very hard to parse,
beyond "something went wrong". I've often spent several hours
sorting out a new page (these sort of problems seem to arise when
I'm already tired). For a _new_ page, I now usually copy an
existing page, perhaps remove or comment parts of it, and then
concentrate on getting the indexing to validate (i.e. unique names).
Yeah, this always tricks me, last thing to do, always trying to quicly,
already tired...
After that, I make several passes through it, changing dependencies
and text, adding sections and generally fixing things up. For an
existing page, 'svn diff' usually helps me spot the errors if I
cannot immediately see them. But for a new page I would now do what
I did the last time I changed the perl modules page: at suitable
times (when it validates), copy it to a new backup. Then, a diff
against the backup will show what I have changed since the backup,
and the error must be in those changes.
Next time, I will do more backups, following your tip.
Wash, rinse, repeat until satisfied.
Clever people can probably add a new page in one go, whilst doing a
couple of other things at the same time. Me, I'm a "bear of little
brain"¹ so I have to develop workflows which make things easier for
me, and then I have to remember to use them ;)
ĸen
[1.] Winnie-the-Pooh : kids' books by A.A. Milne
LOL. I wish I had your good humour, when things are getting me down.
Thanks a lot.
Now, I have finally finished. Will commit as soon as Bruce replies to
this, because the diff is larger than our limit, and he needs probably
to unblock it:
160K ../lxqt-2015.07.15-08h01m26s.diff
BTW, I think that is the BRT time when I succeeded first validation.
Then needed to fix some mistakes, polish, include pre and post install.
The instructions should work, but others testing is the best an editor
can dream, to fix the probable mistakes.
Part of the text is borrowed from our LXDE pages, part from KF5.
The URLS are the ugly ones in fedora, due to a recent move of lxde.org,
and I hope to fix as soon as possible. If someone gives me the URL for a
better repository, I'll much appreciate.
English and format are most probably very poor, particularly I couldn't
find how to write the explanations for the sed commands.
One extra package, libstatgrab-0.91, was necessary, and will go with the
the commit, and as soon as I send this message, I will open a ticket for it.
There is one package included that is already deprecated, replaced by
"solid", from KF5, but I think it is for the next LXQt release.
I am in debt with Igor Živković, who first draw my attention to LXQt,
last year, I think.
Of course, this is like the first draft. We will see if it is worth to
keep it in the BLFS, or continue using LXDE, but this should be better
decided in a couple of days to a fortnight.
I have included only the DE, not applications, although it is arguable
that some of the packages should be better placed as applications. If
someone wants, please create a new directory for apllications and move
them, or please, tell me to do it.
Two applications, which are normally bundled with LXQt are qterminal and
qupzilla.
I am willing to include them to the missing Applications section for
LXQt, or inviting somebody to do it, whatever, but think that was not
discussed before, and we (\me and who else is interested) need some input.
I can't remember if Laura or Emanuele or somebody else make intense use
of Qt, and it would be much appreciated opinions/corrections/ideas.
I think there was something else I wanted to report, but forgot.
It is a too big job for my experience, so, apologies for my humour
fluctuations these last days of despair/joy.
Bruce, can I commit the 160 K update/task?
--
[]s,
Fernando
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
