Hi
libuv1 1.48.0 contains a fix for CVE-2024-24806.
Can I upload it directly to unstable ?
or do you have an on-going transition on nodejs ?
All the best
Dod
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Hi
Following Jeremy's request, I've uploaded libuv1 1.46.0-1 in experimental.
Please tell me if it's fine with you to upload to unstable.
Without news from your group, I'll upload libuv1 in unstable at the end of
September.
All the best
Dominique
--
Pkg-javascript-devel mailing list
On Sunday, 31 July 2022 16:35:12 CEST Jérémy Lal wrote:
> Indeed, sorry for my somewhat irritated tone - it just happens that it was
> the second time libuv1 was updated during a nodejs transition, and the
> upstream bug it creates on nodejs hasn't been fixed yet, so it shoots the
> transition in
On Saturday, 30 July 2022 19:36:26 CEST you wrote:
> libuv1 is a library, you're supposed to manage the transition:
> https://wiki.debian.org/Teams/ReleaseTeam/Transitions
This page applies when the new version breaks the ABI or API. This was not the
case. There was no symbol change. The SO
On Saturday, 30 July 2022 17:25:29 CEST you wrote:
> libuv1 maintainer: please avoid uploading new versions when nodejs is
> in transition...
I package libuv1 because it's a dependency of moarvm.
I don't follow nodejs releases, so I was not aware of on-going transition and
I did not expect
On Monday, 11 February 2019 09:51:11 CET Jérémy Lal wrote:
> that's what i tried to do in the first place.
> However, the lack of v8 soname and abi stability across versions gave me so
> much additional work that i ended up not doing it at all, leading to v8
> being unmaintained. The solution here
Hi
On Friday, 8 February 2019 12:10:01 CET Jérémy Lal wrote:
> > I suppose i need to ask a removal of libv8 from unstable (it's removed
> > from testing) to
> > be able to "take" libv8-dev. Or maybe declare a libv8-in-nodejs-dev
> > package ?
> > In any case i don't know if i should make a
On Tue, 3 Jul 2018 19:46:30 +0200 Paul Gevers wrote:
> ok 9 fs - fs.scandir
> ./tests/test-fs.lua:83: UNKNOWN FS TYPE 29
Looks like this issue has been fixed in upstream lua:
https://github.com/luvit/luv/commit/853546063c88f0f06b680844b8a2c90dc13343d3
All the best
--
Pkg-javascript-devel
On Saturday, 2 June 2018 17:01:42 CEST you wrote:
> I tend to think there's an issue with the error codes either in the
> kernel or libuv1. I doubt we are
> actually running out of memory.
ok. I've forwarded the bug upstream [1].
Please follow-up there.
All the best
[1]
On Thursday, 17 May 2018 09:41:46 CEST Paolo Greppi wrote:
> If we are sure that this is undesirable, we should also fix it in a lot of
> other places: http://deb.li/RcWh
We had a similar problem with Perl program delivered as debian packages. Now,
Perl policy requires programs to start with
Package: node-js-yaml
Version: 3.11.0+dfsg-1
Severity: normal
File: /usr/lib/nodejs/js-yaml/bin/js-yaml.js
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I have both nodejs installed by Debian package and an
On Monday, 30 April 2018 15:23:47 CEST Luca BRUNO wrote:
> Feel free to start migrating it to salsa, I've been slowly moving my other
> stuff there too.
Done: https://salsa.debian.org/debian/libuv1
> I'm not actively using libuv1 anymore, which is why I've
> been lagging behind lately, but I
Hello
libuv1 is used by projects than nodejs, Perl6 cmake and other. It's still
hosted on alioth in in javascript team repo. It's only uploader is Luca Bruno.
All uploads since 2016 were done by team uploads.
Since Alioth is now deprecated, it's time to migrate libvu1 to Salsa.
After
13 matches
Mail list logo
