Re: Non-bootstrappable NPM packages

Nicolas Graves writes: > On 2019-07-24 15:41, Jelle Licht wrote: > >> Timothy Sample writes: >> >> [snip] >> >>> I’ve come to think that bootstrapping JavaScript might be easier than it >>> looks. As time goes on, Node gets better at the newer

Re: Potential removal of unmaintained node-openzwave-shared

Hi, "Philip McGrath" writes: > Hi, > > On Wed, Mar 22, 2023, at 8:08 AM, Jelle Licht wrote: >> Hey guix, >> >> In getting `Node.js' updated to a more recent LTS version[0], I found >> out that node-openzwave-shared no longer builds with mo

Potential removal of unmaintained node-openzwave-shared

Hey guix, In getting `Node.js' updated to a more recent LTS version[0], I found out that node-openzwave-shared no longer builds with modern versions of node [1]; random people on the Internet seem to indicate that the hip new thing is Z-Wave JS [2]. Long story short, what is our de facto policy

Guix driver paths for icecat RDD sandbox

Hi guix, I was playing around tyring to get hardware enabled video decoding working in icecat and/or firefox in guix, and found out that the fine folks working on Nix have already gotten a patch upstreamed that allows stuff in /nix/store to be loaded[0]. (Grep around for '/nix/store' in our

Re: RFC: new syntax for inline patches

Liliana Marie Prikler writes: > Hi Ricardo, > > Am Dienstag, dem 04.01.2022 um 17:50 +0100 schrieb Ricardo Wurmus: >> Hi Guix, >> >> does this pattern look familiar to you? >> >>   (arguments >>     (list >>     #:phases >>     '(modify-phases %standard-phases >>   (add-after 'unpack

Re: importers and input package lookup

Ludovic Courtès writes: > Hi! > > Attila Lendvai skribis: > >> there are two, independent namespaces: >> 1) the scheme one, and >> 2) the guix package repository. >> >> when i work on an importer (golang), it skips the packages that are already >> available in 2), but then it has no clue under

Re: Convention for new “guix style“?

Hi, zimoun writes: > Hi, > > This could be part of a RFC process. :-) > > > The Big Change introduces new style, other said, this old > > --8<---cut here---start->8--- > (native-inputs > `(("perl" ,perl) >("pkg-config" ,pkg-config))) >

Re: Flag day for simplified package inputs

Hello, Ludovic Courtès writes: > Hi, > > Jelle Licht skribis: > >> I will work on that. Do we already have a suitable 'bulk change' in the >> repo? Or should we first run `guix style', and subsequently use that >> commit as the first entry in the .git-blame-igno

Re: Flag day for simplified package inputs

Hello there, Ludovic Courtès writes: > Hi, > > Jelle Licht skribis: > >> Ludovic Courtès writes: >> >>> Hi, >>> >>> Jelle Licht skribis: >>> >>>> When applying this and future bulk changes, could we perhaps list the

Re: Flag day for simplified package inputs

Hello there, Ludovic Courtès writes: > Hi, > > Jelle Licht skribis: > >> When applying this and future bulk changes, could we perhaps list the >> specific commits (+ commented shortlog line) in a file. To clarify, if >> we were to store these commits in `.git-b

Re: Using G-Expressions for public keys (substitutes and possibly more)

Ludovic Courtès writes: > Hi, > > Liliana Marie Prikler skribis: > >> I think we would probably want to improve on this end in the guile- >> gcrypt module, i.e. have a public-key "constructor" that returns a >> canonical-sexp and so on. WDYT? > > I don’t find it very compelling given there’s

Re: Using G-Expressions for public keys (substitutes and possibly more)

Hey folks, Liliana Marie Prikler writes: > Hi Ludo, > > Am Donnerstag, den 21.10.2021, 22:13 +0200 schrieb Ludovic Courtès: >> Hi! >> >> Liliana Marie Prikler skribis: >> >> > let's say I wanted to add my own substitute server to my >> > config.scm. >> > At the time of writing, I would have

Re: Flag day for simplified package inputs

Hey Guix, Ludovic Courtès writes: > Hello Guix! > > As a reminder, the plan I proposed¹ is to have a “flag day” shortly > before ‘core-updates-frozen’ is merged into ‘master’ when we would run > ‘guix style’ on the whole repo, thereby removing input labels from most > packages. > If everything

Re: Patches that should be applied in the Future

Ludovic Courtès writes: > Hi! > > Jelle Licht skribis: > >> What can we do to make sure we won't simply forget to apply this and >> other such changes? > > I’d suggest making this change right away in ‘core-updates’. We need to override a change that has not lande

Patches that should be applied in the Future

Hello there guix, All of this is about core-updates-frozen at revision dac8d013bd1. `c-ares' in gnu/packages/adns.scm has its tests disabled; On my x86_64 machine, it seems the tests for c-ares pass just fine because of the defined GTEST_FILTER when I re-enable them; With my limited git-foo, it

Re: Hero culture among Guix maintainers

Hello Ryan, tl;dr: (!= 'accountability 'blame), but accountability is essential to any social endeavour. Ryan Prior writes: > Hey Guix. There's a specific thing I'm motivated to address after the > recent security incident with the "cosmetic" patches & all the fallout > of that. Some

Re: npm global prefix needs to be a writeable directory

Ryan Prior writes: > On November 26, 2020, Jelle Licht wrote: >> On other distros it defaults to a location that is not writable by >> normal users either; > > Indeed I can confirm that Ubuntu node also has this problem. > >> Another way folks solved this prob

Re: npm global prefix needs to be a writeable directory

Hey, Ryan Prior writes: > Hi folks! I stumbled across an issue with the node package today and > wanted to send a report before I forget. > > npm assumes that the global prefix is a writeable folder. Operations > like `npm link` will fail if it isn't. Right now our node package > doesn't set a

Re: wip-node-14 branch

Ludovic Courtès writes: > Jelle Licht skribis: > >> As a small extra, I have also worked on getting Timothy Sample's >> 'binary' npm importer to work with the contemporary guix import and >> guile-json APIs; I'd like some insight into whether this binary importer >&g

Re: Release: Docker Image? DockerHub? skopeo?

Hello, zimoun writes: > Some days ago, we discussed on #guix about releasing Docker images > ready-to-use. And you pointed your project: > > https://gitlab.com/daym/guix-on-docker/ [snip] > Fourth question for Jelle: do you have time to add examples to the > Cookbook using the package

wip-node-14 branch

Hey Guix! Depending on whom you ask, I come with what I see as good news! I just pushed a series of patches with the long-term goal of getting the Node.js situation in guix unstuck. You may find it on the `wip-node-14' branch on on Savannah. First things first: most of the hard work has been

Re: hide more output

Pierre Neidhardt writes: > Ludovic Courtès writes: > >> So in effect, it wouldn’t display anything upfront, only the size of the >> stuff downloaded right? Plus maybe the list of things to build? > > I think the list of things to build is a lower level details. The users > want to know what's

Re: Guix System on a GCE VM -- Success

Hey there, elaexuo...@wilsonb.com writes: > To simplify the process I created a script capable of setting up a GCE > instance > from a local qcow2 image, which I am also attaching. The script is intentially > not a simple turnkey solution, since you should be somewhat familiar with the > GCE

Working on network-manager-l2tp

Hey guix, Seeing as a lot of people might be working from home at the moment, it seems a good moment to look at issues that might prevent us from using guix for that exact purpose. Right now, I can not connect to my company vpn, which make several processes much more difficult than they need to

Re: branch master updated (0aa0e1f -> 9b7f9e6)

Heya, Ludovic Courtès writes: > [...] > I see reluctance to the proposed changes in > (I > agree with Ricardo’s concerns). > > To me, that suggests at least that further discussion would have been > needed before pushing

Getting docker cli-plugins in guix

Hey guix, Along with many other folks, I find myself in the situation of having to interact with docker often. The latest docker command line client supports a way to add new subcommands via a cli-plugins system[1]. This way of working is easy, but relies on building programs and putting them in

Re: “Guix Profiles in Practice”

Konrad Hinsen writes: > Maybe we should start a Guix CLI nursery. A project/repository separate > from Guix itself that contains a copy of the "guix" script under a > different name ("guixx" for guix-extras?) and with the same interface > for scripting modules. We could then use this to play

Re: Loading modules built using linux-module-build-system

ping :-) Jelle Licht writes: > Hello Guix, > > Not too long ago, the linux-module-build-system was introduced. I ran > into some code in the wild written by Alex Griffin that defines a > shepherd service that does the following for a given kernel-module >

How to keep biber working

Guix, I've noticed some time ago that the biber version that we currently have is incompatible with the texlive revision we have packaged. Incidentally, since the latest core-updates merge, biber does not pass its test suite anymore due to the hardcoded `perl-unicode-collate'-related hashes. I

Re: i686-linux GCC package on x86_64

Jelle Licht writes: > Would `guix build cross-gcc-i686-unknown-linux-gnu' work? > My mail reader did not expand your snippet fully, I overlooked the fact that you already overrode the name field. Sorry for the noise!

Re: i686-linux GCC package on x86_64

Pierre Neidhardt writes: >[snip] > --8<---cut here---start->8--- > (define-public cross-gcc > (package > (inherit ((@@ (gnu packages cross-base) cross-gcc) > "i686-unknown-linux-gnu" > #:libc (cross-libc

Re: Joint statement on the GNU Project

Taylan Kammer writes: > [snip] > > All other political conflicts should IMO be decided on a case by case > basis with the goal of reaching mutual compromise within the confines of > the communication channels of the GNU project. That is, 1. no favorites > on who gets to silence who and 2.

Re: i686-linux GCC package on x86_64

Mathieu Othacehe writes: > > --8<---cut here---start->8--- > (native-inputs > `(,@(if (not (string-prefix? "i686" (%current-system))) >`(("cross-gcc" ,(cross-gcc "i686-unknown-linux-gnu")) > ("cross-binutils" ,(cross-binutils

Re: Let’s merge ‘core-updates’!

Ludovic Courtès writes: > Hello Guix! > > The ‘core-updates’ branch is in a good shape now, and I think we should > go ahead and merge in the coming days! > > Please try to upgrade your system and your user profile to see if > anything’s wrong for you (I did that a few days ago and I’m happy!).

Re: Error cross-compiling Mesa: failing test

Pierre Neidhardt writes: > Jelle Licht writes: > >> Pierre Neidhardt writes: >> >>> (define mesa32 >>> (package >>> (inherit (to32 mesa)) >>> (arguments >>

Re: Error cross-compiling Mesa: failing test

Pierre Neidhardt writes: > (define mesa32 > (package > (inherit (to32 mesa)) > (arguments > (substitute-keyword-arguments (package-arguments mesa) ^ you use (64bit?)

Re: Website translation

"pelzflorian (Florian Pelz)" writes: > [snip] > We could of course translate the URLs instead, we would then add a > procedure url->localized-href that calls gettext to return the > localized URL for a given URL and replace each > > (@ (href "/help")) > > by > > (@ ,(url->localized-href

Re: Non-bootstrappable NPM packages

Timothy Sample writes: [snip] > I’ve come to think that bootstrapping JavaScript might be easier than it > looks. As time goes on, Node gets better at the newer JavaScript > features. This removes the need for things like Babel or Rollup, since > with some care, Node can run the source

Re: IceWeasel-UXP and IceDove-UXP

Hey guixuser, guixuser writes: > [use this thread] > > Budget? Are you serious? Any distro has to focus on their basic things like > email and browser for new user; at least if project wants to grow and > accommodate new users. For at least your browsing needs, I know of two options. Guix

Loading modules built using linux-module-build-system

Hello Guix, Not too long ago, the linux-module-build-system was introduced. I ran into some code in the wild written by Alex Griffin that defines a shepherd service that does the following for a given kernel-module package: - set the LINUX_MODULE_DIRECTORY environment variable to /lib/modules

Re: guix import crate wraps #:cargo-inputs twice

Ivan Petkov writes: > [...] > I tried building some of the crates and most of the errors I saw were > something > like “failed to select a version for the requirement `foo = ^0.6 > candidate versions found which didn’t match: 0.8.5”. > > Please note that the crate importer always picks the

Re: Guix trademarked by Express Logic

mikadoZero writes: > Jelle Licht writes: >> I really think that "software" is much too broad a category to consider >> for a trademark clash in this case. From what I can see, there is barely >> any overlap between our Guix and the GUIX product that Express Log

Re: Guix trademarked by Express Logic

mikadoZero writes: > I have search guix-devel for this and did not find it. I would like to > [ snip ] Thanks for looking into this. > # Proactive name change > > Looking at the pug thread above shows that it would have been nice if > Jade had not been forced to change their name so quickly

Re: Meeting in Brussels on Wednesday evening?

? Contact me if you feel like helping me out, and thanks in advance. Regards, Jelle Licht

Re: 07/07: gnu: emacs-ghub: Update to 3.2.0.

Mark H Weaver writes: > Hi Jelle, > [...] > > In toplevel form: > magit-reset.el:30:1:Error: Cannot open load file: No such file or directory, > graphql > make[1]: *** [Makefile:65: magit-reset.elc] Error 1 > make[1]: Leaving directory >

Re: Help wanted with recursive npm import returning #f

Op di 4 dec. 2018 om 22:07 schreef Jelle Licht : > Hi swedebugia, > > Super swell to see you take an interest in this! :D. > > Some points; > > It seems you wrote your own sanitize-npm-version, but this is not (at all) > how npm > deals with versions; I implore

Re: Help wanted with recursive npm import returning #f

Hi swedebugia, Super swell to see you take an interest in this! :D. Some points; It seems you wrote your own sanitize-npm-version, but this is not (at all) how npm deals with versions; I implore you to have a look at https://semver.org/ again to see what all the silly squigles mean :). A

Re: Cyclic npm dependencies

Op za 24 nov. 2018 om 16:38 schreef Pjotr Prins : > On Sat, Nov 24, 2018 at 03:41:35PM +0000, Jelle Licht wrote: > >Hey swedebugia, > >I will still send a more elaborate reply to the general npm-importer > >thread later this week, but we can

Re: Cyclic npm dependencies

Hey swedebugia, I will still send a more elaborate reply to the general npm-importer thread later this week, but we can assume that generally these recursive dependencies can be untangled by looking at the different versions of the dependencies. So in your example, I imagine an input chain like:

Re: Promoting the GNU Kind Communication Guidelines?

Hello! HiPhish writes: > If you don't want to continue the discussion then so be it, but I cannot leave > my points misrepresented. When I say "you" I don't necessarily mean you > personally, but rather the larger discussion. You don't have to respond if you > don't want to, I believe we have

Re: Promoting the GNU Kind Communication Guidelines?

Hello, HiPhish writes: > I am really trying to understand the other side here, so please help me out on Without attributing malice to your statement here, I think it is disingenuous to talk about "the other side". We are all part of communities we interact with, there is no need for any

Re: GSoC update

2018-07-11 0:40 GMT+02:00 Ludovic Courtès : > Hi Ioannis, > > Ioannis Panagiotis Koutsidis skribis: > > > This patch adds initial support for .socket unit files. It does not > > currently work but is near completion. > > Could you expound a bit? That’s a very short summary for all the sweat >

Re: GSoC: Adding a web interface similar to the Hydra web interface

2018-07-04 22:54 GMT+02:00 Tatiana Sholokhova : > Hi all, > > Hi Tatiana, > I just committed the code I wrote trying to improve pagination. I screwed > up a bit with the new pagination. > The problem I encountered is following. If we want to maintain a link to > the previous page we have to

Re: Maintaining implementations of similar utility functions like json-fetch

Ludovic Courtès writes: > Hey, > > Jelle Licht skribis: > >> I basically added the robust features of `json-fetch*' to the exported >> `json-fetch' >> instead, and all existing functionality seems to work out as far as I can >> see. > > So are you

Re: Improving Shepherd

Ludovic Courtès <l...@gnu.org> writes: Heya, Jelle Licht <jli...@fsfe.org> skribis: Good news: signfalfd seems to work as far as I can see. I am not quite sure how to make it work consistently with guile ports yet though. Good! What do you mean by “work with guile p

Re: Improving Shepherd

Hey all, 2018-02-05 14:08 GMT+01:00 Ludovic Courtès : > Hello! > > [...] > > Currently shepherd monitors SIGCHLD, and it’s not supposed to miss > those; in some cases it might handle them later than you’d expect, which > means that in the meantime you see a zombie process, but

Re: Maintaining implementations of similar utility functions like json-fetch

Hi Ludo', 2018-01-27 17:09 GMT+01:00 Ludovic Courtès <l...@gnu.org>: > Hello! > > Jelle Licht <jli...@fsfe.org> skribis: > > > I noticed that there are currently two very similar functions for > fetching > > json data; `json-fetch' in (guix import json

Re: Dinner in Brussels?

Me and Michiel would also like to be there on Friday. 2018-01-30 14:20 GMT+01:00 Amirouche Boubekki : > In for dinner on Friday. > > Le 30 janv. 2018 2:11 PM, "Gábor Boskovits" a > écrit : > >> 2018-01-30 14:09 GMT+01:00 Julien Lepiller

Re: Improving Shepherd

2018-01-29 22:14 GMT+01:00 Carlo Zancanaro : > I'm keen to do some work on shepherd. Partially this is driven by me using > it to manage my user session and having it not always work right, and > partially this is driven by me grepping the code for "FIXME" (which was >

Maintaining implementations of similar utility functions like json-fetch

Hello! I noticed that there are currently two very similar functions for fetching json data; `json-fetch' in (guix import json) and `json-fetch*' in (guix import github). Some things I noticed: - Dealing with http error codes seems to be a bit more robust in `json-fetch*'. - Making sure that

Re: [RFC] A simple draft for channels

2018-01-19 9:24 GMT+01:00 Ricardo Wurmus : > Hi Guix, > > I’d like to retire GUIX_PACKAGE_PATH as the main way to get third-party > packages, because we can’t really keep track of packages that were added > or redefined in this way. I want to replace it with

Re: license naming

ng0 writes: > I've just read this link: > https://www.fsf.org/blogs/rms/rms-article-for-claritys-sake-please-dont-say-licensed-under-gnu-gpl-2 > > Full Quote: > >> In this article, For Clarity's Sake, Please Don't Say "Licensed under GNU >> GPL 2"!, Free Software Foundation

Re: Dualbooting with guixsd not handling grub installation

2017-12-10 0:35 GMT+01:00 Martin Castillo : > Hi guixers, > > I want to dualboot into GuixSD. My main os is currently NixOS. > Currently, I don't want to let guixsd control my grub setup. So my > situation is similar to [1]. > > One solution is to use the unreliable

Re: Automatically checking commit messages

2017-09-20 17:47 GMT+02:00 Arun Isaac : > > I have been working on a guile script to automatically check commit > messages -- something like `guix lint' but for commit messages instead > of package definitions. This could help us enforce our commit message > guidelines

Re: collaboration from students of a technical school

It could also be interesting to have the more software-engineering/devops focused students look at improving guix QA process. They could work on technical solutions for making things more robust, as to make sure `master' is broken less often ;-). I have no specific ideas on how to approach this

Re: npm (mitigation)

2017-07-15 5:34 GMT+02:00 Mike Gerwitz <m...@gnu.org>: > On Fri, Jul 14, 2017 at 13:57:30 +0200, Jelle Licht wrote: > > Regardless, the biggest issue that remains is still that npm-land is > mired > > in cyclical dependencies and a fun-but-not-actually unique depende

Re: npm (mitigation)

Hi Catonano, I would be be happy to help you with this, but tbh, I am not comfortable discussing this in-depth on guix-devel, as this seems antithetical to Guix' goals. All I will say here is that you need to adapt the npm importer to use the sources from the npm registry instead of resolving to

Re: On merging the npm importer

2017-03-29 19:39 GMT+02:00 Christopher Allan Webber : > Jan Nieuwenhuizen writes: > > > Hi, > > Hi Jan! > Hello Jan and Christopher! > > > We have a working importer for npm packages written by Jelle that I have > > been using for about half a year. It can use some

[PATCH] gnu: node: Update to 7.8.0.

Hi, Attached you will find a (simple) patch to update Node.js to the latest released version. Regards, jlicht From fe46d754e61c776e46d59f72f5fc2bed5a0a177e Mon Sep 17 00:00:00 2001 From: Jelle Licht <jli...@fsfe.org> Date: Thu, 30 Mar 2017 15:57:59 +0200 Subject: [PATCH] gnu: node:

[PATCH] gnu: Add libtorrent-rasterbar.

/packages/bittorrent.scm +++ b/gnu/packages/bittorrent.scm @@ -5,6 +5,7 @@ ;;; Copyright © 2016, 2017 Efraim Flashner <efr...@flashner.co.il> ;;; Copyright © 2016 Tomáš Čech <sleep_wal...@gnu.org> ;;; Copyright © 2016 Tobias Geerinckx-Rice <m...@tobias.gr> +;;; Copyright © 201

Re: jquery 3.1.1

umanitiesNerd/Culturia > > One last fun fact: while I was watching the output flowing in my terminal, > I saw a package called > > "broccoli-funnel" > > No, really. It's here > https://registry.npmjs.org/broccoli-funnel > > Ok, that's all for now. > Thanks again for your efforts on this. I am looking forward to working with your data. Regards, Jelle Licht

Re: NPM and trusted binaries

Just a quick note from me; AFAIK, the http module is a built-in of node, so you can probably save yourselves the efforts of packaging it ;-). Furthermore, lots of development dependencies are not strictly necessary; e.g. a minifier/uglifier is not required for most functionality of a package,

Re: GSoC NPM

the choice to skip the npm tarball because I'd rather err on the side of caution, and not let people download and run these non-source packages by accident ;-). I will have more time to see this through next week. - Jelle 2016-09-02 16:24 GMT+02:00 Jan Nieuwenhuizen <jann...@gnu.org>: &

Re: [PATCH 3/4] gnu: node: Do not use bundled dependencies.

2016-08-27 22:38 GMT+02:00 Alex Kost <alez...@gmail.com>: > Jelle Licht (2016-08-27 14:23 +0300) wrote: > > > The Node build system was previously building its own copies of > > C-ares and http-parser. > > > > * gnu/packages/node.scm (node)[inputs]: Add c-

Re: GSoC NPM

Hi Ricardo Wurmus writes: > Hi > >> I also took both Ludovic', as well as Catonano's detailed feedback on the >> initial draft of the recursive importer into account when rewriting it. It >> should now only visit each node in the dependency graph once, and be a >>

[PATCH 4/4] gnu: node: Use compression: prefix.

* gnu/packages/node.scm (define-module): Import gnu packages compression with a prefix (node): Likewise. --- gnu/packages/node.scm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gnu/packages/node.scm b/gnu/packages/node.scm index 7c020e6..351e988 100644 ---

[PATCH 3/4] gnu: node: Do not use bundled dependencies.

The Node build system was previously building its own copies of C-ares and http-parser. * gnu/packages/node.scm (node)[inputs]: Add c-ares and http-parser. [arguments]: Add configure flags for using system libraries. --- gnu/packages/node.scm | 7 ++- 1 file changed, 6 insertions(+), 1

[PATCH 2/4] gnu: node: Add search path specification for 'NODE_PATH'.

* gnu/packages/node.scm (node)[native-search-paths]: New field. --- gnu/packages/node.scm | 4 1 file changed, 4 insertions(+) diff --git a/gnu/packages/node.scm b/gnu/packages/node.scm index 545..d1c5e1b 100644 --- a/gnu/packages/node.scm +++ b/gnu/packages/node.scm @@ -151,6 +151,10

[PATCH 1/4] gnu: node: Add http-parser.

* gnu/packages/node.scm (http-parser): New variable. * gnu/packages/node.scm (define-module): Import gnu packages tls with tls: prefix --- gnu/packages/node.scm | 39 +-- 1 file changed, 37 insertions(+), 2 deletions(-) diff --git a/gnu/packages/node.scm

[PATCH 0/4] Unbundle node dependencies patch series

These patches allow us to make use of the existing c-ares package, as well as an unbundled version of http parser. Jelle Licht (4): gnu: node: Add http-parser. gnu: node: Add search path specification for 'NODE_PATH'. gnu: node: Do not use bundled dependencies. gnu: node: Use compression

[PATCH] gnu: node: Update to 6.4.0.

/2016-08/msg00816.html >From 9765c88b70f03fdee8a1ac5c55de3b7a34af7fad Mon Sep 17 00:00:00 2001 From: Jelle Licht <jli...@fsfe.org> Date: Fri, 5 Aug 2016 12:51:15 +0200 Subject: [PATCH] gnu: node: Update to 6.4.0. To: guix-devel@gnu.org Remove <https://debbugs.gnu.org/23744

GSoC NPM

to identify them. I probably forgot quite some important and unimportant details, so if you have any questions, tips or just want to blame me for getting more messy JavaScript into guix-land, send me a mail ;-). - Jelle Licht [0] https://lists.gnu.org/archive/html/guix-devel/2016-07/msg01726.html [1

Re: node FTBFS

Hi Alex, The patch I supplied at [0] seems to not have these issues: - It builds (yay) - That particular test seems run successfully Some other tests had to be disabled, but this was mostly due to constraints of the build environment. Thanks, Jelle [0]:

[PATCH] gnu: jq: Fix CVE-2015-8863.

Hello, Attached patch backports the commit[0] for jq that fixed the vulnerability referred to as CVE-2015-8863[1]. Some feedback would be welcome. - Jelle >From cbd181ae84003bf3cf4a2d15f44b5242dcc97860 Mon Sep 17 00:00:00 2001 From: Jelle Licht <jli...@fsfe.org> Date: Thu, 11 Aug 2016

Re: [PATCH v2] gnu: node: Update to 6.3.1.

Leo Famulari <l...@famulari.name> writes: > On Sun, Aug 07, 2016 at 02:45:20PM +0200, Jelle Licht wrote: >> Leo Famulari <l...@famulari.name> writes: >> >> - (replace 'patch-shebangs >> >> - (lambda* (#:key outputs #:allow-other

Re: [PATCH] python-kivy and Adobe source-code-pro font

Dylan Jeffers writes: > Hi all, > Hello Dylan, Thanks for this patch! I love the source-code-pro font :). > First patch to guix-devel; tried my best to conform to the guidelines. Guix (usually) has a one commit per change policy. Contributions in guix usually

Re: [PATCH v2] gnu: node: Update to 6.3.1.

Leo Famulari <l...@famulari.name> writes: > On Fri, Aug 05, 2016 at 01:02:45PM +0200, Jelle Licht wrote: >> ;; FIXME: These tests fail in the build container, but they >> don't >> ;; seem to be indicative of real problems in practice.

[PATCH v2] gnu: node: Update to 6.3.1.

* gnu/packages/node.scm (node): Update to 6.3.1. --- gnu/packages/node.scm | 32 ++-- 1 file changed, 14 insertions(+), 18 deletions(-) diff --git a/gnu/packages/node.scm b/gnu/packages/node.scm index 887ef93..4c98799 100644 --- a/gnu/packages/node.scm +++

Re: [PATCH] gnu: node: Update to 6.3.1

Please disregard this patch, I was a wee bit impatient with trying out git send-mail - Jelle 2016-08-05 12:28 GMT+02:00 Jelle Licht <jli...@fsfe.org>: > * gnu/packages/node.scm (node): Update to 6.3.1. > --- > gnu/packages/node.scm | 35 --- &g

[PATCH] gnu: node: Update to 6.3.1

* gnu/packages/node.scm (node): Update to 6.3.1. --- gnu/packages/node.scm | 35 --- 1 file changed, 16 insertions(+), 19 deletions(-) diff --git a/gnu/packages/node.scm b/gnu/packages/node.scm index 887ef93..f62555e 100644 --- a/gnu/packages/node.scm +++

Re: License auditing

Something like this could be quite convenient. The following spdx->guix license symbol converter might save you some time: http://paste.lisp.org/display/322105 - Jelle 2016-08-03 19:55 GMT+02:00 Danny Milosavljevic : > On Wed, 3 Aug 2016 18:28:38 +0200 > David Craven

Re: Rust

I looked into this once; I found a Rust compiler written in OCaml on the web. There should be a path from that compiler to the current version of Rust. The problem lies in the fact that the entire "1.9 build 1.10 builds 1.11" spiel only become the official policy of the Rust project recently.

Re: [GSoC update] Npm & guix

Quick reply from my phone, but thanks for the feedback. On Jul 29, 2016 16:53, "Catonano" <caton...@gmail.com> wrote: > 2016-07-25 23:26 GMT+02:00 Ludovic Courtès <l...@gnu.org>: > >> Hello! >> >> Jelle Licht <jli...@fsfe.org> skribis: >

[GSoC update] Npm & guix

Hello Guix! After hopefully enough contemplation and a lot of elbow grease, I would like to give you an overview of what I have been up to these past weeks. To start off with something that might make some people less than happy; jQuery and its dependencies will most likely not be packaged this

Re: [PATCH] gnu: wxwidgets-2: Update to upstream's re-release of 2.8.12.

Hello guix, Shamelessly stole most of this from Efraim, as wxwidgets had the same problem. Lets hope that it's just a couple of packages on SourceForge that have been changed in place. Jelle 2016-07-22 15:59 GMT+02:00 Jelle Licht <jli...@fsfe.org>: > * gnu/packages/wxwidgets.scm (wx

[PATCH] gnu: wxwidgets-2: Update to upstream's re-release of 2.8.12.

* gnu/packages/wxwidgets.scm (wxwidgets-2): Add a guix revision number to the version scheme of wxwidgets-2 to force an update. --- gnu/packages/wxwidgets.scm | 54 +- 1 file changed, 29 insertions(+), 25 deletions(-) diff --git

Re: [PATCH] gnu: node: Correctly patch npm shebang.

Jelle Licht <jli...@fsfe.org> writes: > * gnu/packages/node.scm (node): Correctly patch npm shebang. > --- > gnu/packages/node.scm | 6 ++ > 1 file changed, 6 insertions(+) > > diff --git a/gnu/packages/node.scm b/gnu/packages/node.scm > index 2f269d0..2cedda8

[PATCH] gnu: node: Correctly patch npm shebang.

* gnu/packages/node.scm (node): Correctly patch npm shebang. --- gnu/packages/node.scm | 6 ++ 1 file changed, 6 insertions(+) diff --git a/gnu/packages/node.scm b/gnu/packages/node.scm index 2f269d0..2cedda8 100644 --- a/gnu/packages/node.scm +++ b/gnu/packages/node.scm @@ -51,8 +51,14 @@

Re: CFP: GNU Hacker Meeting 2016

Efraim Flashner writes: > On Sun, Jun 05, 2016 at 02:59:56PM +0200, Ludovic Courtès wrote: >> Hello Guix! >> >> Now is the time to register for the GNU Hackers Meeting! The more, the >> merrier! >> >> https://gnunet.org/ghm2016 >>

[GSoC] Integrating npm into the Guix ecosystem

Greetings Guix hackers, It has been some time since my last mail to this list, so I wanted to share what I have been up to. For the people who might want to watch along after today, I will be posting the changes that should not break everything immediately to [1]. (Apologies for it being

  1   2   >