I don't think that the patch is correct.
The url attribute in the identifier element should not point to the omf file
itself. It should rather point to the correct documentation file to be used by
scrollkeeper-conforming help browsers.
I'm not sure which file this is, but I think it should be
** Changed in: update-manager (Ubuntu)
Status: Fix Committed = Fix Released
--
scrollkeeper-update -v error
https://launchpad.net/bugs/45548
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for your bugreport and your patch. This will be fixed with the
next update-manager upload to edgy.
** Changed in: update-manager (Ubuntu)
Status: Confirmed = Fix Committed
--
scrollkeeper-update -v error
https://launchpad.net/bugs/45548
--
ubuntu-bugs mailing list
Mila: what did you change? If it's a problem in /usr/share/omf/update-
manager/update-manager-C.omf, it's an update-manager bug.
--
scrollkeeper-update -v error
https://launchpad.net/bugs/45548
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have actually the same problem with dapper drake final upgraded from
flights...
scrollkeeper-rebuilddb doesn't help.
The problem is reproducible. just as easy as running scrollkeeper-
update.
--
scrollkeeper-update -v error
https://launchpad.net/bugs/45548
--
ubuntu-bugs mailing list
After editing /usr/share/omf/update-manager/update-manager-C.omf the
problem disappeared. probably libxml2 bug
--
scrollkeeper-update -v error
https://launchpad.net/bugs/45548
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
