Description of problem: The file /etc/sgml/sgml-docbook-4.1.cat is incorrect Version-Release number of selected component (if applicable): 1.0.57 How reproducible: Each time Steps to Reproduce: 1. Try to build a doc with a 4.1 SGML Docbook ref 2. fail. 3. Typically the mondo HOWTO in HTML made from the original DocBook content Iy seems that it's much better when you add to the /etc/sgml/sgml-docbook-4.1.cat file ref to the missing catalog: bruno > cat ~/sgml-docbook-4.1.cat CATALOG "/usr/share/sgml/openjade-1.3.3/catalog" CATALOG "/usr/share/sgml/openjade/catalog" CATALOG "/usr/share/sgml/docbook/dsssl-stylesheets/catalog" CATALOG "/usr/share/sgml/docbook/sgml-dtd-4.1/catalog" CATALOG "/usr/share/sgml/sgml-iso-entities-8879.1986/catalog" Is one is working much better, at least from a DocBook perspective (I now have texlive issues, but that's for another report maybe ;-) I tried to look at the spec, but it's far from obvious where this catalogs are genertaed, and why this content is missing, whereas it is in the 4.3 SGML version.
@ Bruno Sorry for responding so late. Your report passed the first test of not being a duplicate. The second test is reproducing the bug, we are waiting for someone familiar with DocBook to do that
CC: (none) => marja11
@ Jani Can you help with this, please? I don't know DocBook at all.
CC: (none) => jani.valimaa
Sorry, me neither. I can see I've made one commit to this pkg, but it was just a dep version bump to fix pkg install, IIRC.
@ wobo Can you help with this bug?
CC: (none) => molch.b
CC: jani.valimaa => (none)
CC: (none) => remco
I'm not familiar with docbook at all, or clear on what is missing from the catalog, but looking at the rpm, the /etc/sgml/$fmt-docbook-$ver.cat files are generated by the postinstall scriptlet. See the output of rpm -q --scripts docbook-dtds
CC: (none) => davidwhodgins
@ Bruno, Can you show me the content of your /etc/sgml/sgml-docbook-4.1.cat file in your install? Mine appears to be the same as what you have listed in your bugreport and which I understand to be working. Also, given our unfamiliarity with this, can you give an example command that illustrates the problem to us? Thanks!
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
No reply to the question in comment 6 from over half a year ago. Closing as OLD
Status: NEW => RESOLVEDResolution: (none) => OLD