bug#32769: Packaging Next browser (Common Lisp) [work in progress]

2018-10-11 Thread Andy Patterson
Hi Pierre, On Thu, 11 Oct 2018 12:44:43 +0200 Pierre Neidhardt wrote: > You were right, this was the issue. I've posted a patch upstream, it > should be fixed soon. > > Now Next compiles. Hurray!!! :D Nice. > > There is one last step though: the .asd bunble works, but not the >

bug#32183: New ‘guix pull’ /root/.config/current/bin/guix: Permission denied

2018-10-11 Thread Ludovic Courtès
Hi there! I believe commit ed9d7cb4d95f8f4776e6fee2778ab52bc2852969 fixes it. That is, if you run ‘guix pull’ as root and then start ~/.config/guix/current/bin/guix-daemon, everything should be fine. Thanks, Ludo’.

bug#33015: asdf: cl-cffi-gtk tests fail: Unhandled memory fault at #x0

2018-10-11 Thread Pierre Neidhardt
I've reported the issue upstream: https://github.com/Ferada/cl-cffi-gtk/issues/24#issuecomment-428756336 but it could be that the errors comes from the way we run tests. Here is a copy of the error output during the check phase: --8<---cut

bug#32878: Python-3 CVE-2018-14647

2018-10-11 Thread Mark H Weaver
Leo Famulari writes: > On Sat, Oct 06, 2018 at 04:51:07PM +0200, Marius Bakke wrote: >> From a60d655fd4dddb86e1c8134c675fb61af52b32af Mon Sep 17 00:00:00 2001 >> From: Marius Bakke >> Date: Sat, 6 Oct 2018 16:47:05 +0200 >> Subject: [PATCH] gnu: python: Fix CVE-2018-14647. >> >> *

bug#32877: Python-2 CVE-2018-1060 CVE-2018-1061 CVE-2018-14647 CVE-2018-1000802

2018-10-11 Thread Mark H Weaver
Leo Famulari writes: > On Sat, Oct 06, 2018 at 06:53:36PM +0200, Marius Bakke wrote: >> From 2891a9acb7704c3397ef34fbb520b46936504422 Mon Sep 17 00:00:00 2001 >> From: Marius Bakke >> Date: Sat, 6 Oct 2018 18:50:47 +0200 >> Subject: [PATCH] gnu: python2: Add upstream security fixes. >> >> This

bug#32769: Packaging Next browser (Common Lisp) [work in progress]

2018-10-11 Thread Andy Patterson
Hi, On Wed, 10 Oct 2018 15:21:26 +0200 Pierre Neidhardt wrote: > The good news: all Next browser dependencies are now packaged under > the branch wip-nextbrowser. > > The bad news: Next browser fails to build. > > [...] > > Andy, any clue on this? It's probably the > ; caught WARNING: > ;