Re: Auto-install EFI / BIOS bootloader

> (Hybrid MBR/GPT are "dangerous" because they have to be updated in lock-step) Oops, correction: GPT always has a dummy MBR partition table which marks everything as "used". So the MBR will not be updated further. Grub2 will use GPT (if available) both in the EFI and in the non-EFI case. pgp4

Re: Auto-install EFI / BIOS bootloader

Hi Pierre, > From there, why wouldn't Guix do that automatically for use? In practise UEFI likes to fake a lot of stuff. It can happen that /sys/firmware/efi exists but the system cannot *boot* via EFI. Likewise, /sys/firmware/efi can vanish just because you booted from CD using UEFI's BIOS fal

Re: Current state of cargo-build-system

Hi Ivan, On Sun, 20 Jan 2019 16:11:58 -0800 Ivan Petkov wrote: > Are there any philosophical or technical blockers that preclude pulling in > packages from crates.io, Cycles. Also, often Cargo.lock specifies exact versions of dependencies (in programs, at least). >or is it just a matter of c

Re: defining core modules

Hi, On Mon, 28 Jan 2019 11:51:53 +0100 Ludovic Courtès wrote: > I support the idea; I’m not entirely sure about the core/ name space but > that’s a secondary issue. I support the idea, too. > It may prove to be tricky though. For example, the set of dependencies > of GCC has been steadily gro

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Ludo, > while reading from child process ^ Is that a real Pentium, or qemu on x86_64? We had some problems with spawning child processes on the qemu transparent emulator. pgphnzPYl3GKD.pgp Description: OpenPGP digital signature

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Ludo, on second thought: On Mon, 28 Jan 2019 15:39:33 +0100 Ludovic Courtès wrote: > > /gnu/store/fw4yy7cgb5ahs9s2ir00bawnsl5zj7db-mrustc-0.8.0/bin/mrustc[...] > munmap_chunk(): invalid pointer Maybe the above causes > src/tools/cargo/src/crates-io/lib.rs:65: BUG:src/expand/proc_macro.cpp:9

Re: Rust 1.19 fails to build on i686 on ‘staging’

Possible use-after free fix in mrustc commits: https://github.com/thepowersgang/mrustc/commit/a51eea542ae086687ea2c4cb09321785f5cc6269 This was not in the mrustc 0.8.0 release yet. pgp12KN34YAvz.pgp Description: OpenPGP digital signature

Re: Rust 1.19 fails to build on i686 on ‘staging’

Something more serious seems to be up with guix staging because I get, on trying "make" (after "./configure --localstatedir=/var") inside guix staging (commit df09e1d6e71f68a8fb44bcc9f13e625f9f9701a5) on x86_64: Backtrace: In ice-9/boot-9.scm: 222:29 19 (map1 _) 222:29 18 (map1 _) 222:29

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Ricardo, On Mon, 28 Jan 2019 19:41:50 +0100 Ricardo Wurmus wrote: > Did you run “make clean-go” before? Nope. Did so now - the build of guix staging works now. Thanks! pgpaROXXhhog4.pgp Description: OpenPGP digital signature

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Ludo, running gdb in an i686 transparent qemu emulation gives me: $ gdb --args /gnu/store/gpc2m2f79rsgy15m65x0s5av7a41rp8b-mrustc-0.8.0/bin/mrustc src/tools/cargo/src/crates-io/lib.rs --crate-name crates_io --crate-type rlib --crate-tag 0_9_0 -g --cfg debug_assertions -O -o output/cargo-bu

Re: Rust 1.19 fails to build on i686 on ‘staging’

Chris and I compared what gets sent by the parent on i686 (where it breaks) vs on x86_64 (where it doesn't break): There are no differences. The next step will be to find out what the child process does with the data. I suspect that the child processes' input deserializer is broken. For referenc

Re: Issue with my version of guix

Hi Laura, On Fri, 8 Feb 2019 12:25:41 -0300 Laura Lazzati wrote: > This is the output of my guix --version, which shows a commit. > guix --version > guix (GNU Guix) 9d58e8819fdbc4c1c8a1ef6149e2d2376731a6a6 > Copyright (C) 2019 the Guix authors This commit seems to be very recent, so not sure wh

Re: Issue with my version of guix

Hi Laura, On Fri, 8 Feb 2019 16:22:08 -0300 Laura Lazzati wrote: > Weirdest, look at this: > guix-daemon (GNU Guix) 0.16.0-3.6ddc63e > root@ada:~# /proc/$(pidof -s guix-daemon)/exe -V > guix-daemon (GNU Guix) 0.15.0-8.71a78ba Yeah, I think Guix on GuixSD uses the guix-daemon from the package "g

Re: GDM update!

Hi Ludo, https://github.com/GNOME/gdm/commit/0bb8a777cfc0a3bc53c2c2830dd7e6e2baeeef38#diff-9b802b1ffb5f0ff95bfaa85046d262e7 says: >custom is a magic name we used to allow for having the user decide their >session by a ~/.xsession file. We no longer support that construct and >haven't for many

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Chris, upstream says that compiling rust 1.19.0 works fine for them on i686 with their mrustc master (since they have applied our variable-length integer decoding patch): https://github.com/thepowersgang/mrustc/issues/108 >Hmm... works for me, using gcc (Debian 6.3.0-18+deb9u1) 6.3.0 2017051

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Chris, On Tue, 12 Feb 2019 03:47:53 -0800 Chris Marusich wrote: > > Would you have some time and a free computer to be able to build rust > > 1.19.0 with > > > > ./pre-inst-env guix build -K -s i686-linux rust@1.19.0 > > > > on guix master with the patch below? > > I have a spare compu

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Chris, On Wed, 13 Feb 2019 20:35:51 -0800 Chris Marusich wrote: > My understanding is that "term-signal: 8" means the process (rustc) was > terminated by signal 8 (SIGFPE on my system according to "kill -l"). Is > that right? According to upstream [1], it might be SIGABRT, but I see your re

Re: problem with dockerd service

Hi Giovanni, On Thu, 14 Feb 2019 18:27:03 +0100 Giovanni Biscuolo wrote: > I'm trying to create a VM with a dockerd service installed > > I'm using the same configuration as the one used in this bug #34333 > http://issues.guix.info/issue/34333 > except I removed gfs package gnome and desktop se

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Chris, On Fri, 15 Feb 2019 01:11:02 -0800 Chris Marusich wrote: > Here's more info about what I did. On my x86_64-linux Guix System > machine, where the build failed, I ran the following commands: > > --8<---cut here---start->8--- > cd /tmp/guix-build-rus

[PATCH 1/3] gnu: python-simplejson: Update to 3.10.0.

* gnu/packages/python.scm (python-simplejson): Update to 3.10.0. --- gnu/packages/python.scm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm index 83ef372..418a644 100644 --- a/gnu/packages/python.scm +++ b/gnu/packages/pyth

[PATCH 0/3] Update Flask & co

Danny Milosavljevic (3): gnu: python-simplejson: Update to 3.10.0. gnu: python-pyopenssl: Update to 16.2.0. gnu: python-flask: Update to 0.11.1. gnu/packages/python.scm | 14 -- 1 file changed, 8 insertions(+), 6 deletions(-)

[PATCH 2/3] gnu: python-pyopenssl: Update to 16.2.0.

* gnu/packages/python.scm (python-pyopenssl): Update to 16.2.0. --- gnu/packages/python.scm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm index 418a644..ad27934 100644 --- a/gnu/packages/python.scm +++ b/gnu/packages/pytho

[PATCH 3/3] gnu: python-flask: Update to 0.11.1.

* gnu/packages/python.scm (python-flask): Update to 0.11.1. [native-inputs]: Add python-click. --- gnu/packages/python.scm | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm index ad27934..497da52 100644 --- a/gnu/packages/py

[PATCH v2 0/4] Update Flask & co

Danny Milosavljevic (4): gnu: python-simplejson: Update to 3.10.0. gnu: python-pyopenssl: Update to 16.2.0. gnu: python-flask: Update to 0.11.1. gnu: python2-flask: Pick up python-flask's native-inputs. gnu/packages/python.scm | 22 +- 1 file changed, 13 inser

[PATCH v2 1/4] gnu: python-simplejson: Update to 3.10.0.

* gnu/packages/python.scm (python-simplejson): Update to 3.10.0. --- gnu/packages/python.scm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm index 83ef372..418a644 100644 --- a/gnu/packages/python.scm +++ b/gnu/packages/pyth

[PATCH v2 2/4] gnu: python-pyopenssl: Update to 16.2.0.

* gnu/packages/python.scm (python-pyopenssl): Update to 16.2.0. --- gnu/packages/python.scm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm index 418a644..ad27934 100644 --- a/gnu/packages/python.scm +++ b/gnu/packages/pytho

[PATCH v2 4/4] gnu: python2-flask: Pick up python-flask's native-inputs.

* gnu/packages/python.scm (python2-flask)[native-inputs]: Pick up python-flask's native-inputs. --- gnu/packages/python.scm | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm index 497da52..39b40e7 100644 --- a/gnu/packag

[PATCH v2 3/4] gnu: python-flask: Update to 0.11.1.

* gnu/packages/python.scm (python-flask): Update to 0.11.1. [native-inputs]: Add python-click. --- gnu/packages/python.scm | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm index ad27934..497da52 100644 --- a/gnu/packages/py

Re: [PATCH 2/3] gnu: yosys: Add xdot functionality.

LGTM.

Re: [PATCH] gnu: python-pip: Update to 9.0.1

Hi, On Mon, 28 Nov 2016 17:08:49 -0800 Maxim Cournoyer wrote: > (inputs > - `(("python-setuptools" ,python-setuptools) > -("python-virtualenv" ,python-virtualenv) > -;; Tests > -("python-mock" ,python-mock) > -("python-pytest" ,python-pytest) > -

Re: New python build system merged

Hi, > There is still at least one new failure, borg. Are there more? If so, we > should revert the changes until they are ready. I think it depends on how much work fixing them is. If it were just five minutes then I'd say leave it in master and fix the packages that failed. Otherwise revert.

Re: [Patch v2] daemon: Set ownership of kept build directories to the calling user.

Hi Hartmut, On Mon, 28 Nov 2016 22:31:44 +0100 Hartmut Goebel wrote: > I just need some C programming hint: uid_t is an unsigned int, so > comparing with -1 raises a warning (which IMO is the same as en error). The system call handler in the Linux kernel does this, among other things: #define l

[PATCH] gnu: python-flask: Make python-click a propagated-input.

* gnu/packages/python.scm (python-click)[native-inputs]: Move to ... [propagated-inputs]: ... here. --- gnu/packages/python.scm | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm index 8f8b0de72..9c3902c3e 100644 --- a/gnu/p

Re: [PATCH] gnu: Add openfwwf-firmware.

On Wed, 16 Nov 2016 21:29:18 -0600 Eric Bavier wrote: > + "This is firmware from Open FirmWare for WiFi networks (OpenFWWF) for > the > +Broadcom/AirForce chipset BCM43xx with Wirelss-Core Revision 5. It is used > by ^ Wirelss-Core ? Is it real

Re: [PATCH v3] daemon: Set ownership of kept build directories to the calling user.

Hi Hartmut, > +#if defined(SO_PEERCRED) ... > +#else > +/* Setting these to -1 means: do not change */ > +settings.clientUid = -1; > +settings.clientGid = -1; > +#endif I think you also have to cast them there, so settings.clientUid

[PATCH] gnu: Add python-sadisplay.

* gnu/packages/python.scm (python-sadisplay): New variable. --- gnu/packages/python.scm | 23 +++ 1 file changed, 23 insertions(+) diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm index d62422964..68c66b4ea 100644 --- a/gnu/packages/python.scm +++ b/gnu/packages/

Re: [PATCH 2/3] gnu: Add python-argcomplete.

On Wed, 7 Dec 2016 04:22:27 +0100 Tobias Geerinckx-Rice wrote: > On 07/12/16 04:19, Tobias Geerinckx-Rice wrote: > > * gnu/packages/python.scm (argcomplete): New variable. > > s/argcomplete/python-argcomplete/ :-) > LGTM (with the name change).

[PATCH] gnu: python-sqlalchemy-utils: Update to 0.32.11.

* gnu/packages/python.scm (python-sqlalchemy-utils): Update to 0.32.11. --- gnu/packages/python.scm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm index 8fe3d36d0..3d938ccc1 100644 --- a/gnu/packages/python.scm +++ b/gnu/pa

[PATCH] gnu: Add python-flask-restful-swagger.

* gnu/packages/python.scm (python-flask-restful-swagger, python2-flask-restful-swagger): New variables. --- gnu/packages/python.scm | 24 1 file changed, 24 insertions(+) diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm index f61c64623..d642dc672 100644 --

[PATCH] gnu: sunxi-tools: Update to 1.4.2.

* gnu/packages/admin.scm (sunxi-tools): Update to 1.4.2. --- gnu/packages/admin.scm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gnu/packages/admin.scm b/gnu/packages/admin.scm index 2079bf9e0..69c04dc13 100644 --- a/gnu/packages/admin.scm +++ b/gnu/packages/admin.scm @@

Re: [PATCH 6/6] gnu: Add grub-efi.

Did you add (grub grub-efi) in your in your system config? Or another package with --with-platform=efi ?

Re: BOA

Hi, On Sun, 18 Dec 2016 15:30:20 + Echedey López Romero wrote: > I would like know when you are going to add this program Heh. Well I had some spare time so I tried to package boa 0.94.13. Unfortunately I get a compilation error: util.c: In function ‘get_commonlog_time’: util.c:100:39: e

Re: [PATCH 01/11] gnu: Add python-flask-wtf.

Since flask-WTF directly imports flask, this package should also propagate flask.

Re: [PATCH] gnu: Fix load-extension path in packaging of guile-ncurses.

> Sure (I would like to see a convention where such explanations are > put in the commit messaage, but I have previously been outvoted on > that issue): No, please don't put explanations into the commit message. But do put them into the source code as a comment. I'm also working on other project

Re: [PATCH 6/6] gnu: Add grub-efi.

Hi, efibootmgr is trying to add an entry for Linux to the EFI bootmanager and set the boot priority order. It won't usefully autoboot without it. That said, depending on how good the UEFI implementation on your laptop is you might be able to hit a function key on POST and select the image file

Re: [PATCH v4] daemon: Set ownership of kept build directories to the calling user.

On Fri, 23 Dec 2016 14:33:31 +0100 John Darrington wrote: > On Fri, Dec 23, 2016 at 12:18:11PM +0100, Vincent Legoll wrote: > Hello, > > +// Change the ownership if clientUid is set. Never change > the > +// ownership or the group to "root" for securi

Re: Trouble setting up hplip and cups - printer ppd fails

Hi, On Sat, 24 Dec 2016 14:08:44 + ng0 wrote: > > Traceback (most recent call last): > > File > > "/gnu/store/95vp3r6n9z7s85achc7a0b8aay1k73qq-hplip-3.16.11/share/hplip/setup.py", > > line 560, in > > desc = nickname_pat.search(nickname).group(1) > > TypeError: cannot use a string p

Icecat crash

Hi, so I've finally found a 100% reproducible way to crash icecat. Previously it has been sporadic and not reproducible. Try going to this site in a new icecat (guix master) instance: http://arstechnica.com/security/2016/12/this-low-cost-device-may-be-the-worlds-best-hope-against-account-takeov

Re: [PATCH v4] daemon: Set ownership of kept build directories to the calling user.

Hi, On Sat, 24 Dec 2016 13:34:16 +0100 Hartmut Goebel wrote: > The "magic value" for gid is -1, too, as you can see in > nix/nix-daemon/nix-daemon.cc. > > gid 0 is not used as a magic value. As you can read in the comment, the > test just prohibits changing the group to "root": > > setting

rust: Crate Dependencies

Hi, I'm trying Rust out for a bit and for that I added some Crates. (using David's v2 patches as a base) Right now I'm stuck at rust-c-vec which I tried to add myself. I get: starting phase `unpack' c_vec-1.1.0/.travis.yml c_vec-1.1.0/Cargo.toml c_vec-1.1.0/LICENSE-APACHE c_vec-1.1.0/LICENSE-MI

Re: rust: Crate Dependencies

Hi David, On Thu, 29 Dec 2016 11:49:19 +0100 David Craven wrote: > It matters very > much which versions of rustc and cargo are used I used the versions in your v2 patch. I also tried ng0's update which didn't improve things. How does rustc find the (Rust) dependencies when building a package

Re: [PATCH] gnu: hplip: Add qt5 gui.

Hi, > + "--enable-dbus-build" >;; TODO: Make hp-setup find python-dbus. Does that mean that dbus now works in hp-setup?

Re: [PATCH 02/12] build-system: Add cargo build system.

Hi, when I use git-download, the files it checked out will have r-- permissions and thus cargo-build-system can't patch Cargo.toml . To reproduce, try: (define-public rust-c-vec (package (name "rust-c-vec") (version "1.1.0") (source (origin (method git-fetch) (uri (git-re

Guix build side - including modules (guix hash), (guix gcrypt): How to provide shared library?

Hi, how can I use (guix hash) on the build side? It requires the libgcrypt shared library and that's not available on the build side...

Re: Getting rid of "source file .. newer than compiled" messages

Hi, On Mon, 2 Jan 2017 13:40:47 +0100 Hartmut Goebel wrote: > Hi, > > when developing packages, esp. when switching branches, I get lots of > messages like this: > > ;;; note: source file …/guix/gnu/packages/tor.scm > ;;; newer than compiled …/guix/gnu/packages/tor.go > > How can I get

Re: Guix build side - including modules (guix hash), (guix gcrypt): How to provide shared library?

Hi David, On Mon, 2 Jan 2017 11:06:27 +0100 David Craven wrote: > > how can I use (guix hash) on the build side? It requires the libgcrypt > > shared library and that's not available on the build side... > > Depends. For a one off package I'd add it to native-inputs. Otherwise > you can crea

Re: [PATCH 11/12] gnu: Add rust-rand.

This is missing a native-input rust-log for the tests.

cargo-build-system: cargo-build-flags: --cfg=unix in package recipe

Hi, so it seems I got the cargo-build-system to work for large-ish Rust dependency trees now. It still can't pick up transitive dependencies but hey :P However, some of the Rust crates have a "windows" target which fails. For these I'd like to pass "--cfg=unix" and I'd like to put it into the p

Re: cargo-build-system: cargo-build-flags: --cfg=unix in package recipe

It was missing in guix/build-system/cargo.scm cargo-build as a keyword parameter. Adding (define* (cargo-build store name inputs #:key (tests? #t) (test-target #f) - (configure-flags #f) +

Re: cargo-build-system: cargo-build-flags: --cfg=unix in package recipe

> It still can't pick up transitive dependencies but hey :P Aha! It can - if one uses propagated-inputs in the package recipes. I think the importer should propagate inputs if the current package is Rust-source-only. Otherwise packages further down the dependency graph (further to the clients)

[PATCH] build-system: cargo: Add #:cargo-build-flags keyword argument.

* guix/build-system/cargo.scm (cargo-build): Add #:cargo-build-flags keyword argument. --- guix/build-system/cargo.scm | 2 ++ 1 file changed, 2 insertions(+) diff --git a/guix/build-system/cargo.scm b/guix/build-system/cargo.scm index ffc0afda3..011ea9c57 100644 --- a/guix/build-system/cargo.sc

[PATCH] build-system: cargo: Remove obsolete comment.

* guix/build/cargo-build-system.scm (%standard-phases): Remove obsolete comment. --- guix/build/cargo-build-system.scm | 1 - 1 file changed, 1 deletion(-) diff --git a/guix/build/cargo-build-system.scm b/guix/build/cargo-build-system.scm index 7d656a8d5..1c0064ed4 100644 --- a/guix/build/cargo-

[PATCH v2] build-system: cargo: Add #:cargo-build-flags keyword argument.

* guix/build-system/cargo.scm (cargo-build): Add #:cargo-build-flags keyword argument. --- guix/build-system/cargo.scm | 2 ++ 1 file changed, 2 insertions(+) diff --git a/guix/build-system/cargo.scm b/guix/build-system/cargo.scm index ffc0afda3..011ea9c57 100644 --- a/guix/build-system/cargo.sc

WIP patch: build-system: cargo: Make lots and lots of rust packages work

For it to work, you also have to back out the (cons "src" outputs) (in ./guix/build-system/cargo.scm) and the (assoc-ref outputs "src") (in guix/build/cargo-build-system.scm) starting from current master. --- guix/build/cargo-build-system.scm 2017-01-03 04:31:01.691543854 +0100 +++ /home/danny

Re: WIP patch: build-system: cargo: Make lots and lots of rust packages work

Hi David, On Tue, 3 Jan 2017 12:08:56 +0100 David Craven wrote: > Can you elaborate on why you think it's a bad idea to separate the > source from the binaries into different outputs? Huh? I think it's a good idea. It just doesn't work yet and I didn't find out why :) > I see that you are try

Re: cargo-build-system: cargo-build-flags: --cfg=unix in package recipe

On Tue, 3 Jan 2017 11:57:48 +0100 David Craven wrote: > > For these I'd like to pass "--cfg=unix" and I'd like to put it into the > > package recipe and not hardcode it into the build system. > > Nice, didn't know about this flag. That explains why it refused to > build without the windows de

Re: WIP patch: build-system: cargo: Make lots and lots of rust packages work

> > Can you elaborate on why you think it's a bad idea to separate the > > source from the binaries into different outputs? > > Huh? I think it's a good idea. It just doesn't work yet and I didn't find out > why :) Hmm I think I would have to update all my imported crates' package recipes to

Re: cargo-build-system: cargo-build-flags: --cfg=unix in package recipe

Hi ng0, On Tue, 03 Jan 2017 11:19:55 + ng0 wrote: > It does indeed, and this would fix the bug I filed. > I've cut down the number of crates I packaged from 160 to 81 just > by removing the *32-sys and winapi dependencies after reading a > bit about the system. Just a heads-up, if there's a

Re: [PATCH] gnu: doxygen: Use sh from the store.

Thanks for the patch! Looks good to me. In any case, if we search for "portable_system", we find that there are lots of other things that don't use in-store names: ./cite.cpp: if ((exitCode=portable_system("perl","\""+bib2xhtmlFile+"\" "+bibOutputFiles+" \""+ ./dia.cpp: if ((exitCode=portable

Re: [PATCH 1/4] gnu: Use 'license:' prefix in (gnu packages ocaml).

LGTM!

Re: cargo-build-system: cargo-build-flags: --cfg=unix in package recipe

Hi David, On Tue, 3 Jan 2017 11:57:48 +0100 David Craven wrote: > > Aha! It can - if one uses propagated-inputs in the package recipes. I think > > the importer should propagate inputs if the current package is > > Rust-source-only. Otherwise packages further down the dependency graph > > (fu

[PATCH] gnu: Add ghc-language-c.

* gnu/packages/haskell.scm (ghc-language-c): New variable. --- gnu/packages/haskell.scm | 27 +++ 1 file changed, 27 insertions(+) diff --git a/gnu/packages/haskell.scm b/gnu/packages/haskell.scm index 8e5927a00..ef6845056 100644 --- a/gnu/packages/haskell.scm +++ b/gnu/pa

Re: [PATCH 01/86] gnu: Add rust-libc.

> +(license (list license:expat license:asl2.0 Please clarify whether that means AND or OR in a comment. Other than that, OK!

Re: [PATCH 02/86] gnu: Add rust-spin.

>+(synopsis "Spin is a library which implements a simple spinlock") Just (synopsis "Simple spinlock") is enough. Maybe mention Rust? What do you think? > + "Synchronization primitives based on spinning. They may contain > +data, they are usable without `std` and static initializers are

Re: [PATCH 06/86] gnu: Add rust-log.

> +(license (list license:expat license:asl2.0 Please clarify whether that means AND or OR in a comment. Otherwise OK!

Re: [PATCH 10/86] gnu: Add rust-void.

> + "The uninhabited type, @code{enum Void { }} Hmm can texinfo actually process that?

Re: [PATCH 11/86] gnu: Add rust-slab.

OK! Maybe mention Rust in the summary?

Re: [PATCH 82/86] gnu: rust-quickcheck: Add rust-env-logger input.

On Tue, 3 Jan 2017 23:36:38 + ng0 wrote: > * gnu/packages/rust.scm (rust-quickcheck)[arguments]: Add rust-env-logger. > - ;; TODO: ("rust-env-logger" ,rust-env-logger "src") > + ("rust-env-logger" ,rust-env-logger "src") That causes a cycle rust-quickcheck - rust-env-logger - ru

Re: [PATCH 80/86] gnu: rust-csv: Add rust-regex input.

Cycle rust-csv - rust-regex - rust-aho-corasick - rust-csv.

Re: [PATCH 41/86] gnu: Add rust-fnv.

> +(license (list license:expat license:asl2.0 Please mention in a comment whether that means AND or OR.

Re: [PATCH 42/86] gnu: Add rust-heapsize.

OK!

Re: [PATCH 46/86] gnu: Add rust-term.

> +(license (list license:expat license:asl2.0 Please mention in a comment whether that means AND or OR. Otherwise OK!

Re: [PATCH 50/86] gnu: Add rust-strsim.

OK!

WIP v2: build-system: cargo: Make lots and lots of rust packages work

With minimal changes (bugfixes) compared to the last version... (see attachement) ;;; GNU Guix --- Functional package management for GNU ;;; Copyright © 2016 David Craven ;;; ;;; This file is part of GNU Guix. ;;; ;;; GNU Guix is free software; you can redistribute it and/or modify it ;;; unde

Re: [PATCH 53/86] gnu: Add rust-fs2.

When I compile it I get error[E0554]: #[feature] may not be used on the stable release channel --> src/lib.rs:1:19 | 1 | #![cfg_attr(test, feature(test))] | ^ error: aborting due to previous error error: Could not compile `fs2`. To learn more, run the command

Re: [PATCH 01/86] gnu: Add rust-libc.

Also, there are tests in https://github.com/rust-lang/libc/archive/0.2.18.tar.gz but not in the 0.2.18 crate. I haven't managed to run them successfully yet. It's supposed to work like this: $ cd libc-test $ cargo run I get Unknown error Permission denied. See also

Re: 77 Rust Crates, fluid, roboto-font, libpsyc rust bindings

Hi ng0, > > For those I checked (like rust-openssl-sys) left me in confusion. Does our > > cargo build-system just build nothing? Most Rust libraries are installed as source code (similar to C++ templates which are also installed as source code). The current Guix master cargo build system does

Re: cargo-build-system: cargo-build-flags: --cfg=unix in package recipe

I'm against packaging unstable stuff. We would be packaging a moving target where everything breaks every day. Let's not. There's a reason there are stable releases (of anything): there's (supposed to be) a (social) guarantee that the API doesn't change in incompatible ways. If a library doesn'

[PATCH] gnu: Add ghc-markdown-unlit.

* gnu/packages/haskell.scm (ghc-markdown-unlit): New variable. --- gnu/packages/haskell.scm | 33 + 1 file changed, 33 insertions(+) diff --git a/gnu/packages/haskell.scm b/gnu/packages/haskell.scm index de061a630..899a5b24c 100644 --- a/gnu/packages/haskell.scm ++

Re: [PATCH 2/3] gnu: Add fluid.

Hi, > + `(#:tests? #f)) ; 3 tests want a connection to the display. Please set the QT_QPA_PLATFORM environment variable. and let the tests run: (setenv "QT_QPA_PLATFORM" "offscreen") Or does this not work for some reason? Otherwise OK! P.S. What do you all think about putting that seten

Re: [PATCH] gnu: Add ldc-1.1.0-beta4

Hi, On Wed, 4 Jan 2017 17:01:14 +0300 Frederick Muriithi wrote: > Added ldc-1.1.0-beta4 since all other beta versions from there seem to > reuse the same phobos, druntime and dmd-testsuite. Thanks for the patch! Hmm, you added gdb to the native-inputs but commented out the gdb invocations lat

[PATCH v2] gnu: Add ghc-markdown-unlit.

* gnu/packages/haskell.scm (ghc-markdown-unlit): New variable. --- gnu/packages/haskell.scm | 29 + 1 file changed, 29 insertions(+) diff --git a/gnu/packages/haskell.scm b/gnu/packages/haskell.scm index de061a630..1f6611d0b 100644 --- a/gnu/packages/haskell.scm +++ b/

Re: [PATCH] gnu: econnman: Add missing input.

On Wed, 04 Jan 2017 10:27:42 +0100 Clément Lassieur wrote: > I don't have Enlightenment either. Without this input, I get this error > when I execute econnman-bin: Good enough for me. OK! I also tested it without the patch, where it failed as described, and with the patch, where it works.

Re: [PATCH] gnu: Add ldc-1.1.0-beta4

> Hmm, my understanding of how the package definitions work might be > incomplete: It seemed to me like after you inherited, from a package, > and then added a definition in any of the variables, the new variables > would NOT add to the values of the older ones but rather, they would > completely o

Re: [PATCH] gnu: Add ldc-1.1.0-beta4

On Wed, 4 Jan 2017 18:53:47 +0300 Frederick Muriithi wrote: > I tried that, but since dmd2/root/port.c file no longer exists, the > 'patch-dmd2 step causes the build to fail. That's the reason I decided > to just add the same things again, but without the 'patch-dmd2 step Ah, okay. I have no comp

[PATCH] gnu: Add corrode.

* gnu/packages/rust.scm (corrode): New variable. --- gnu/packages/rust.scm | 28 1 file changed, 28 insertions(+) diff --git a/gnu/packages/rust.scm b/gnu/packages/rust.scm index 97d0d7cb0..fa2806201 100644 --- a/gnu/packages/rust.scm +++ b/gnu/packages/rust.scm @@ -2

WIP v3: build-system: cargo: Make lots and lots of rust packages work

Now also uses "src" output. See attachment. ;;; GNU Guix --- Functional package management for GNU ;;; Copyright © 2016 David Craven ;;; ;;; This file is part of GNU Guix. ;;; ;;; GNU Guix is free software; you can redistribute it and/or modify it ;;; under the terms of the GNU General Public Li

[PATCH v4 0/3] Prepare for Sphinx update

This adds new packages that will be required for an eventual Sphinx update. Danny Milosavljevic (3): gnu: Add python-snowballstemmer. gnu: Add python-sphinx-cloud-sptheme. gnu: Add python-sphinx-alabaster-theme. gnu/packages/python.scm | 74

[PATCH v4 2/3] gnu: Add python-sphinx-cloud-sptheme.

* gnu/packages/python.scm (python-sphinx-cloud-sptheme, python2-sphinx-cloud-sptheme): New variables. --- gnu/packages/python.scm | 23 +++ 1 file changed, 23 insertions(+) diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm index 6589c59e3..e93e827de 100644 --- a

[PATCH v4 1/3] gnu: Add python-snowballstemmer.

* gnu/packages/python.scm (python-snowballstemmer, python2-snowballstemmer): New variables. --- gnu/packages/python.scm | 25 + 1 file changed, 25 insertions(+) diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm index 04cd3fa90..6589c59e3 100644 --- a/gnu/pac

<    1   2   3   4   5   6   7   8   9   10   >