Red Hat Bugzilla – Bug 440052
Demos don't work
Last modified: 2009-02-19 10:05:50 EST
Description of problem:
The MochiKit demos in /usr/share/doc/MochiKit-1.3.1/examples don't work.
MochiKit.js isn't found, because the demos refer to it using the relative
path "../../lib/MochiKit/MochiKit.js". However, there is
Either a copy of (or a symlink to) MochiKit.js should be placed at that path,
or the demos be modified to
reference "../../../../../share/MochiKit/MochiKit.js", i.e. the copy
Version-Release number of selected component (if applicable):
Steps to Reproduce:
A static table.
A sortable table.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Sorry for the delay, apparently MochiKit had been orphaned as a package. I picked it up this morning, there is a new release so I will be focusing on packaging that in order to get it pushed to updates and hopefully this will fix the bug, if not I will go from there in trying to track down the issue.
Bug fixed, koji build complete. Awaiting testing in bodhi.
Hopefully will push to stable soon.
In order for the examples to work, you must copy the code directory for the specific example into a web publishable directory because the MochiKit code is referenced by its relative web location (which is the fix that was made, before it was a hard coded location that mirrored the directory structure of the source distribution of the upstream project).
(In reply to comment #5)
> In order for the examples to work, you must copy the code directory for the
> specific example into a web publishable directory because the MochiKit code is
> referenced by its relative web location (which is the fix that was made, before
> it was a hard coded location that mirrored the directory structure of the
> source distribution of the upstream project).
Hm. What I wanted was to browse file:/usr/share/doc/MochiKit-*/examples, with working examples. For this to work, the example files should use a relative path to MochiKit.
Or, even better, you could put them into a web-accessible location, most likely in a sub package. See httpd-manual for an example.
The bug has been fixed and has been pushed out through Bodhi, there is apparently a ticket in to infrastructure about the fact that updates are not automatically closing bugs.
Marking bug as closed, relevant update links: