Re: [PATCH 1/4] gnu: Add python-pytest-3.0.7

On Mon, Mar 27, 2017 at 11:09:24AM -0400, Leo Famulari wrote: > From f44c8d0dec2af7677ad16cfad877fb73407b6c30 Mon Sep 17 00:00:00 2001 > From: Leo Famulari > Date: Mon, 27 Mar 2017 03:10:53 -0400 > Subject: [PATCH] gnu: python-pytest-2.9.2: Replace with python-pytest-3.0. > >

Re: [PATCH 4/4] gnu: Add python-mando

On Sun, Mar 26, 2017 at 12:23:35PM +0300, Muriithi Frederick Muriuki wrote: > * gnu/packages/python.scm (python-mando): New variable. Pushed with a python2 variant, thanks!

Re: [PATCH 1/4] gnu: Add python-pytest-3.0.7

On Sun, Mar 26, 2017 at 12:23:32PM +0300, Muriithi Frederick Muriuki wrote: > * gnu/packages/python.scm (python-pytest-3.0.7): New variable. Pushed, thanks!

Re: [PATCH 2/4] gnu: Add python-sphinx-1.5.2, python-sphinx-1.5.3

On Mon, Mar 27, 2017 at 11:12:34AM -0400, Leo Famulari wrote: > On Mon, Mar 27, 2017 at 11:11:00AM -0400, Leo Famulari wrote: > > On Sun, Mar 26, 2017 at 06:32:49PM +0300, Frederick Muriithi wrote: > > > On Sun, Mar 26, 2017 at 6:10 PM, Pjotr Prins > > > wrote: > > > >

Re: [PATCH 3/4] gnu: Add python-paramunittest

On Sun, Mar 26, 2017 at 12:23:34PM +0300, Muriithi Frederick Muriuki wrote: > * gnu/packages/python.scm (python-paramunittest): New variable. I added a python2 variant (we like to do this when adding new Python packages) and pushed. Thanks! signature.asc Description: PGP signature

Re: A "busy beaver" approach to assisting package definition updates

Hey there! Christopher Allan Webber skribis: > David Thompson and I had the good fortune to be able to hang out with > the esteemed Gerald Sussman in his office over tea. Topics were wide > ranging, but one in particular has stuck in my mind as to how it could > apply

Re: [PATCH 4/4] gnu: Add python-mando

Leo Famulari skribis: > On Sun, Mar 26, 2017 at 12:23:35PM +0300, Muriithi Frederick Muriuki wrote: >> * gnu/packages/python.scm (python-mando): New variable. > > Thanks, looks good! > > I'll push this series (or a revision of it) after we get a timely > response to the

Re: [PATCH 3/4] gnu: Add python-paramunittest

Hi Frederick, Frederick Muriithi skribis: >> An issue has been started, and hopefully, we'll receive the answer soon. > > From this thread https://github.com/rik0/ParamUnittest/issues/8 the > author has finally chosen BSD-2. Cool. Do you want to send an updated patch or

Re: wrong key used for signing

On Tue, Mar 28, 2017 at 10:47:05AM +0200, Marius Bakke wrote: > Thomas Danckaert writes: > > > I accidentally used the wrong key when signing my commits to > > core-updates yesterday. How can I fix this? A number of commits were > > already made on top of mine, so

Re: wrong key used for signing

On Tue, Mar 28, 2017 at 03:03:23PM +0200, Marius Bakke wrote: > To be clear, simply "vouching" for the commits in a signed message is > good enough for me. It would be good to have the signing key for future > reference, but if you don't want to disclose it I'm fine with that. The key that was

On merging the npm importer

Hi, 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 improvements and that's why I think we should merge it. Have alook at my npm branch here, rebased on master https://gitlab.com/janneke/guix I added a patch with

mtab

As far as I know we have a message on every boot which spits an non-fatal error about mtab. A while back in Gentoo I asked about this while I experienced it on their system, and the solution was this: rm /etc/mtab && ln -s /proc/self/mounts /etc/mtab is there something special about our mtab

`check' phase for the emacs build system

Many emacs packages have tests in something like "packagename-tests.el". Would it be a good idea to add a `check' phase to the emacs build system that looks for these test files, and attempts to run tests? Regards, Arun Isaac.

Re: wrong key used for signing

Marius Bakke writes: > Thomas Danckaert writes: > >> I accidentally used the wrong key when signing my commits to >> core-updates yesterday. How can I fix this? A number of commits were >> already made on top of mine, so we'd need to rebase? > >

systemd on debian8, a possible solution

Hi, could we point out the solution redhat had in this case? root@sharknado9000:~# systemctl enable guix-daemon Failed to execute operation: No such file or directory The output above was when you follow our documentation. Now redhat has this workaround

Re: wrong key used for signing

Thomas Danckaert writes: > I accidentally used the wrong key when signing my commits to > core-updates yesterday. How can I fix this? A number of commits were > already made on top of mine, so we'd need to rebase? If you can send a signed message (using key D77D54FD

wrong key used for signing

I accidentally used the wrong key when signing my commits to core-updates yesterday. How can I fix this? A number of commits were already made on top of mine, so we'd need to rebase? These are the offending commits: b1a8fd2d2 gnu: libreoffice: Update to 5.3.1.2. 90ac806d3 gnu: orcus: Update

[PATCH 0/1] QEMU 2.9.0-rc1

This is just a release candidate, but it does boot the GuixSD release image. I'm sharing it so that people can get early access to the bug fixes it includes. Leo Famulari (1): gnu: qemu: Update to 2.9.0-rc1 [security fixes]. gnu/local.mk | 13 ---

[PATCH 1/1] gnu: qemu: Update to 2.9.0-rc1 [security fixes].

Fixes CVE-2016-9602 and CVE-2017-{5857,5973,5987,6058,6505}. * gnu/packages/qemu.scm (qemu): Update to 2.9.0-rc1. [source]: Remove obsolete patches. * gnu/packages/patches/qemu-CVE-2016-10155.patch, gnu/packages/patches/qemu-CVE-2017-2615.patch, gnu/packages/patches/qemu-CVE-2017-2620.patch,