i just upgraded all of these app-text ebuilds docbook-sgml-dtd-4.0-r1 docbook-sgml-dtd-3.0-r1 docbook-xsl-stylesheets-1.57.0 docbook-sgml-dtd-4.1-r1 docbook-dsssl-stylesheets-1.77-r1 docbook-sgml-dtd-3.1-r1 html401-19991224-r1 xhtml1-20020801-r1 gentoo-guide-xml-dtd-2.1-r1 sgml-common-0.6.3-r3 openjade-1.3.1-r6 i noticed way too late that the entries in /etc/sgml/catalog got removed after the old packages were removed this is a serious problem. i am not sure how to fix this
They were removed on purpose; maybe I misunderstood the upgrading process. All catalog *should* be removed on package removal, which is why the revisions were all bumped -- so that the new system of removal gets included. Anyway, the process is as such: pkg_prerm removes pkg_postinst installs As near as I could tell, when I tested the ugprade process on this system, they were all installed at the end. When the upgrade is completed, do you still have an empty /etc/sgml/catalog? If so, try by re-emerging the packages in question. I posted a message to -dev and -user about this upgrade and received no responses.
Ha! I tested it again, and yeah, I must have been doing something wrong before. Well, a re-emerge will solve the problem for now, I'll post a message, but there has to be a solution using various portage solutions.
New behavior for sgml-catalog.eclass is to completely refrain from removing catalog files if they still exist. This should cover upgrades, in lieu of a more permanent solution, which carpaski may be working on... I will close if no comments in two days.
Ok, I'll close it a day early.
