On Thu, 13 Sep 2012, Flavio Bello Fialho wrote:
> I imagine that mediawiki 1:1.19.1-1 is
> incompatible with libjs-jquery-tablesorter 6-1, although one depends on the
> other. I suggest removing the dependency and using the upstream mediawiki file
> instead of the symlink.
That would violate Poli
>> I imagine that mediawiki 1:1.19.1-1 is
>> incompatible with libjs-jquery-tablesorter 6-1, although one depends
on the
>> other. I suggest removing the dependency and using the upstream
mediawiki file
>> instead of the symlink.
>
> That would violate Policy. Which version of libjs-jquery-tabl
On Thu, 13 Sep 2012, Flavio Bello Fialho wrote:
> Based on the file header, it seems mediawiki uses a fork of tablesorter or is
> a modified version of it, specifically for use with mediawiki.
I see. In this case, the Policy part I had in mind does
not apply, and it’s correct to use the version s
___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Hi!
On Tue, Sep 11, 2012 at 10:53 PM, Marcelo Jorge Vieira wrote:
> Hi Per Andersson,
>
> On Tue, 2012-09-11 at 13:25 +, nore...@alioth.debian.org wrote:
>> Per Andersson (avtobiff-guest) has requested to join your project.
>> You can approve this request here:
>> https://alioth.debian.org/p
Hi!
I have been packaging the mezzanine cms [0] the last week. It
includes some javascript, which, of course, led me down the path
of packaging some javascript. (And also repackaging.)
After a while I noticed that there is a source package called
jquery-goodies. Are there any specific rules for i
On Thu, Sep 13, 2012 at 10:08 PM, Per Andersson wrote:
>
> After a while I noticed that there is a source package called
> jquery-goodies. Are there any specific rules for including stuff
> in that package?
Actually, could I get a quick primer on how to introduce new stuff in
that package?
Best
Package: libv8
Severity: grave
Tags: security
Hi,
please check the status of these security issues in libv8.
They were all fixed in Chrome, but it's not clearly from
which Chrome release the libv8 package in Wheezy was cut:
http://security-tracker.debian.org/tracker/CVE-2011-3111
http://security-
