New WASM related mailing list

Hi all, as there has been an interest in creating WASM SIG , I moved on with it. You can already join our mailing list: wasm-...@lists.fedoraproject.org

Re: Web Assembly on Fedora: interested in a Fedora SIG to work on this?

I opened an issue for a mailing list to be created in case someone wants to follow/provide feedback. https://pagure.io/fedora-infrastructure/issue/11087 Zuzka On Wed, Jan 11, 2023 at 4:34 PM Michael Dawson wrote: > It's the new year and we are going to get things going. > > Zuzana is going to

Node.js 14 in F33

Node.js v14.x was released last week, which should become LTS in autumn. modular builds for stable releases and rawhide are already submitted in Bodhi and should be available soon. I'd like to make it the default stream for F33 once it's tested a bit. I'd like to ask maintainers and users of nodej

Renaming nodejs-yarn -> yarnpkg

Hi, I submitted a rename review[1] for nodejs-yarn to be renamed to yarnpkg to make it more consistent with other distros and upstream. If you have any comments or this change causes you any issues, feel free to speak up. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1823724 Thanks Zuzka ___

Re: Orphaned packages need new maintainers

I'll take them. On Tue, Apr 16, 2019 at 10:56 AM Miro Hrončok wrote: > On 15. 04. 19 18:52, Christopher wrote: > > If nobody picks up the ones by my name (nodejs-path-exists, > > nodejs-bluebird, nodejs-grunt-known-options), then I will probably > > have to orphan js-jquery, because it probably

/usr/bin/yarn conflict between nodejs-yarn, hadoop-yarn and cmdtest

Hi, there are currently three packages, that (should) provide /usr/bin/yarn and it obviously causes conflicts. [1] [2] Right now we would like nodejs-yarn to provide /usr/bin/yarn and cmdtest and hadoop-yarn to use different naming. We would like to get some feed-back (or suggestions) before som

Node.js 8 officially in rawhide

Hi, as announced, yesterday I built nodejs-8.1.2 in rawhide. Please, check that your packages work, especially native modules, as there seem to be a few incompatibilities. We also got new npm@5, which is said to be a little buggy. Regards Zuzka ___ d

Fwd: Node.js v8.x in Fedora

-- Forwarded message -- From: Zuzana Svetlikova Date: Mon, Jun 19, 2017 at 5:48 PM Subject: Node.js v8.x in Fedora To: devel@lists.fedoraproject.org Cc: nod...@lists.fedoraproject.org Hi everyone, as there is nothing stopping us now, the nodejs package in Rawhide will soon be

Node.js v8.x in Fedora

Hi everyone, as there is nothing stopping us now, the nodejs package in Rawhide will soon be updated to Node.js v8.x. It also comes with npm@5 and new V8. Note that upstream has made a lot of changes and your projects/packages might have some issues. I'll update nodejs in rawhide next week, if y

Re: Orphaning packages

Took nodejs-* packages. Zuzka - Original Message - From: "Gerard Ryan" To: devel@lists.fedoraproject.org Sent: Saturday, October 15, 2016 2:21:44 PM Subject: Orphaning packages Hi all, I no longer use the following packages nor have the time to maintain them, so I'm going to orphan the

Using devtoolset for EPEL builds

Hi, I need/want/would like to build new node 6 for EL6, but gcc is too old. For that reason, I'd like to use devtoolset-4-gcc, but the build fails (obviously) because the package doesn't exist. So, is there a way to make that work somehow? I am not sure about enabling external repos during buil