Ryan Attard writes:
> I've been struggling with this bug, but I'm a little confused by this
> bug report and the response from the maintainers.
Thank you for asking to clarify. I agree that this bug report discussion
can be difficult to follow.
> The source package has these JS files under in c
Sorry, my previous response was a little unclear:
> Can't you just drop the libjs* recommends and install the stuff in the source
package onto the target system?
My response was definitely more aimed at the python-coverage maintainers
than the libjs-jquery-hotkeys maintainers. Why doesn't python-c
I've been struggling with this bug, but I'm a little confused by this bug
report and the response from the maintainers.
The source package has these JS files under in coverage/htmlfiles (with
what I'm assuming is the compatible/tested version), why aren't they
shipped in the debian package?
It ma
I did some further testing around changing the version of jquery.hotkeys.js
in libjs-jquery-hotkeys to the upstream jeresig version, and behavior of
the various libraries that depend on it.
For python-coverage, the bug is still there, with the addition of a new
error related to differences in unlo
On 23-May-2017, Eevel Weezel wrote:
> I'm attaching a patch. This will remove the bundled version of the js
> libraries, allowing python-coverage to use the system libraries.
Thank you for the patch. Is that needed, though? The package already
omits those files from the HTML report, via an exist
Hello Maintainer,
I'm attaching a patch. This will remove the bundled version of the js
libraries, allowing python-coverage to use the system libraries.
Best,
Heather
python-coverage_diff
Description: Binary data
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.or
