For those following this discussion: there is now a version of
r-cran-v8 that uses libnode-dev in sid. Is there anything we need to
do to get r-cran-v8 back in buster?
On Tue, Jan 29, 2019 at 10:04 AM Andreas Tille wrote:
>
> Hi Jeroen,
>
> I realised that the Debian package of V8 has de facto
On Fri, Feb 8, 2019 at 9:44 AM Jérémy Lal wrote:
>
>
>
> Le ven. 8 févr. 2019 à 07:36, Jeroen Ooms a écrit :
>>
>> For those following this discussion: there is now a version of
>> r-cran-v8 that uses libnode-dev in sid. Is there anything we need to
>>
Is there another version of libv8 available on Debian? I'm willing to
try to port it to a newer version of V8. The issue with libv8 has
always been that Google refuses to define a stable API, and they do a
new release every day (no joke). So it's very hard to program against
that.
That said,
On Tue, Jan 29, 2019 at 10:56 AM Jérémy Lal wrote:
>
>
>
> Le mar. 29 janv. 2019 à 19:41, Jeroen Ooms a écrit :
>>
>> Is there another version of libv8 available on Debian? I'm willing to
>> try to port it to a newer version of V8. The issue with libv8 has
>
On Tue, Jan 29, 2019 at 12:15 PM Jonas Smedegaard wrote:
>
> Quoting Jeroen Ooms (2019-01-29 20:11:20)
> > On Tue, Jan 29, 2019 at 10:56 AM Jérémy Lal wrote:
> > >
> > >
> > >
> > > Le mar. 29 janv. 2019 à 19:41, Jeroen Ooms a écrit :
> >
On Tue, Jan 29, 2019 at 1:04 AM Andreas Tille wrote:
>
> The problem is that the CRAN V8 package has some reverse dependencies
> which all are affected and can not migrate to the next Debian stable
> release which would be a real shame. Do you see any chance to adapt V8
> to some more recent
On Wed, May 22, 2019 at 11:06 AM Jérémy Lal wrote:
>>> Hi Jérémy
>>>
>>> Now that r-cran-v8 seems to be working great with libnode-dev, perhaps
>>> the old libv8 should be removed from sid? Today I was working in sid
>>> and I noticed that apt still prefers the old v8 over the libnode-dev
>>>
