FS#3758 - docbook-xml xml catalog gets lost on upgrades
Attached to Project:
Arch Linux
Opened by Jan de Groot (JGC) - Friday, 13 January 2006, 08:12 GMT
Last edited by Jan de Groot (JGC) - Saturday, 02 June 2007, 11:40 GMT
Opened by Jan de Groot (JGC) - Friday, 13 January 2006, 08:12 GMT
Last edited by Jan de Groot (JGC) - Saturday, 02 June 2007, 11:40 GMT
|
Details
The docbook-xml package includes /etc/xml/catalog, which is
a file that gets edited by many packages (gtk-doc,
scrollkeeper, gnome-doc-utils, libglade, etc). Upgrading
docbook-xml would remove all these things from the catalog,
which means scrollkeeper documentation installations will
take ages, several applications fail to work, etc.
When updating this package, please generate the /etc/xml/catalog in postinstall if it doesn't exist, but make sure it's not included in the filelist anymore. I don't think there's a solution for this problem in this state: whenever you upgrade docbook-xml, the catalog is gone, whatever the new package will say. When upgrading docbook-xml, please also increase the pkgrel number for packages that install these things in /etc/xml/catalog (scrollkeeper and libglade are two examples I know of) |
This task depends upon
Closed by Jan de Groot (JGC)
Saturday, 02 June 2007, 11:40 GMT
Reason for closing: Fixed
Additional comments about closing: Finally, after all these years, after lots of irritation, after losing faith in this one ever getting fixed... I fixed it on linuxtag 2007 :)
Saturday, 02 June 2007, 11:40 GMT
Reason for closing: Fixed
Additional comments about closing: Finally, after all these years, after lots of irritation, after losing faith in this one ever getting fixed... I fixed it on linuxtag 2007 :)
i know not much about catalogs, but i managed to package to arch (uglily) some debian packages including:
sgml-base sgml-data xml-core docbook
i also noticed that docbook-xml & docbook-xsl includes far less files than their debian equivalents
i dropped a mail to the docbook-xml package maintainer but got no answer :/
As pacman uses pre_upgrade from the new package when upgrading, preserving the XML catalog isn't a big problem anymore. I'll dive into this somewhere next week.
I looked a bit closer at your suggested changes, I think it will get included somewhere this week. The catalog preserving can be done from pre_upgrade, where a check is made for the older package, we could move the catalog out of the way in pre_upgrade, extract the new package and move the file back on post_upgrade.