Hi, On 31.05.2012 09:20, Robert Luberda wrote: > po4a or any other program that calls nsgmls fails with: > nsgmls:/etc/sgml/mutter-common.cat:8:8:E: cannot open > "/usr/share/sgml/mutter-common/catalog" (No such file or directory) > > I can see in the changelog for 3.4.1-2 that removal of > mutter-common.catalog file was intentional but > /etc/sgml/mutter-common.cat still referes to it.
Since update-catalog was responsible for installing this file into /etc/sgml, I'm wondering if it isn't also update-catalog's job to clean up the conffile once the package is removed or it stops shipping the catalog file. In case of mutter-common we removed the catalog file, so the conffile should be removed on upgrades. I've also had a look at another package shipping a catalog file: metacity-common: # apt-get install metacity-common # ls /etc/sgml/ catalog metacity-common.cat # apt-get remove metacity-common # ls /etc/sgml/ catalog metacity-common.cat # cat /etc/sgml/metacity-common.cat CATALOG /usr/share/sgml/metacity-common/catalog # ls /usr/share/sgml/metacity-common/catalog ls: cannot access /usr/share/sgml/metacity-common/catalog: No such file or directory In this case we would run into the same problem, as with mutter-common, right? So, this looks like a more general problem to me. Something which is ideally fixed in update-catalog. That's why I've CCed the sgml-base maintainers before adding any local workarounds to mutter-common. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
