Hi,
On Sat, Mar 22, 2014 at 12:56 PM, Ben Finney <ben+deb...@benfinney.id.au>wrote: > > Isn't the problem best fixed by reverting the 'libjs-jquery-hotkeys' > package to the working "0.8" version? The newer version breaks dependent > packages, so the right place to apply pressure it seems to me is by > rejecting that newer code from Debian until it works again. > > > I'm not sure what the best solution is. I've identified the last revision > > of that package that worked well with coverage.py. One option is to > > revert the debian package, but presumably those changes were made for a > > reason, and I'd hate to break other projects. Another option is to use > > the vendorised libraries in upstart coverage.py. > > Sure. It's easy for me to identify the location for a solution in a package > which I'm not really involved with, so my position is not the only one to > consider. > > > Please let me know if I can do anything to help out. > > Have you got any feedback from the Debian package maintainer of > 'libjs-jquery-hotkeys' to find out whether rolling back to version "0.8" is > feasible? > > As far as I can tell, the maintainer is listed as ' pkg-javascript-de...@lists.alioth.debian.org', and I assume they're getting these bug emails, but I've not had any response yet. > Have you worked with that package maintainer to report the bug upstream (it > is the package maintainer's responsibility)? Has the upstream developer > > You cut out here, but I get the gist. There's a few complications. As far as I can make out, the problem was not introduced upstream, but rather in Debian's version of the library. The upstream code ( https://github.com/tzuryby/jquery.hotkeys) does not contain the problematic code. WRT reverting the changes made to the library, that solution would suit me fine, but I have no idea whether this will break other people (not being a JS developer, this is kind of hard for me to determine). Cheers, -- Thomi Richards thomi.richa...@canonical.com
