Hi fellow devs, after examining bug #206753 with Ford_Prefect and remi last week it seems we broke upgrade path from sk to rarian. * If you did the upgrade, you have an entry in /etc/xml/catalog that tells xsltproc and other xml tools they can find the dtd locally when it has actually been uninstalled during the upgrade. * If you didn't ever install sk-0.3.14 then you are _always_ relying on web access to build applications using the omf format for their doc. This is really bad since not so long ago (about 2 months) sourceforge was kind of down blocking any attempts to build software using omf. So I made Ford_Prefect work out this ebuild that I propose by added as a dep to rarian and sk-9999 (and it's only a dtd that used to be stable after all). I'd also like to know your opinion on commiting this to the tree directly stable for release's sake. This should solve bug #206753, but it seems bug #229077 could be a duplicate.
Created attachment 158153 [details] scrollkeeper-dtd-1.0.ebuild there you go.
If it does fix the xml parser bugs, then I vote for fast tracking it. After all, it only installs one silly file :)
ok, after more fighting with the checks of gnome-desktop, Ford_Prefect indicated to me that it still wasn't using the locally available dtds. This is because of the way xmllint was called by specifying the dtd inline which for some reason means it tries to find a _system_ dtd corresponding to that URL. I'll commit a fixed ebuild based on the one attached here with the extra fix needed for proper uninstallation as well (forgotten echo). This is going straight to stable to match sk-9999 visibility, I'll also do a r1 of sk-9999 just to make sure everyone gets the updated dep and finally stop stressing the sourceforge mirrors, slowing down build times, ... @release, you probably want to update your snapshots with those 2 new ebuilds to make sure new install can build without network access.
ok, manipulation done. I'll leave it up to releng for the rest of the story, feel free to poke me if my explanations aren't clear enough.
nearly one year has passed. Closing since there is obviously nothing happening for release anymore.
