Ping. It's going to work ...
On 5/22/25 8:35 PM, Volker Schlecht wrote:
Here's another update to another latest release of lang/node.
Fortunately it's very low impact, barely touches v8 and is thus very
unlikely
to break anything.
Tested on amd64 and arm64. ok?
Here's another update to another latest release of lang/node.
Fortunately it's very low impact, barely touches v8 and is thus very unlikely
to break anything.
Tested on amd64 and arm64. ok?
Index: Makefile
===
RCS file: /cvs/ports/la
Unusually simple update to the latest release of lang/node.
Builds and works on amd64 and arm64, slight changes in riscv64 related
code however, but I think I got the diff right this time :-)
ok?Index: Makefile
===
RCS file: /cvs/po
I think it's safe to ask for ok now. Anyone?
On 2025-02-11 20:52, Volker Schlecht wrote:
Trivial update for lang/node, even without any PLIST churn.
v8 is basically untouched, so no build issues to be expected.
I'll be dogfooding it for a bit and will probably come asking for ok on the
weekend.
Trivial update for lang/node, even without any PLIST churn.
v8 is basically untouched, so no build issues to be expected.
I'll be dogfooding it for a bit and will probably come asking for ok on the
weekend.
If anyone else wants to give it a spin ...
Index: Makefile
==
Update to latest lang/node release. Builds and runs on amd64 (IBT), and arm64
(non-BTI).
They fiddled with something riscv64 related, so it might benefit from a test
there:
https://github.com/nodejs/node/pull/52888/files
Thoughts? OK?
Index: Makefile
===
On Wed, Dec 04, 2024 at 06:48:03PM +0100, Volker Schlecht wrote:
> An unusually simple diff to update lang/node to v22.12.0
>
> Built and lightly tested on amd64.
> v8 is unchanged, so this is very unlikely to break on other platforms.
> However it requires libuv 1.49.x to build.
An unusually simple diff to update lang/node to v22.12.0
Built and lightly tested on amd64.
v8 is unchanged, so this is very unlikely to break on other platforms.
However it requires libuv 1.49.x to build.
Index: Makefile
===
RCS
Time to ask for ok:
* Builds and runs on amd64 (tested with IBT)
* Builds and runs on arm64 (tested without IBT)
* Builds and runs on riscv64 (tested by jca@)
* Rebuilds www/mozilla-firefox (tested on arm64)
I couldn't find a problem with the node things I'm using.
aisha@, I'm not actively using
Simple update to the latest release plus a bit of npm-based PLIST churn.
Builds and works fine on arm64 and amd64, v8 barely changed so unlikely to cause
issues with other archs.
ok?
Index: Makefile
===
RCS file: /cvs/ports/lang/nod
Updates lang/node to the latest release and switches build to OpenSSL 3.2
Tested on arm64 and amd64, so far I noticed no fallout of the change in OpenSSL.
Upstream still bundles OpenSSL 3.0, so we're already deviating from upstream
here anyway.
Opinions? OKs?
Index: Makefile
===
Attached is a security update to node v20.15.1, addressing
CVE-2024-36138 - Bypass incomplete fix of CVE-2024-27980 (High, Windows-Only!)
CVE-2024-22020 - Bypass network import restriction via data URL (Medium)
CVE-2024-22018 - fs.lstat bypasses permission model (Low)
CVE-2024-36137 - fs.fchown/f
On Thu, Jun 20, 2024 at 11:26:13PM +0200, Volker Schlecht wrote:
> I've been sitting on node v20.14.0 just long enough for the v20.15.0 release
> to happen :-)
>
> Built and tested on arm64 and amd64, and the diff doesn't look like it'd cause
> trouble on any other platform.
builds fine and I can
I've been sitting on node v20.14.0 just long enough for the v20.15.0 release
to happen :-)
Built and tested on arm64 and amd64, and the diff doesn't look like it'd cause
trouble on any other platform.
Index: Makefile
===
RCS file: /c
On Sat, May 18, 2024 at 10:19:25AM +0200, Volker Schlecht wrote:
> Just as a heads up:
>
> amd64 and arm64 tested by myself, I have been dogfooding node 20.x on amd64
> for
> a while already.
It also went through an amd64 bulk build (minus chrome variants).
> i386 built, lightly tested by tb@
>
Just as a heads up:
amd64 and arm64 tested by myself, I have been dogfooding node 20.x on amd64 for
a while already.
i386 built, lightly tested by tb@
riscv64 tested by jca@
ok?
On 2024-05-14 19:33, Volker Schlecht wrote:
Update with some additional feedback from jca@ for riscv64 and without
Update with some additional feedback from jca@ for riscv64 and without REVISION.
On 2024-05-13 19:51, Volker Schlecht wrote:
I'd like to propose a switch of lang/node to their 20.x release branch, the
currently active LTS release, which is probably more likely to become compatible
with OpenSSL 3
I'd like to propose a switch of lang/node to their 20.x release branch, the
currently active LTS release, which is probably more likely to become compatible
with OpenSSL 3.2 eventually :-)
The attached diff builds and works on amd64 (with IBT) and arm64 (tested
without IBT). It includes patches f
On Thu, Feb 15, 2024 at 06:55:48PM +0100, Volker Schlecht wrote:
> Security update to v18.19.1
>
> https://nodejs.org/en/blog/vulnerability/february-2024-security-releases/
>
> Fixes
> CVE-2024-24758 (in the bundled version of undici)
> CVE-2024-22019
> CVE-2024-21896
> CVE-2024-22017
> CVE-2023-
Security update to v18.19.1
https://nodejs.org/en/blog/vulnerability/february-2024-security-releases/
Fixes
CVE-2024-24758 (in the bundled version of undici)
CVE-2024-22019
CVE-2024-21896
CVE-2024-22017
CVE-2023-46809
CVE-2024-21891
CVE-2024-21890
The diff to v18.19.0 is rather small, v8 isn't
Update of everyone's favourite port to the latest release, probably the last
one before I'll try to get Node 20 up and running over the holidays.
Adds two patches to get the newly bundled dependency "ada" not to conflict with
our arpa/nameser.h, other than that nothing particularly exciting.
Bui
Here's a simple update for lang/node for a change:
v18.18.1
* Changed bundled versions of libuv, which doesn't affect our build since
we're building against libuv in ports
v18.18.2
* Changed bundled version of nghttp2, which doesn't affect us since we're
building against nghttp2 in ports
* Ch
On Mon Sep 25, 2023 at 7:59 PM CEST, Stuart Henderson wrote:
> On 2023/09/25 19:35, Volker Schlecht wrote:
> > updated diff against the current version in tree (MASTER_SITES removed...)
> >
> > On Sat Sep 23, 2023 at 3:16 PM CEST, Volker Schlecht wrote:
> > > Update to the original patch including
On 2023/09/25 19:35, Volker Schlecht wrote:
> updated diff against the current version in tree (MASTER_SITES removed...)
>
> On Sat Sep 23, 2023 at 3:16 PM CEST, Volker Schlecht wrote:
> > Update to the original patch including a fix for ppc64 from gkoehler@
> >
> > ok?
> >
> > On Wed Sep 20, 2023
updated diff against the current version in tree (MASTER_SITES removed...)
On Sat Sep 23, 2023 at 3:16 PM CEST, Volker Schlecht wrote:
> Update to the original patch including a fix for ppc64 from gkoehler@
>
> ok?
>
> On Wed Sep 20, 2023 at 12:14 AM CEST, Volker Schlecht wrote:
> > * Updates lang
Update to the original patch including a fix for ppc64 from gkoehler@
ok?
On Wed Sep 20, 2023 at 12:14 AM CEST, Volker Schlecht wrote:
> * Updates lang/node to the latest revision of the LTS release branch.
> * Use SITES
>
> Node dropped the node-gyp binary in this release, which has been depreca
* Updates lang/node to the latest revision of the LTS release branch.
* Use SITES
Node dropped the node-gyp binary in this release, which has been deprecated for
a while. As far as I can tell, the only port that's actually building a node
extension is lang/node itself, so this shouldn't cause any
node just released a security update, fixing:
CVE-2023-30581:
mainModule.__proto__ Bypass Experimental Policy Mechanism (High)
CVE-2023-30588:
Process interuption due to invalid Public Key information in x509
certificates (Medium)
CVE-2023-30589:
HTTP Request Smuggling via Empty headers separat
I added a bit to the patch comments and committed.
On 2023/05/14 16:29, Thomas Frohwein wrote:
> I'm a bit curious if there might be a risk of other Tiger Lake-related
> issues and this could be the canary?
This is about AVX-512. AIUI it requires not just CPU support but also
OS support. Current
On Sun, May 14, 2023 at 09:55:15PM +0200, Volker Schlecht wrote:
[...]
> Tested on amd64 (on a system that didn't show the bug in the first place).
> thfr@ confirmed that with this diff he doesn't see the build failing on his
> Tiger Lake system anymore.
Thanks Volker! I'd like to mention it also
Friendly ping ... amd64, arm64 and i386 are fine, and as far as I could
tell there are no changes that could negatively impact riscv64 nor
powerpc64.
On 4/22/23 10:01, Volker Schlecht wrote:
Ping
On 4/14/23 18:06, Volker Schlecht wrote:
Time for an easy update of everyone's favorite port:
Upd
Ping
On 4/14/23 18:06, Volker Schlecht wrote:
Time for an easy update of everyone's favorite port:
Update node to v18.16.0
Adds initial support for compiling JavaScript into single executables.
Didn't test that, and don't think it's a particularly good idea.
Lots of smaller changes and fixes o
Time for an easy update of everyone's favorite port:
Update node to v18.16.0
Adds initial support for compiling JavaScript into single executables.
Didn't test that, and don't think it's a particularly good idea.
Lots of smaller changes and fixes otherwise:
https://github.com/nodejs/node/blob/ma
On 2023/03/14 16:38, A Tammy wrote:
>
> On 3/12/23 14:40, Volker Schlecht wrote:
> > Updates lang/node to the latest release 18.15.0
> > https://github.com/nodejs/node/releases/tag/v18.15.0
> >
> > Builds and runs fine on amd64, i386 and arm64.
> >
> > AFAICT no changes with an obvious risk for ot
On 3/12/23 14:40, Volker Schlecht wrote:
> Updates lang/node to the latest release 18.15.0
> https://github.com/nodejs/node/releases/tag/v18.15.0
>
> Builds and runs fine on amd64, i386 and arm64.
>
> AFAICT no changes with an obvious risk for other platforms.
> As usual, quite a bit of PLIST chu
Updates lang/node to the latest release 18.15.0
https://github.com/nodejs/node/releases/tag/v18.15.0
Builds and runs fine on amd64, i386 and arm64.
AFAICT no changes with an obvious risk for other platforms.
As usual, quite a bit of PLIST churn due to npm.Index: Makefile
On 2/12/23 09:02, Volker Schlecht wrote:
> ping
>
> On 2/5/23 14:17, Volker Schlecht wrote:
>> Update lang/node to 18.14.0
>>
>> * reinstate old patch to disable building the bundled googletest,
>> because that could lead to build-time conflicts when devel/gt
ping
On 2/5/23 14:17, Volker Schlecht wrote:
Update lang/node to 18.14.0
* reinstate old patch to disable building the bundled googletest,
because that could lead to build-time conflicts when devel/gtest is
installed, now that the version of devel/gtest has diverged from the
bundled version
Update lang/node to 18.14.0
* reinstate old patch to disable building the bundled googletest,
because that could lead to build-time conflicts when devel/gtest is
installed, now that the version of devel/gtest has diverged from the
bundled version again
* This fixes a build issue on riscv64
Here's an update for everyone's favourite port. Nothing particularly
urgent or important about it, according to upstream's changelog.
Tested on amd64, arm64 and i386. Builds and runs fine on all three.
None of the riscv64 patches are affected by the update, but there's been
some renaming of ri
With the attached patch, node builds and works for me on my freshly
dedicated i386 build machine and on amd64.
On 1/4/23 07:26, Barry K. Nathan wrote:
On Tue, Jan 3, 2023 at 4:20 PM Volker Schlecht
wrote:
Looping in Barry since he reportedly had the build working on i386, in
the hope that he
On Tue, Jan 3, 2023 at 4:20 PM Volker Schlecht
wrote:
>
> Looping in Barry since he reportedly had the build working on i386, in
> the hope that he can remember the missing puzzle piece.
I'll look at this when I get a chance, but that may not be until
the weekend, unfortunately. (In addition to o
Looping in Barry since he reportedly had the build working on i386, in
the hope that he can remember the missing puzzle piece.
The patch in www/chromium is against a very different version of v8, so
I don't think that'll be much help here.
My next best guess would be to patch in
#if !defined
On 2023/01/03 21:04, Volker Schlecht wrote:
> I think I lost Barry K. Nathan's patch somehow.
> Does that fix the build?
>
> Still works on amd64 with that one.
>
>
>
> On 1/3/23 13:18, Stuart Henderson wrote:
> > On 2023/01/03 11:31, Stuart Henderson wrote:
> > > FYI, this was broken on i386,
I think I lost Barry K. Nathan's patch somehow.
Does that fix the build?
Still works on amd64 with that one.
On 1/3/23 13:18, Stuart Henderson wrote:
On 2023/01/03 11:31, Stuart Henderson wrote:
FYI, this was broken on i386, and probably any non-LP64 arch.
I have now synced patch-deps_v8_src
On 2023/01/03 11:31, Stuart Henderson wrote:
> FYI, this was broken on i386, and probably any non-LP64 arch.
> I have now synced patch-deps_v8_src_base_atomicops_h with the patch in
> www/chromium which should fix it (retrying build now), that's the only
> difference in that v8 patches between node
FYI, this was broken on i386, and probably any non-LP64 arch.
I have now synced patch-deps_v8_src_base_atomicops_h with the patch in
www/chromium which should fix it (retrying build now), that's the only
difference in that v8 patches between node and chromium.
- Forwarded message from Stuart
It took half an eternity, but my raspberry pi just successfully built a
working node 18.12.1 with the attached diff. It's the same as the last
one, I'm just attaching it again for convenience.
So far we had successful tests on:
* amd64
* i386
* aarch64
* riscv64
On 12/29/22 00:36, A Tammy wr
> > Not sure why lib/eopenssl30/{crypto,ssl} aren't found by
> > port-lib-depends-check...
>
> Not sure either, but that was the case for node 16 with eopenssl11 already
> ...
port-lib-depends-check doesn't handle libraries in lib/subdir/
On 12/29/22 02:28, Thomas Frohwein wrote:
- Build log shows a bunch of '-O3', not everywhere, but looks like
CFLAGS/CXXFLAGS aren't honored consistently.
True, thanks for catching that!
- I'm getting some odd messages from `make port-lib-depends-check`:
node-18.12.1v0(lang/node):
Bogus
I can compile and run a brief interactive test session with the
interactive node interpreter. Noticed a two things, guess they might be
known already about the port (?):
- Build log shows a bunch of '-O3', not everywhere, but looks like
CFLAGS/CXXFLAGS aren't honored consistently.
- I'm getting
On 12/27/22 11:10, Volker Schlecht wrote:
> bump
>
> On 12/20/22 19:15, Volker Schlecht wrote:
>> bump once more in the hope of finding someone to eventually commit ;-)
>>
working fine for me.
ok aisha
going to commit this tomorrow if no one has any objections. I don't know
if we have testers for
bump
On 12/20/22 19:15, Volker Schlecht wrote:
bump once more in the hope of finding someone to eventually commit ;-)
On 12/17/22 09:55, Volker Schlecht wrote:
bump
On 12/10/22 15:24, Volker Schlecht wrote:
If it works, it works ...
Here's the diff with Barry's i386 change included.
So we h
bump once more in the hope of finding someone to eventually commit ;-)
On 12/17/22 09:55, Volker Schlecht wrote:
bump
On 12/10/22 15:24, Volker Schlecht wrote:
If it works, it works ...
Here's the diff with Barry's i386 change included.
So we have positives on amd64, i386 and riscv64 now.
(
bump
On 12/10/22 15:24, Volker Schlecht wrote:
If it works, it works ...
Here's the diff with Barry's i386 change included.
So we have positives on amd64, i386 and riscv64 now.
(By the way, the patch from my previous email worked for me on both
amd64 and i386.)
If it works, it works ...
Here's the diff with Barry's i386 change included.
So we have positives on amd64, i386 and riscv64 now.
(By the way, the patch from my previous email worked for me on both
amd64 and i386.)
Index: Makefile
==
On Sat, Dec 10, 2022 at 5:05 AM Volker Schlecht
wrote:
>
> Hi Barry,
>
> thanks! I noticed that www/chromium already removed a part of the patch
> to use the inline definition of Relaxed_CompareAndSwap.
>
> Unfortunately I don't have an i386 machine to test on, but wouldn't the
> attached variant
Hi Barry,
thanks! I noticed that www/chromium already removed a part of the patch
to use the inline definition of Relaxed_CompareAndSwap.
Unfortunately I don't have an i386 machine to test on, but wouldn't the
attached variant fix the same issue?
regards,
Volker
On 12/10/22 11:21, Barry K.
On Sat, Dec 10, 2022 at 12:35 AM Volker Schlecht
wrote:
>
> FWIW, github user barrykn, who identified the bug now also confirmed
> that it builds and works.
Hi, I'm github user barrykn!
It builds and works on amd64, but it fails to build on i386.
On i386 I get lots of errors like this:
In file
FWIW, github user barrykn, who identified the bug now also confirmed
that it builds and works.
On 12/6/22 17:03, Volker Schlecht wrote:
Someone in nodejs' github found an embarrassing typo (thanks barrykn!).
Updated patch is attached!
On 12/6/22 16:23, Theo Buehler wrote:
It looks like you'ru
Someone in nodejs' github found an embarrassing typo (thanks barrykn!).
Updated patch is attached!
On 12/6/22 16:23, Theo Buehler wrote:
It looks like you'running 'make test', which fails because tests can't be
run as _pbuild.
Oh yes, indeed. Thanks.
Index: Makefile
==
> It looks like you'running 'make test', which fails because tests can't be
> run as _pbuild.
Oh yes, indeed. Thanks.
On 12/6/22 06:57, Theo Buehler wrote:
I don't care deeply if OpenSSL 3 is used for this, I just wanted to make
sure the switch wasn't made blindly since newer is better (which in this
case it probably isn't).
It really wasn't - I just intend to stick as closely to upstream's choices
as possi
> > I don't care deeply if OpenSSL 3 is used for this, I just wanted to make
> > sure the switch wasn't made blindly since newer is better (which in this
> > case it probably isn't).
>
> It really wasn't - I just intend to stick as closely to upstream's choices
> as possible without having to get
On 12/5/22 23:27, Theo Buehler wrote:
On Mon, Dec 05, 2022 at 11:14:56PM +0100, Volker Schlecht wrote:
That's switching as in "They bundle OpenSSL 3.07 + QUIC Patch and that's
what they develop against".
They also support BoringSSL which does not yet provide any OpenSSL 3 API.
Well ... fo
On Mon, Dec 05, 2022 at 11:14:56PM +0100, Volker Schlecht wrote:
> That's switching as in "They bundle OpenSSL 3.07 + QUIC Patch and that's
> what they develop against".
They also support BoringSSL which does not yet provide any OpenSSL 3 API.
> Also the project would rather have switched to Open
That's switching as in "They bundle OpenSSL 3.07 + QUIC Patch and that's
what they develop against".
Also the project would rather have switched to OpenSSL 3.0 for the
previous LTS release already:
https://nodejs.org/en/blog/announcements/nodejs16-eol/
So while it might build against OpenSSL
On Mon, Dec 05, 2022 at 09:24:35PM +0100, Volker Schlecht wrote:
> Upstream switched to OpenSSL 3 with their 18.x release:
>
> https://openjsf.org/blog/2022/04/19/nodejs-18-released/
Is that an actual switch as "switching is required"? The language sounds
more like they plan to support their LTS
Upstream switched to OpenSSL 3 with their 18.x release:
https://openjsf.org/blog/2022/04/19/nodejs-18-released/
On 12/5/22 21:18, Theo Buehler wrote:
@@ -34,7 +33,7 @@ MODULES = lang/python
WANTLIB += c execinfo m pthread ${COMPILER_LIBCXX}
WANTLIB += z brotlienc brotlidec
WAN
> @@ -34,7 +33,7 @@ MODULES = lang/python
> WANTLIB += c execinfo m pthread ${COMPILER_LIBCXX}
> WANTLIB += z brotlienc brotlidec
> WANTLIB += icudata icui18n icuuc cares nghttp2 uv
> -WANTLIB += lib/eopenssl11/ssl lib/eopenssl11/crypto
> +WANTLIB += lib/eopenssl30/ssl lib/eopenssl30/c
Here's the updated patch for lang/node 18.12.1, including
* Feedback from jca@ for riscv64
* Feedback from sthen@ for comment re: OpenSSL usage
* Upstreamed fix for node-pledge
As of now I'm quite happy with it and am now looking for someone to
check and commit ;-DIndex: Makefile
==
On Sun, Nov 27 2022, Jeremie Courreges-Anglas wrote:
> On Sat, Nov 26 2022, Volker Schlecht wrote:
>> Here's a first shot at updating lang/node to the most recent LTS
>> Release. 16.x is still maintained, but LTS has been switched to 18.x
>> a few weeks ago.
>>
>> Smoke testing showed no major is
On 2022/11/26 20:21, Volker Schlecht wrote:
> +# OpenSSL used: {X,Ed}25519 via EVP, SSL_CIPHER_standard_name and
> +# 5-10 other missing symbols/defines.
We have EVP X25519/Ed25519 now, but there are a whole stack of
other OpenSSL things it tries to use, I started making a list but
there are too m
On Sat, Nov 26 2022, Volker Schlecht wrote:
> Here's a first shot at updating lang/node to the most recent LTS
> Release. 16.x is still maintained, but LTS has been switched to 18.x
> a few weeks ago.
>
> Smoke testing showed no major issues so far, so I'll be dogfooding this
> for a while. Howeve
Here's a first shot at updating lang/node to the most recent LTS
Release. 16.x is still maintained, but LTS has been switched to 18.x a
few weeks ago.
Smoke testing showed no major issues so far, so I'll be dogfooding this
for a while. However a few more eyes on it would be very welcome.
In
On Tue, Aug 23 2022, Volker Schlecht wrote:
> Attached diff updates lang/node to v16.17.0
> https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V16.md#16.17.0
>
> Refreshingly little PLIST churn, considering that they updated npm,
> though ;-)
Refreshed diff for those who want to te
Le Tue, Aug 23, 2022 at 09:17:02PM +0200, Volker Schlecht a écrit :
> I'd like to add: www/mozilla-firefox 104.0 builds fine with it.
>
> I saw a metric ton of "function control flow change detected (hash
> mismatch)" warnings though. Unlikely to be related to lang/node, but is that
> to be expect
FWIW, I built this and I build-tested devel/electron and
www/tor-browser/browser with this, that worked.
Caspar
On Sat, Jul 16, 2022 at 11:37:43AM +0200, Volker Schlecht wrote:
> Regular bump ;)
>
> On 7/10/22 18:59, Volker Schlecht wrote:
> > On 7/10/22 15:10, Caspar Schutijser wrote:
> > > Hi,
Hi,
No comment on the diff itself but:
On Fri, Jul 08, 2022 at 11:31:01AM +0200, Volker Schlecht wrote:
> Attached patch updates lang/node to 16.16.0
>
> This contains fixes for:
>
> CVE-2022-32212 (High)
> CVE-2022-32213 (Medium)
> CVE-2022-32214 (Medium)
> CVE-2022-32215 (Medium)
>
> https:/
Ah thanks, that looks promising, I can probably fix it in the build then
On 2022/06/08 22:31, Volker Schlecht wrote:
> From a (very) quick glance, the issue might be related to this:
>
> https://github.com/npm/cli/issues/4996
>
> I'll look into it, but due to time constraints might take a few da
I had committed this but now backed it out as it's breaking build of
devel/electron
[1132/32676] ACTION
//electron:electron_version_args(//build/toolchain/openbsd:clang_x64)
FAILED: gen/electron/electron_version.args
python ../../electron/build/npm-run.py --silent generate-version-json --
/usr/o
On 2022/06/04 15:58, Volker Schlecht wrote:
> This updates lang/node to 16.15.1
>
> Changes:
> * use tar.xz instead of tar.gz (smaller archives)
> * make use of devel/gtest in TEST_DEPENDS ... gtest in ports no longer
> conflicts with the bundled version
> * PLIST churn due to update of the bundle
On 2022/03/10 20:09, Volker Schlecht wrote:
> On 3/10/22 15:13, Stuart Henderson wrote:
>
> > > https://github.com/nodejs/node/blob/v12.x/doc/api/net.md
> > >
> > > "If host is omitted, the server will accept connections on the unspecified
> > > IPv6 address (::) when IPv6 is available, or the un
On 2022/03/09 22:18, Volker Schlecht wrote:
>
>
> On 3/9/22 15:57, Stuart Henderson wrote:
> > On 2022/02/10 21:18, Volker Schlecht wrote:
> > > I integrated the patch for src/env.cc, dropped one for the bundled uv and
> > > upgraded to 12.22.10 ... what do you think?
> >
> > Sorry it took a whi
On 2022/02/10 21:18, Volker Schlecht wrote:
> I integrated the patch for src/env.cc, dropped one for the bundled uv and
> upgraded to 12.22.10 ... what do you think?
Sorry it took a while to test this. I would like to get this in but it's
not working properly for me, sockets now only listen to IPv
On 2022/02/16 16:01, Volker Schlecht wrote:
> bump.
revision 1.97
date: 2022/02/16 14:24:37; author: sthen; state: Exp; lines: +2 -3;
commitid: xIIFyVflHgyhbQ00;
update to node-16.14.0, from maintainer Volker Schlecht
;)
> On 2/10/22 22:37, Volker Schlecht wrote:
> > Regular update, no expl
bump.
On 2/10/22 22:37, Volker Schlecht wrote:
Regular update, no explicitly mentioned security content.
PLIST changes are due to the update of the bundled npm to 8.3.1
Regular update, no explicitly mentioned security content.
PLIST changes are due to the update of the bundled npm to 8.3.1Index: Makefile
===
RCS file: /cvs/ports/lang/node/Makefile,v
retrieving revision 1.96
diff -u -p -r1.96 Makefil
I integrated the patch for src/env.cc, dropped one for the bundled uv
and upgraded to 12.22.10 ... what do you think?
On 2/9/22 20:53, Volker Schlecht wrote:
On 2/9/22 14:01, Stuart Henderson wrote:
Some software I run doesn't work with 16.x yet, so I have reworked a
port for 12 based on the c
On 2/9/22 14:01, Stuart Henderson wrote:
Some software I run doesn't work with 16.x yet, so I have reworked a
port for 12 based on the changes in 16 (using system libraries etc)
and wondered what you think about including it in the tree alongside?
My only concern is that node 12 will not be sup
On 2022/02/09 12:58, Stuart Henderson wrote:
> /tmp/node12.tgz
Oops, sent the attachment but not the text :)
Some software I run doesn't work with 16.x yet, so I have reworked a
port for 12 based on the changes in 16 (using system libraries etc)
and wondered what you think about including it in t
/tmp/node12.tgz
node12.tgz
Description: application/tar-gz
Sure ... https://github.com/nodejs/node/issues/41834
On 2/3/22 20:05, Aaron Bieber wrote:
Volker Schlecht writes:
The other patch should fix builds breaking on machines with devel/gtest
installed from ports. In those cases, node picked up and used the (ancient)
ports version, instead of the
Volker Schlecht writes:
>>> The other patch should fix builds breaking on machines with devel/gtest
>>> installed from ports. In those cases, node picked up and used the (ancient)
>>> ports version, instead of the bundled one.
>> that one fails on a system without gtest installed:
>
> Right, se
The other patch should fix builds breaking on machines with devel/gtest
installed from ports. In those cases, node picked up and used the (ancient)
ports version, instead of the bundled one.
that one fails on a system without gtest installed:
Right, seem we have to add the bundle's include p
On 2022/02/03 17:56, Volker Schlecht wrote:
> I've included another patch nicked from www/chromium that looks like it
> addresses this issue. I had no way of testing i386, so I didn't just blindly
> include it at first.
>
> Note: www/chromium includes another ia32 patch, that's not needed in
> lan
I've included another patch nicked from www/chromium that looks like it
addresses this issue. I had no way of testing i386, so I didn't just
blindly include it at first.
Note: www/chromium includes another ia32 patch, that's not needed in
lang/node and probably in www/chromium anymore:
patch
This fails on i386; various errors like
../deps/v8/src/wasm/baseline/ia32/liftoff-assembler-ia32.h:433:24: error:
out-of-line definition of 'Load' does not match any declaration in
'v8::internal::wasm::LiftoffAssembler'
gzipped build log attached.
node.log.gz
Description: application/gunzip
Volker Schlecht writes:
> Even smaller diff attached.
>
> To reiterate the (intended) changes to look out for:
>
> * Update to v16.13.2 (Active LTS Release)
>
> * Change from bundled versions of
> - libuv
> - c-ares
> - nghttp2
> - zlib
> - brotli
> - icu
>
On 2022/01/26 08:12, Volker Schlecht wrote:
> At the risk of being considered a PITA: Is there anything *I* can do to
> move this a step forward?
I can only speak for myself and there are other people that can
review too, but I already mentioned what would have made it easier for
me to review on t
1 - 100 of 214 matches
Mail list logo
