[xml/sgml-pkgs] Bug#507070: Bug#507070: scrollkeeper: I/O error : Attempt to load network entity

[Daniel Leidert]

Am Freitag, den 28.11.2008, 13:21 +0100 schrieb Josselin Mouette:
> Le vendredi 28 novembre 2008 à 13:00 +0100, Daniel Leidert a écrit :
> > 2) Why do you think, this is an xml-core problem? Can you show the
> > corrupt catalog?
> 
> I’m almost sure this comes from the catalog, since the error is about a
> DTD not found.

But an online DTD. This just means, that the location is not rewritten
to the local DTD source and there is probably a problem accessing the
network/internet. That's why I think, scrollkeeper is maybe called
before docbook-xml setup is finished (the prerm script removes the
registered entities and the postinst script registers them).

> The docbook DTD is found in the docbook-xml which
> registers it the system-wide catalog, so it should be available when
> scrollkeeper runs. However I didn’t think that the catalog could not be
> up-to-date at the time scrollkeeper runs, as you explained:
> 
> > I wonder, if scrollkeeper needs to pre-depend on docbook-xml when it
> > tries to access an online-system-ID rewritten to a local location by
> > docbook-xml. What I can imagine is, that scrollkeeper tries to load the
> > entity, before the installation of docbook-xml is completed - means:
> > before the entity is registered (again). And if the system hasn't any
> > online access, this will fail of course.
> 
> Indeed, this may be caused by the fact that many packages don’t depend
> on scrollkeeper, yet register their documents with it in the postinst,
> only checking that /usr/bin/scrollkeeper-update exists.

Yeah. This might be a real problem. I'm currently working on the
XML/SGML core design, because it causes a few (serious) issues. However,
I don't think my design changes will partially solve this problem. I
plan to change to not longer register and remove all entities during a
package update. Instead the catalogs should be added to the system
catalog (nextCatalog tag), so this can also be triggered. This means,
that entities are available all the time. So if a package update removes
an entity, then another package depending on it might run into a missing
entity. But that's a problem of dependencies I hope.

> Ross, could you look through your dpkg.log and find whether docbook-xml
> or xml-core was updated in the same run as the one where you hit the
> issue? That would explain the problem without incriminating xml-core at
> all.

They were both updated (I'm the maintainer for both and uploaded them in
the same run).

Regards, Daniel