On Sat, Dec 6, 2014 at 4:57 AM, Moritz Mühlenhoff wrote:
> severity serious
> thanks
>
>> This package forks a local copy of the Iceweasel Javascript engine which is
>> no longer supported with security updates (currently only the ESR24 series
>> is maintained)
>>
>> What's the strategy here? Do y
severity serious
thanks
> This package forks a local copy of the Iceweasel Javascript engine which is
> no longer supported with security updates (currently only the ESR24 series
> is maintained)
>
> What's the strategy here? Do you plan to backport/triage all Javascript
> related
> security iss
severity 733496 wishlist
tags 733496 wontfix
thanks
Hi Mike/Emilio,
On Thu, Feb 27, 2014 at 12:06:23PM +0900, Mike Hommey wrote:
> On Wed, Feb 26, 2014 at 08:53:32PM +0100, Emilio Pozuelo Monfort wrote:
> > Hi Moritz,
> >
> > Laurent spoke to Mike regarding this and Mike said he was thinking/pla
On Thu, Feb 27, 2014 at 8:17 AM, Vincent Cheng wrote:
> On Wed, Feb 26, 2014 at 11:09 PM, Emilio Pozuelo Monfort
> wrote:
>> Have you seen #739132 ? Do you have any plans to upload mozjs 24? Given
>> mozjs17
>> hasn't entered testing and has very few rdeps, maybe we could go directly for
>> mozj
Hi Emilio,
On Wed, Feb 26, 2014 at 11:09 PM, Emilio Pozuelo Monfort
wrote:
> Hi Vincent,
>
> Vincent Cheng wrote:
>> 0ad upstream is already working (and making good progress) on
>> migrating to ESR 24, and should be done in time for their next
>> release. I can't speak on behalf of all the other
Hi Vincent,
Vincent Cheng wrote:
> 0ad upstream is already working (and making good progress) on
> migrating to ESR 24, and should be done in time for their next
> release. I can't speak on behalf of all the other packages that depend
> on spidermonkey currently though.
Have you seen #739132 ? Do
On Wed, Feb 26, 2014 at 08:53:32PM +0100, Emilio Pozuelo Monfort wrote:
> Hi Moritz,
>
> Laurent spoke to Mike regarding this and Mike said he was thinking/planning on
> dropping libmozjs packages from src:iceweasel (please correct. The only
> possible
> alternative is to have a code copy as a se
Hi Moritz,
Laurent spoke to Mike regarding this and Mike said he was thinking/planning on
dropping libmozjs packages from src:iceweasel (please correct. The only possible
alternative is to have a code copy as a separate source package (as we have done
with mozjs and now with mozjs17). Note that de
On Thu, Jan 16, 2014 at 1:52 PM, Moritz Mühlenhoff wrote:
> On Sun, Jan 05, 2014 at 02:47:39AM -0800, Vincent Cheng wrote:
>> Hi,
>>
>> > Package: mozjs17
>> > Severity: serious
>> >
>> > This package forks a local copy of the Iceweasel Javascript engine which is
>> > no longer supported with secu
On Sun, Jan 05, 2014 at 02:47:39AM -0800, Vincent Cheng wrote:
> Hi,
>
> > Package: mozjs17
> > Severity: serious
> >
> > This package forks a local copy of the Iceweasel Javascript engine which is
> > no longer supported with security updates (currently only the ESR24 series
> > is maintained)
>
Hi,
> Package: mozjs17
> Severity: serious
>
> This package forks a local copy of the Iceweasel Javascript engine which is
> no longer supported with security updates (currently only the ESR24 series
> is maintained)
Out of curiosity, why is this a RC bug when there seems to be no
issues from the
Package: mozjs17
Severity: serious
This package forks a local copy of the Iceweasel Javascript engine which is
no longer supported with security updates (currently only the ESR24 series
is maintained)
What's the strategy here? Do you plan to backport/triage all Javascript related
security issues
12 matches
Mail list logo
