Re: pre-release [PATCH] git-service [v2]

[Alex Kost]

ng0 (2016-08-25 12:55 +0300) wrote:

> Hi,
>
> thanks for finding the errors. I applied your suggestions but the
> service still goes into respawn loop when the VM boots. Do you have any
> idea why this could happen?

Is there any output in syslog?  How does you patch look now?  What is
the exact "git daemon" command that is executing?  You can find this
command by looking at "/gnu/store/…-shepherd-git.scm" file: when you
built the system, guix told you that it would build this file.  If you
missed it, you can still find it by looking at
"/run/current-system/boot", there is a reference to
"/gnu/store/…-shepherd.conf", and there you can find a link to
"…-shepherd-git.scm" file.

-- 
Alex

Re: [PATCH] gnu: Add ola

[Alex Vong]

Hi,

John J Foerch  writes:

> Hello,
>
> Here is a package definition for ola (Open Lighting Architecture).  I
> was having trouble getting ola's python bindings to build, as detailed
> in an earlier message, so this patch does not include them.  I intend to
> add them when I figure out how, but since they're not essential to the
> function of the library, I think they need not block adding the basic
> package.  Ola also provides bindings for java, but they depend on Apache
> maven, which we don't seem to have a package for yet, so here again, I
> think that this can be added later.
>
> Please let me know of anything that should be changed.
>
> Thank you,
>
> --
> John Foerch
>
>
> From f600e8a43997efecb9587a9c39579a7d6f3291f4 Mon Sep 17 00:00:00 2001
> From: "John J. Foerch" 
> Date: Wed, 3 Aug 2016 21:36:52 -0500
> Subject: [PATCH] gnu: Add ola.
>
> * gnu/packages/ola.scm (ola): New variable.
> ---
>  gnu/packages/ola.scm | 77 
> 
>  1 file changed, 77 insertions(+)
>  create mode 100644 gnu/packages/ola.scm
>
> diff --git a/gnu/packages/ola.scm b/gnu/packages/ola.scm
> new file mode 100644
> index 000..f47c029
> --- /dev/null
> +++ b/gnu/packages/ola.scm
> @@ -0,0 +1,77 @@
> +;;; GNU Guix --- Functional package management for GNU
> +;;; Copyright © 2016 John J. Foerch 
> +;;;
> +;;; 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 License as published by
> +;;; the Free Software Foundation; either version 3 of the License, or (at
> +;;; your option) any later version.
> +;;;
> +;;; GNU Guix is distributed in the hope that it will be useful, but
> +;;; WITHOUT ANY WARRANTY; without even the implied warranty of
> +;;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +;;; GNU General Public License for more details.
> +;;;
> +;;; You should have received a copy of the GNU General Public License
> +;;; along with GNU Guix.  If not, see .
> +
> +(define-module (gnu packages ola)
> +  #:use-module (guix build-system gnu)
> +  #:use-module (guix download)
> +  #:use-module ((guix licenses) #:prefix license:)
> +  #:use-module (guix packages)
> +  #:use-module (gnu packages bison)
> +  #:use-module (gnu packages check)
> +  #:use-module (gnu packages compression)
> +  #:use-module (gnu packages gnunet)
> +  #:use-module (gnu packages flex)
> +  #:use-module (gnu packages libftdi)
> +  #:use-module (gnu packages libusb)
> +  #:use-module (gnu packages linux)
> +  #:use-module (gnu packages pkg-config)
> +  #:use-module (gnu packages protobuf))
> +
> +(define-public ola
> +  (package
> +(name "ola")
> +(version "0.10.2")
> +(source (origin
> +  (method url-fetch)
> +  (uri (string-append
> +
> "https://github.com/OpenLightingProject/ola/releases/download/;
> +version "/ola-" version ".tar.gz"))
> +  (sha256
> +   (base32
> +"09zx1c8nkj29shfdzkahrh9397m3mwnsy0gj7jrb63f89f3n2vlq"
> +(build-system gnu-build-system)
> +(native-inputs
> + `(("bison" ,bison)
> +   ("cppunit" ,cppunit)
> +   ("flex" ,flex)
> +   ("pkg-config" ,pkg-config)))
> +(inputs
> + `(("libftdi" ,libftdi)
> +   ("libmicrohttpd" ,libmicrohttpd)
> +   ("libusb" ,libusb)
> +   ("libuuid" ,util-linux)
> +   ("zlib" ,zlib)))
> +(propagated-inputs
> + `(("protobuf" ,protobuf)))
> +(arguments
> + `(;; G++ >= 4.8 macro expansion tracking requires lots of memory, 
> causing
> +   ;; build to fail on low memory systems.  We disable that with the
> +   ;; following configure flags.
> +   #:configure-flags (list "CXXFLAGS=-ftrack-macro-expansion=0")
> +   #:make-flags (list (string-append "PREFIX=" (assoc-ref %outputs 
> "out")))
> +   #:phases %standard-phases))
> +(synopsis "Framework for controlling entertainment lighting equipment")
> +(description "The Open Lighting Architecture is a framework for lighting
> +control information.  It supports a range of protocols and over a dozen USB
> +devices.  It can run as a standalone service, which is useful for converting
> +signals between protocols, or alternatively using the OLA API, it can be used
> +as the backend for lighting control software.  OLA runs on many different
> +platforms including ARM, which makes it a perfect fit for low cost Ethernet 
> to
> +DMX gateways.")
> +(home-page "https://www.openlighting.org/ola;)
> +(license license:lgpl2.1+)))

The patch builds on my machine and lgtm. I make some minor changes (in
diff format):

1. Add ola.scm to gnu/local.mk, so that the build system knows the
   presence of gnu/package/ola.scm. The commit message should say this
   as well.

2. Move protobuf from 

[PATCH] gnu: Add ola

[John J Foerch]

Hello,

Here is a package definition for ola (Open Lighting Architecture).  I
was having trouble getting ola's python bindings to build, as detailed
in an earlier message, so this patch does not include them.  I intend to
add them when I figure out how, but since they're not essential to the
function of the library, I think they need not block adding the basic
package.  Ola also provides bindings for java, but they depend on Apache
maven, which we don't seem to have a package for yet, so here again, I
think that this can be added later.

Please let me know of anything that should be changed.

Thank you,

--
John Foerch

>From f600e8a43997efecb9587a9c39579a7d6f3291f4 Mon Sep 17 00:00:00 2001
From: "John J. Foerch" 
Date: Wed, 3 Aug 2016 21:36:52 -0500
Subject: [PATCH] gnu: Add ola.

* gnu/packages/ola.scm (ola): New variable.
---
 gnu/packages/ola.scm | 77 
 1 file changed, 77 insertions(+)
 create mode 100644 gnu/packages/ola.scm

diff --git a/gnu/packages/ola.scm b/gnu/packages/ola.scm
new file mode 100644
index 000..f47c029
--- /dev/null
+++ b/gnu/packages/ola.scm
@@ -0,0 +1,77 @@
+;;; GNU Guix --- Functional package management for GNU
+;;; Copyright © 2016 John J. Foerch 
+;;;
+;;; 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 License as published by
+;;; the Free Software Foundation; either version 3 of the License, or (at
+;;; your option) any later version.
+;;;
+;;; GNU Guix is distributed in the hope that it will be useful, but
+;;; WITHOUT ANY WARRANTY; without even the implied warranty of
+;;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+;;; GNU General Public License for more details.
+;;;
+;;; You should have received a copy of the GNU General Public License
+;;; along with GNU Guix.  If not, see .
+
+(define-module (gnu packages ola)
+  #:use-module (guix build-system gnu)
+  #:use-module (guix download)
+  #:use-module ((guix licenses) #:prefix license:)
+  #:use-module (guix packages)
+  #:use-module (gnu packages bison)
+  #:use-module (gnu packages check)
+  #:use-module (gnu packages compression)
+  #:use-module (gnu packages gnunet)
+  #:use-module (gnu packages flex)
+  #:use-module (gnu packages libftdi)
+  #:use-module (gnu packages libusb)
+  #:use-module (gnu packages linux)
+  #:use-module (gnu packages pkg-config)
+  #:use-module (gnu packages protobuf))
+
+(define-public ola
+  (package
+(name "ola")
+(version "0.10.2")
+(source (origin
+  (method url-fetch)
+  (uri (string-append
+"https://github.com/OpenLightingProject/ola/releases/download/;
+version "/ola-" version ".tar.gz"))
+  (sha256
+   (base32
+"09zx1c8nkj29shfdzkahrh9397m3mwnsy0gj7jrb63f89f3n2vlq"
+(build-system gnu-build-system)
+(native-inputs
+ `(("bison" ,bison)
+   ("cppunit" ,cppunit)
+   ("flex" ,flex)
+   ("pkg-config" ,pkg-config)))
+(inputs
+ `(("libftdi" ,libftdi)
+   ("libmicrohttpd" ,libmicrohttpd)
+   ("libusb" ,libusb)
+   ("libuuid" ,util-linux)
+   ("zlib" ,zlib)))
+(propagated-inputs
+ `(("protobuf" ,protobuf)))
+(arguments
+ `(;; G++ >= 4.8 macro expansion tracking requires lots of memory, causing
+   ;; build to fail on low memory systems.  We disable that with the
+   ;; following configure flags.
+   #:configure-flags (list "CXXFLAGS=-ftrack-macro-expansion=0")
+   #:make-flags (list (string-append "PREFIX=" (assoc-ref %outputs "out")))
+   #:phases %standard-phases))
+(synopsis "Framework for controlling entertainment lighting equipment")
+(description "The Open Lighting Architecture is a framework for lighting
+control information.  It supports a range of protocols and over a dozen USB
+devices.  It can run as a standalone service, which is useful for converting
+signals between protocols, or alternatively using the OLA API, it can be used
+as the backend for lighting control software.  OLA runs on many different
+platforms including ARM, which makes it a perfect fit for low cost Ethernet to
+DMX gateways.")
+(home-page "https://www.openlighting.org/ola;)
+(license license:lgpl2.1+)))
-- 
2.9.0

Re: GuixSD 0.11.0 Install

[Danny Milosavljevic]

>The GuixSD system install (desktop) seemed to install successfully. However, 
>when booting into the new system (non-UEFI) a kernel panic occurs. Something 
>about "Kernel panic - not syncing : Attempted to kill init!"

This is not the original problem. What does it say right above it?

Usually it can't find the root filesystem, the filesystem type is unknown, the 
harddrive drivers are not found etc.

Re: Store on separate partition

[Tomáš Čech]

On Thu, Aug 25, 2016 at 04:30:37PM +0200, Tomáš Čech wrote:

On Wed, Aug 24, 2016 at 12:37:49PM +0200, Carlos Sánchez de La Lama wrote:

my (not very big) root partition is almost full, even after
garbage-collecting. I am trying to move the store to a separate
partition, but this is problematic as you need the store at boot time
for the system utilities (and to mount partitions, actually).


I tried to do it recently but failed.  My understanding is that it's
impossible, but I may be wrong.


After giving it some more thinking, I also think this is not
possible. The kernel image itself is in the store (and must be, because
you can have several system generations, each using a different
kernel). Same with initrd images.

I have finally moved the whole root to a bigger disk, not much different
to moving the store as root size (aside from the store) is rather small.


I think it is impossible now but to achieve that you'd need only:

1] to store /gnu/store on separate partition (so grub will find it with its 
--search)
2] and have some bind mounts ready in initrd stage.

It would be nice to have more flexibility in this area.


According to
https://www.gnu.org/software/guix/manual/guix.html#File-Systems it
seems that 'bind-mount' is supported flag so together with
'needed-for-boot?' it should be doable.

normal mount
/dev/sdX --> /mnt/store-partition

bind mount
/mnt/store-partition/gnu --> /gnu

grub should find your kernel and initrd with --search

S_W


signature.asc
Description: Digital signature

Re: How to import modules into build phase

[David Craven]

Found a solution. Requires both #:modules and #:imported-modules to be
set to work.

HELP needed with CA certificates! [PATCH] gnu: Add tup, Add pbpst.

[ng0]

First things first: Corrections will happen, this is not what I ask
for. I need help with getting pbpst (which just uses curl for this) to
learn about the certificates on the system.
I can not continue this, all the greping and no advance. I can not solve
this, I need help.

>From 9556d469f3be74a0ea0ada9e4879c25a32858a3e Mon Sep 17 00:00:00 2001
From: ng0 
Date: Mon, 15 Aug 2016 00:26:40 +
Subject: [PATCH 1/2] gnu: Add tup.

* gnu/packages/tup.scm: New file.
* gnu/local.mk (GNU_SYSTEM_MODULES): Add it.
---
 gnu/local.mk |  2 ++
 gnu/packages/tup.scm | 83 
 2 files changed, 85 insertions(+)
 create mode 100644 gnu/packages/tup.scm

diff --git a/gnu/local.mk b/gnu/local.mk
index b8c5378..bc4b968 100644
--- a/gnu/local.mk
+++ b/gnu/local.mk
@@ -5,6 +5,7 @@
 # Copyright © 2013, 2014, 2015, 2016 Mark H Weaver 
 # Copyright © 2016 Chris Marusich 
 # Copyright © 2016 Kei Kebreau 
+# Coypright © 2016 ng0 
 #
 # This file is part of GNU Guix.
 #
@@ -343,6 +344,7 @@ GNU_SYSTEM_MODULES =\
   %D%/packages/tmux.scm\
   %D%/packages/tor.scm\
   %D%/packages/tre.scm\
+  %D%/packages/tup.scm\
   %D%/packages/tv.scm\
   %D%/packages/unrtf.scm			\
   %D%/packages/upnp.scm\
diff --git a/gnu/packages/tup.scm b/gnu/packages/tup.scm
new file mode 100644
index 000..66ce099
--- /dev/null
+++ b/gnu/packages/tup.scm
@@ -0,0 +1,83 @@
+;;; GNU Guix --- Functional package management for GNU
+;;; Copyright © 2016 ng0 
+;;;
+;;; 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 License as published by
+;;; the Free Software Foundation; either version 3 of the License, or (at
+;;; your option) any later version.
+;;;
+;;; GNU Guix is distributed in the hope that it will be useful, but
+;;; WITHOUT ANY WARRANTY; without even the implied warranty of
+;;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+;;; GNU General Public License for more details.
+;;;
+;;; You should have received a copy of the GNU General Public License
+;;; along with GNU Guix.  If not, see .
+
+(define-module (gnu packages tup)
+  #:use-module (gnu packages)
+  #:use-module (gnu packages linux)
+  #:use-module (gnu packages pkg-config)
+  #:use-module (gnu packages version-control)
+  #:use-module (gnu packages perl)
+  #:use-module ((guix licenses) #:prefix license:)
+  #:use-module (guix packages)
+  #:use-module (guix download)
+  #:use-module (guix build-system gnu))
+
+(define-public tup
+  (package
+(name "tup")
+(version "0.7.4")
+(source (origin
+  (method url-fetch)
+  (uri (string-append "https://github.com/gittup/;
+  name "/archive/v" version ".tar.gz"))
+  (file-name (string-append name "-" version ".tar.gz"))
+  (sha256
+   (base32
+"044h9kbcg1sfwpn13j1grw79kwysqhyn3w3g6yy8ap4j32v10gz2"
+(build-system gnu-build-system)
+(arguments
+ ;; tup requires fusermount to have suid, which we cannot provide in build env,
+ ;; we bootstrap it and use tup generate.  This also means that no tests are run.
+ `(#:tests? #f
+   #:modules ((guix build gnu-build-system)
+  (guix build utils))
+   #:phases
+   (modify-phases %standard-phases
+ (replace 'configure
+   (lambda* (#:key outputs #:allow-other-keys)
+ (zero? (system* "./build.sh"))
+ (zero? (system* "./build/tup" "generate" "script.sh"
+ (replace 'build
+   (lambda* (#:key outputs #:allow-other-keys)
+ (substitute* "script.sh"
+   (("`git describe`") (string-append "v" ,version)))
+ (zero? (system* "./script.sh"))
+ #t))
+ (replace 'install
+   (lambda* (#:key outputs #:allow-other-keys)
+ (let* ((out (assoc-ref outputs "out"))
+(bin (string-append out "/bin"))
+(man (string-append out "/share/man/man1")))
+   (install-file "tup" bin)
+   (install-file "tup.1" man))
+ #t)
+(native-inputs
+ `(("pkg-config" ,pkg-config)
+   ("perl" ,perl)))
+(inputs
+ `(("fuse" ,fuse)))
+(synopsis "A file-based build system")
+(description
+ "Tup is a file-based build system for Linux, OSX, and Windows. It inputs a list
+of file changes and a directed acyclic graph (DAG), then processes the DAG to
+execute the appropriate commands required to update dependent files.  Updates are
+performed with very little overhead since tup implements powerful build
+algorithms to avoid doing unnecessary work.  This means you can stay focused on
+your 

How to import modules into build phase

[David Craven]

Hi,

So I'm getting a lot of weird errors and tried a bunch of different things.

I have a wrap-qt-program in (gnu packages qt) and would like to make
it available on the build side.

The snippet I'm trying to use doesn't work:

   #:modules ((gnu packages qt)
  ,@%cmake-build-system-modules)

For reference wrap-qt-program looks like this:

(define (wrap-qt-program out program)
  (define (suffix env-var path)
(let ((env-val (getenv env-var)))
  (if env-val (string-append env-val ":" path) path)))

  (let ((qml-path(suffix "QML2_IMPORT_PATH"
 (string-append out "/qml")))
(plugin-path (suffix "QT_PLUGIN_PATH"
 (string-append out "/plugins")))
(xdg-data-path   (suffix "XDG_DATA_DIRS"
 (string-append out "/share")))
(xdg-config-path (suffix "XDG_CONFIG_DIRS"
 (string-append out "/etc/xdg"
  (wrap-program (string-append out "/bin/" program)
`("QML2_IMPORT_PATH" = (,qml-path))
`("QT_PLUGIN_PATH" = (,plugin-path))
`("XDG_DATA_DIRS" = (,xdg-data-path))
`("XDG_CONFIG_DIRS" = (,xdg-config-path)

Re: [PATCH] gnu: gzochi: Update to 0.10.

[Mark H Weaver]

Julian Graham  writes:
> I've made some fixes and cut a new release. Find attached a patch that
> updates the `gzochi' package to the new released version. I've tested
> the x86_64 and i686 builds as you suggested, and would be much obliged
> if you'd try a build for armhf.

I tested gzochi-0.10.1 by applying your proposed patch to current
'master' (commit 8930fe62f0) and building on armhf.  Unfortunately
there's still a problem: test_oid_strategy_allocation fails an
assertion.  See below.

   Mark


==
   gzochid 0.10.1: tests/test-suite.log
==

# TOTAL: 35
# PASS:  34
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: test-oids
===

/oids/strategy/allocation: **
ERROR:test-oids.c:60:test_oid_strategy_allocation: 'gzochid_oids_reserve_block 
(strategy, , NULL)' should be TRUE
FAIL test-oids (exit status: 134)

[PATCH 2/2] gnu: Add sway.

[Tomáš Čech]

* gnu/packages/freedesktop.scm(sway): New variable.
---
 gnu/packages/freedesktop.scm | 44 
 1 file changed, 44 insertions(+)

diff --git a/gnu/packages/freedesktop.scm b/gnu/packages/freedesktop.scm
index 07a6e0b..597fcaf 100644
--- a/gnu/packages/freedesktop.scm
+++ b/gnu/packages/freedesktop.scm
@@ -35,6 +35,7 @@
   #:use-module (gnu packages gnome)
   #:use-module (gnu packages python)
   #:use-module (gnu packages pth)
+  #:use-module (gnu packages pcre)
   #:use-module (gnu packages linux)
   #:use-module (gnu packages pkg-config)
   #:use-module (gnu packages autotools)
@@ -56,6 +57,7 @@
   #:use-module (gnu packages admin)
   #:use-module (gnu packages polkit)
   #:use-module (gnu packages databases)
+  #:use-module (gnu packages web)
   #:use-module (gnu packages xdisorg))
 
 (define-public xdg-utils
@@ -686,3 +688,45 @@ wish to perform colour calibration.")
  "This is wayland compositor library used by several projects like sway,
 orbment or Guile-WM.")
 (license license:x11)))
+
+(define-public sway
+  (package
+(name "sway")
+(version "0.9")
+(source (origin
+  (method url-fetch)
+  (uri (string-append
+"https://github.com/SirCmpwn/; name "/archive/"
+version ".tar.gz"))
+  (sha256
+   (base32
+"0bgli7scjlvbgas09dx5fnncgda41ssba6fzkw2vyk88pmdgx66w"))
+  (patches (list (search-patch "sway-debug.patch")
+(build-system cmake-build-system)
+(arguments
+ '(#:configure-flags '("-DVERBOSE=1")
+   #:tests? #f)) ; no 'check' target
+(native-inputs
+ `(("gdk-pixbuf" ,gdk-pixbuf)
+   ("libxslt" ,libxslt)
+   ("pkg-config" ,pkg-config)
+   ("wayland" ,wayland)))
+(inputs
+ `(("asciidoc" ,asciidoc)
+   ("cairo" ,cairo)
+   ("docbook-xml" ,docbook-xml)
+   ("docbook-xsl" ,docbook-xsl)
+   ("gdk-pixbuf" ,gdk-pixbuf)
+   ("json-c" ,json-c)
+   ("libinput" ,libinput)
+   ("libxkbcommon" ,libxkbcommon)
+   ("linux-pam" ,linux-pam)
+   ("pango" ,pango)
+   ("pcre" ,pcre)
+   ("wlc" ,wlc)))
+(synopsis "Window manager for Wayland, compatible with i3")
+(home-page "https://github.com/Cloudef/wlc;)
+(description
+ "SirCmpwn's WAYland window manager is work-in-progress i3-compatible
+tiling window manager.")
+(license license:x11)))
-- 
2.9.2

[PATCH 1/2] gnu: Add wlc.

[Tomáš Čech]

* gnu/packages/freedesktop.scm(wlc): New variable.
* gnu/packages/patches/wlc-implement-wlc_view_get_pid.patch: Add it
* gnu/local.mk: Add entry for patch above.
---
 gnu/packages/freedesktop.scm | 41 -
 1 file changed, 40 insertions(+), 1 deletion(-)

diff --git a/gnu/packages/freedesktop.scm b/gnu/packages/freedesktop.scm
index 67f1e1a..07a6e0b 100644
--- a/gnu/packages/freedesktop.scm
+++ b/gnu/packages/freedesktop.scm
@@ -27,10 +27,14 @@
   #:use-module (guix packages)
   #:use-module (guix download)
   #:use-module (guix git-download)
+  #:use-module (guix build-system cmake)
   #:use-module (guix build-system gnu)
   #:use-module (guix build-system python)
+  #:use-module (gnu packages)
+  #:use-module (gnu packages gl)
   #:use-module (gnu packages gnome)
   #:use-module (gnu packages python)
+  #:use-module (gnu packages pth)
   #:use-module (gnu packages linux)
   #:use-module (gnu packages pkg-config)
   #:use-module (gnu packages autotools)
@@ -51,7 +55,8 @@
   #:use-module (gnu packages acl)
   #:use-module (gnu packages admin)
   #:use-module (gnu packages polkit)
-  #:use-module (gnu packages databases))
+  #:use-module (gnu packages databases)
+  #:use-module (gnu packages xdisorg))
 
 (define-public xdg-utils
   (package
@@ -647,3 +652,37 @@ different sorts of messages in different formats.")
 useful for both applications which need colour management and applications that
 wish to perform colour calibration.")
 (license license:lgpl2.1+)))
+
+(define-public wlc
+  (package
+(name "wlc")
+(version "0.0.5")
+(source (origin
+  (method url-fetch)
+  (uri (string-append
+"https://github.com/Cloudef/; name "/releases/download/v"
+version "/" name "-" version ".tar.bz2"))
+  (sha256
+   (base32
+"0dmiklis820qzin74f16bmbz1jkjy93r5mix8cqbcqpb9f7qxahp"
+(build-system cmake-build-system)
+(native-inputs
+ `(("pkg-config" ,pkg-config)))
+(inputs
+ `(("libinput" ,libinput)
+   ("libx11" ,libx11)
+   ("libxkbcommon" ,libxkbcommon)
+   ("mesa" ,mesa)
+   ("pixman" ,pixman)
+   ("pth" ,pth)
+   ("wayland" ,wayland)
+   ("xcb-util-image" ,xcb-util-image)
+   ("xcb-util-wm" ,xcb-util-wm)
+   ("xproto" ,xproto)
+   ("zlib" ,zlib)))
+(synopsis "Wayland Compositor Library")
+(home-page "https://github.com/Cloudef/wlc;)
+(description
+ "This is wayland compositor library used by several projects like sway,
+orbment or Guile-WM.")
+(license license:x11)))
-- 
2.9.2

hackage importer problem

[John J Foerch]

Hello,

I'm seeing a problem with the hackage importer with the git-annex
package:

  $ guix import hackage git-annex
  Syntax error: unexpected token : custom-setup (at line 316, column 0)
  Syntax error: unexpected end of input
  guix import: error: failed to download cabal file for package 'git-annex'

git-annex.cabal is here:

  http://hackage.haskell.org/package/git-annex-6.20160808/git-annex.cabal

Is it a bug in the importer?

Thank you,

--
John Foerch

Re: [PATCH] gnu: Add capnproto.

[Kenton Varda]

On Thu, Aug 25, 2016 at 7:57 AM, Marius Bakke  wrote:
> Hi, thanks for dropping in!
>
> From reading the comments in the Makefile, apparently they are trying to
> enforce something called the One-Definition Rule:
>
> https://en.wikipedia.org/wiki/One_Definition_Rule
>
> The way Guix (and actually most distro build systems) works makes it
> impossible for another definition to "leak" into the build container, so
> I don't understand either what they are trying to solve.

I think what they're actually referring to here is issues with
templates that are instantiated in the same way in different places --
the instances need to be de-duped. When shared libraries are involved,
this gets weird, and Windows and OSX both tend to have severe
problems. Linux/ELF generally "gets it right" by using weak symbols,
although that relies on the fact that symbols in shared libraries all
get lumped into one process-wide symbol table with no namespacing,
which causes a bunch of other problems... but it's great at handling
ODR correctly.

So I think the gtest people may actually be concerned about problems
that primarily affect other platforms and they have applied an
over-broad policy.

Another possibility is that they have severe ABI compatibility issues,
perhaps caused by #ifdefs in template definitions, in which case
linking gtest as a library would fail miserably if the app chose
different flags than gtest itself.

But again, I am mostly speculating and could be wrong.

> I think Kenton is referring to the Debian manual, which is in XML
> format:
>
> https://github.com/thomaslee/capnproto-debian/blob/master/debian/capnp.1.xml
>
> But you are right, it would be better to convert it to a standard format
> and simply add a make target for it.

Right, my main point here is that I would like the help text to be the
canonical source of documentation, with other sources being
auto-generated from it. The nice thing about the help text is that the
kj::Main framework actually makes it very hard to forget to update the
help text, since it forces you to provide documentation for each flag
when defining them. So when the code changes, the help text always
gets updated, whereas a separate document probably won't because I am
incredibly lazy. :)

In theory, it should be easy even for someone with poor C++ skills to
copy the existing code that generates --help then modify it to
generate some other format instead. ;)

In any case, I'll definitely mention it on the issue you opened (which
I actually hadn't seen yet -- email overload).

-Kenton

Re: libtiff security update (multiple CVEs)

[David Craven]

LGTM. I didn't look at the patches, but adding a libtiff/fixed package
and using the replacement field in libtiff is my understanding of how
security updates should be done.

Re: libtiff security update (multiple CVEs)

[Leo Famulari]

On Tue, Aug 23, 2016 at 03:44:34PM -0400, Leo Famulari wrote:
> I took these patches from the libtiff CVS repo using the information
> contained in the respective bug reports:
> http://bugzilla.maptools.org/buglist.cgi?product=libtiff
> 
> This is my first time using CVS, so please review carefully.

Ping! :)

Re: [PATCH] gnu: Add capnproto.

[Marius Bakke]

Alex Vong  writes:

>> PS. regarding the man page, I believe Debian mostly generated this
>> page from the capnp tool's help text. I'd accept a patch to
>> c++/src/kj/main.c++ which adds some code to generate man XML format
>> directly, so that we don't have to maintain the same text in multiple
>> places.
>
> I want to ask what is meant by man XML format? Do you mean to generate
> man page? As far as I know, there are at least 2 ways to generate a man
> page. One way is to use help2man, which is probably the Debian's
> approach. Another way is to write the man page in pod (perl's plain old
> documentation) and use pod2man to translate it into a man page. Would
> you accept any of these approaches?

I think Kenton is referring to the Debian manual, which is in XML
format:

https://github.com/thomaslee/capnproto-debian/blob/master/debian/capnp.1.xml

But you are right, it would be better to convert it to a standard format
and simply add a make target for it.

Cheers,
Marius

Re: [PATCH] gnu: Add capnproto.

[Alex Vong]

Hi,

Kenton Varda  writes:

> Hi, Cap'n Proto upstream author here. Noticed this thread in a Google
> search, thought I'd comment.
>
> To shed some light on the googletest situation:
>
> The googletest maintainers have deemed that googletest should never
> ever be system-installed, and have even disabled `make install` in
> their build. See:
>
> https://github.com/google/googletest/blob/master/googletest/Makefile.am#L300
>
> I don't really understand what they think they're solving here but it
> is what it is and this seems to make it hard to use googletest in a
> non-bundled way. It's possible I misunderstood, though.
>
> FWIW, Cap'n Proto only uses googletest to build its tests. It does not
> install any artifacts that were influenced by googletest.
>
> In any case, this dependency will be gone once I find time to do the
> next release. Sorry for the trouble in the meantime.
>
> -Kenton
>
> PS. regarding the man page, I believe Debian mostly generated this
> page from the capnp tool's help text. I'd accept a patch to
> c++/src/kj/main.c++ which adds some code to generate man XML format
> directly, so that we don't have to maintain the same text in multiple
> places.

I want to ask what is meant by man XML format? Do you mean to generate
man page? As far as I know, there are at least 2 ways to generate a man
page. One way is to use help2man, which is probably the Debian's
approach. Another way is to write the man page in pod (perl's plain old
documentation) and use pod2man to translate it into a man page. Would
you accept any of these approaches?

Thanks,
Alex

Re: [PATCH] gnu: awesome: Add awesome-3.5

[doncatnip]

On Thu, 25 Aug 2016 14:47:19 +
ng0  wrote:

I'm sorry, I just don't really know what to say about this as my
experience with hardening is rather non-existant. I can sure find out
how to disable dbus and submit another patch.

> ng0  writes:
> 
> >> Works for me (written from inside a running awesome-3.5.9).  
> >
> > ng0@shadowwalker ~$ awesome --version
> > awesome v3.5.9 (Mighty Ravendark)
> > • Build: Sun Mar 06 14:05:54Z 2016 for x86_64 by gcc version 4.9.3
> > (@) • Compiled against Lua 5.2.4 (running with Lua 5.2)
> > • D-Bus support: ✔  
> 
> Great, the joy of a limited font... Nevermind this message then for
> obvious reasons but rather take it as a note that dbus and hardening
> is something we need to watch in the future ;)
> 
> > Having no dbus support will help with eventual hardening of Guix,
> > but why do we not have it in awesome? 
> > And why would we we need it (dbus support) at all? I don't even
> > know why I used to build it with dbus support before. Works either
> > way.  
> 

Re: [PATCH] gnu: awesome: Add awesome-3.5

[doncatnip]

On Thu, 25 Aug 2016 14:50:29 +
ng0  wrote:

Hi !
Of course. I didn't notice.

> (Sending this back as a copy to the thread on the list.)
> 
> Hi,
> 
> Can you please CC the guix-devel@gnu.org list or just reply-to the
> list when replying with the intention to not message offlist?
> 
> I think gnu.org does not set a reply-to thing, my email client does
> not care or know about such settings though.
> 
> doncatnip  writes:
> 
> > On Thu, 25 Aug 2016 09:22:38 +
> > ng0  wrote:
> >  
> >> Hi,
> >> 
> >> gno  writes:
> >>   
> >> > Hi guix !
> >> >
> >> > Sure hope I'm doing this right as I'm new to this.
> >> > These patches add Awesome 3.5.9 to the repository. I decided
> >> > against updating since it may break peoples configurations.
> >> > Awesome had API changes in between 3.4 and 3.5.
> >> >
> >> > Please have a look.
> >> 
> >> Awesome! Many thanks for your first patch, I will test this in the
> >> next days, maybe even today. I still have an 3.5.9 config from
> >> another system in a backup.
> >> 
> >> Ah. I see what you mean by you decided against updating. I think
> >> this is tricky. In my opinion awesome should provide the latest
> >> version, while for example awesome-3.4.15 would provide an older
> >> version. I use awesome, and this is what I would expect. When
> >> there was a version update, it was up to me to figure out if my
> >> config still worked and how to make it work again.
> >> I would vote for 3.5 as the new awesome and 3.4 inherits from this.
> >> But this can be applied after 3.5 is added I think?  
> >
> > Yea, there might be a better (guix) way to do this. I just thought
> > it might be good if those changes don't interfere at all with
> > current system configs yet. Should be easy to change later on.
> >  
> >> I did send in a patch to shorten the bloated description of
> >> awesome a couple of days ago, please wait with applying my patch.
> >> I will send in an update once we have this new awesome version
> >> update in tree. 
> >> > From cd3175f242450169b269ead777be6c7835476fba Mon Sep 17 00:00:00
> >> > 2001 From: doncatnip 
> >> > Date: Thu, 25 Aug 2016 01:43:53 +0200
> >> > Subject: [PATCH 1/3] gnu: lua: Enable dynamic library support.
> >> >
> >> > * gnu/packages/lua.scm: (lua)[arguments]: Add make flags.
> >> 
> >> You do more than just adding make flags, maybe let the commit
> >> message say that you added the CFLAGS: -DLUA_USE_POSIX,
> >> -DLUA_USE_DLOPEN and added LDFLAGS? I'm not sure how to express
> >> that, if at all. the git log should have other cases.
> >> Otherwise it looks good to me, this is just a formality the person
> >> commiting your patch(es) could also change on your behalf.  
> >
> > Add make flags which enable ld support as per headline, but yea
> > maybe it's not descriptive enough. I took example from another
> > patch recently posted in this list. I'd apperciate the person
> > commiting the patch changing it to something more appropriate.
> >
> > Thanks for testing this !
> >  
> >> > ---
> >> >  gnu/packages/lua.scm | 6 +-
> >> >  1 file changed, 5 insertions(+), 1 deletion(-)
> >> >
> >> > diff --git a/gnu/packages/lua.scm b/gnu/packages/lua.scm
> >> > index b4b5dee..c68a3ff 100644
> >> > --- a/gnu/packages/lua.scm
> >> > +++ b/gnu/packages/lua.scm
> >> > @@ -4,6 +4,7 @@
> >> >  ;;; Copyright © 2014 Mark H Weaver 
> >> >  ;;; Copyright © 2014 Andreas Enge 
> >> >  ;;; Copyright © 2016 Efraim Flashner 
> >> > +;;; Copyright © 2016 doncatnip 
> >> >  ;;;
> >> >  ;;; This file is part of GNU Guix.
> >> >  ;;;
> >> > @@ -51,7 +52,10 @@
> >> > (modify-phases %standard-phases
> >> >   (delete 'configure)
> >> >   (replace 'build
> >> > -   (lambda _ (zero? (system* "make" "CFLAGS=-fPIC"
> >> > "linux"
> >> > +   (lambda _ (zero? (system*
> >> > +  "make" "LDFLAGS=-ldl"
> >> > +  "CFLAGS=-fPIC -DLUA_USE_DLOPEN
> >> > -DLUA_USE_POSIX"
> >> > +  "linux"
> >> >   (replace 'install
> >> > (lambda* (#:key outputs #:allow-other-keys)
> >> >   (let ((out (assoc-ref outputs "out")))
> >> > -- 
> >> > 2.9.3
> >> >
> >> > From 995b67847508a70782eb522cda52b0aa36a20bd2 Mon Sep 17 00:00:00
> >> > 2001 From: doncatnip 
> >> > Date: Thu, 25 Aug 2016 02:22:37 +0200
> >> > Subject: [PATCH 2/3] gnu: lua: Add lua-lgi.
> >> >
> >> > * gnu/packages/lua.scm (lua-lgi): New variable.
> >> > ---
> >> >  gnu/packages/lua.scm | 71
> >> > +++- 1 file
> >> > changed, 70 insertions(+), 1 deletion(-)
> >> >
> >> > diff --git a/gnu/packages/lua.scm b/gnu/packages/lua.scm
> >> > index c68a3ff..8af0318 100644
> >> > --- a/gnu/packages/lua.scm
> >> > +++ 

Re: [PATCH] gnu: gzochi: Update to 0.10.

[Julian Graham]

Hey Mark,

On Tue, Aug 23, 2016 at 1:44 PM, Mark H Weaver  wrote:
> Either one would be fine for Guix users.  However, for the sake of
> non-Guix users and other distros, I would suggest making a new release.
> I think it's important that upstream software releases should be
> reasonably portable whenever feasible, especially to important
> architectures like i686 and armhf.  What do you think?

Hard to argue with that!

I've made some fixes and cut a new release. Find attached a patch that
updates the `gzochi' package to the new released version. I've tested
the x86_64 and i686 builds as you suggested, and would be much obliged
if you'd try a build for armhf.

Thanks for all the help thus far.


Regards,
Julian
From a3d190804bbe8925e12709c18e34e9c2a9ed36e9 Mon Sep 17 00:00:00 2001
From: Julian Graham 
Date: Thu, 25 Aug 2016 11:08:23 -0400
Subject: [PATCH] gnu: gzochi: Update to 0.10.1.

* gnu/packages/game-development.scm (gzochi): Update to 0.10.1.
---
 gnu/packages/game-development.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/game-development.scm b/gnu/packages/game-development.scm
index d544a72..3b21e1d 100644
--- a/gnu/packages/game-development.scm
+++ b/gnu/packages/game-development.scm
@@ -93,14 +93,14 @@ is used in some video games and movies.")
 (define-public gzochi
   (package
 (name "gzochi")
-(version "0.10")
+(version "0.10.1")
 (source (origin
   (method url-fetch)
   (uri (string-append "mirror://savannah/gzochi/gzochi-"
   version ".tar.gz"))
   (sha256
(base32
-"055m7ywgl48ljwxf0kjhl76ldck890y5afdwjhk5s3p65xyaxh0k"
+"1r0cjd3046rqlgwkgxm5ppkb9mya4gyv3980wfqxq8dfznv3pfdl"
 (build-system gnu-build-system)
 (arguments
  '(#:phases (modify-phases %standard-phases
-- 
2.5.0

Re: [PATCH] gnu: Add capnproto.

[Marius Bakke]

Kenton Varda  writes:

> Hi, Cap'n Proto upstream author here. Noticed this thread in a Google
> search, thought I'd comment.
>
> To shed some light on the googletest situation:
>
> The googletest maintainers have deemed that googletest should never
> ever be system-installed, and have even disabled `make install` in
> their build. See:
>
> https://github.com/google/googletest/blob/master/googletest/Makefile.am#L300
>
> I don't really understand what they think they're solving here but it
> is what it is and this seems to make it hard to use googletest in a
> non-bundled way. It's possible I misunderstood, though.

Hi, thanks for dropping in!

>From reading the comments in the Makefile, apparently they are trying to
enforce something called the One-Definition Rule:

https://en.wikipedia.org/wiki/One_Definition_Rule

The way Guix (and actually most distro build systems) works makes it
impossible for another definition to "leak" into the build container, so
I don't understand either what they are trying to solve.

> FWIW, Cap'n Proto only uses googletest to build its tests. It does not
> install any artifacts that were influenced by googletest.
>
> In any case, this dependency will be gone once I find time to do the
> next release. Sorry for the trouble in the meantime.

No worries, can't blame you for bundling something clearly designed to
be bundled. It's usually easier to remove, though ;)

> PS. regarding the man page, I believe Debian mostly generated this
> page from the capnp tool's help text. I'd accept a patch to
> c++/src/kj/main.c++ which adds some code to generate man XML format
> directly, so that we don't have to maintain the same text in multiple
> places.

I'm guessing it's the issue I opened that sent you here :)
My C++ fu is not strong enough to embark on that journey, but maybe if
you mention it in the ticket someone may pick it up.

Thanks for the feedback!

Marius

static library

[Vincent Legoll]

Hello,

I'm trying to package & use a static library (not mine), but it looks like
the right "-L" parameter is not automagically passed to the user package
(where the lib is in (inputs ...))

something like the following:

(define-public a (package ...))
(define-public b (package ... (inputs `(("liba" ,a))) ...))

I tried to put the right -L into make-flags & configure-flags myself, but
it failed with error, I don't even know if I have to do that :

(define-public b (package ...
(arguments
  `(#:make-flags (list (string-append "LDFLAGS=-L" ,a "/lib -la"))
#:configure-flags (list (string-append "LDFLAGS=-L" ,a "/lib -la"))

this ended with:

ERROR: In procedure primitive-load:
ERROR: In procedure scm_lreadr: /gnu/store/*-guile-builder:1:5211:
Unknown # object: #\<

which is in this :

[...]
#:phases %standard-phases #:locale "en_US.utf8" #:configure-flags
(list (string-append "LDFLAGS=-L" # "/lib -lurlmatch"))
[...]

I did find a use of static lib (apart from libgcc) in utils-linux but
nothing here seems special (even the *.a move looks optional)

Any help appreciated...

-- 
Vincent Legoll

Re: [PATCH] gnu: awesome: Add awesome-3.5

[ng0]

(Sending this back as a copy to the thread on the list.)

Hi,

Can you please CC the guix-devel@gnu.org list or just reply-to the list
when replying with the intention to not message offlist?

I think gnu.org does not set a reply-to thing, my email client does not
care or know about such settings though.

doncatnip  writes:

> On Thu, 25 Aug 2016 09:22:38 +
> ng0  wrote:
>
>> Hi,
>> 
>> gno  writes:
>> 
>> > Hi guix !
>> >
>> > Sure hope I'm doing this right as I'm new to this.
>> > These patches add Awesome 3.5.9 to the repository. I decided against
>> > updating since it may break peoples configurations. Awesome had API
>> > changes in between 3.4 and 3.5.
>> >
>> > Please have a look.  
>> 
>> Awesome! Many thanks for your first patch, I will test this in the
>> next days, maybe even today. I still have an 3.5.9 config from
>> another system in a backup.
>> 
>> Ah. I see what you mean by you decided against updating. I think this
>> is tricky. In my opinion awesome should provide the latest version,
>> while for example awesome-3.4.15 would provide an older version. I use
>> awesome, and this is what I would expect. When there was a version
>> update, it was up to me to figure out if my config still worked and
>> how to make it work again.
>> I would vote for 3.5 as the new awesome and 3.4 inherits from this.
>> But this can be applied after 3.5 is added I think?
>
> Yea, there might be a better (guix) way to do this. I just thought it
> might be good if those changes don't interfere at all with current
> system configs yet. Should be easy to change later on.
>
>> I did send in a patch to shorten the bloated description of awesome a
>> couple of days ago, please wait with applying my patch. I will send in
>> an update once we have this new awesome version update in tree.
>> 
>> > From cd3175f242450169b269ead777be6c7835476fba Mon Sep 17 00:00:00
>> > 2001 From: doncatnip 
>> > Date: Thu, 25 Aug 2016 01:43:53 +0200
>> > Subject: [PATCH 1/3] gnu: lua: Enable dynamic library support.
>> >
>> > * gnu/packages/lua.scm: (lua)[arguments]: Add make flags.  
>> 
>> You do more than just adding make flags, maybe let the commit message
>> say that you added the CFLAGS: -DLUA_USE_POSIX, -DLUA_USE_DLOPEN and
>> added LDFLAGS? I'm not sure how to express that, if at all. the git
>> log should have other cases.
>> Otherwise it looks good to me, this is just a formality the person
>> commiting your patch(es) could also change on your behalf.
>
> Add make flags which enable ld support as per headline, but yea maybe
> it's not descriptive enough. I took example from another patch recently
> posted in this list. I'd apperciate the person commiting the patch
> changing it to something more appropriate.
>
> Thanks for testing this !
>
>> > ---
>> >  gnu/packages/lua.scm | 6 +-
>> >  1 file changed, 5 insertions(+), 1 deletion(-)
>> >
>> > diff --git a/gnu/packages/lua.scm b/gnu/packages/lua.scm
>> > index b4b5dee..c68a3ff 100644
>> > --- a/gnu/packages/lua.scm
>> > +++ b/gnu/packages/lua.scm
>> > @@ -4,6 +4,7 @@
>> >  ;;; Copyright © 2014 Mark H Weaver 
>> >  ;;; Copyright © 2014 Andreas Enge 
>> >  ;;; Copyright © 2016 Efraim Flashner 
>> > +;;; Copyright © 2016 doncatnip 
>> >  ;;;
>> >  ;;; This file is part of GNU Guix.
>> >  ;;;
>> > @@ -51,7 +52,10 @@
>> > (modify-phases %standard-phases
>> >   (delete 'configure)
>> >   (replace 'build
>> > -   (lambda _ (zero? (system* "make" "CFLAGS=-fPIC"
>> > "linux"
>> > +   (lambda _ (zero? (system*
>> > +  "make" "LDFLAGS=-ldl"
>> > +  "CFLAGS=-fPIC -DLUA_USE_DLOPEN
>> > -DLUA_USE_POSIX"
>> > +  "linux"
>> >   (replace 'install
>> > (lambda* (#:key outputs #:allow-other-keys)
>> >   (let ((out (assoc-ref outputs "out")))
>> > -- 
>> > 2.9.3
>> >
>> > From 995b67847508a70782eb522cda52b0aa36a20bd2 Mon Sep 17 00:00:00
>> > 2001 From: doncatnip 
>> > Date: Thu, 25 Aug 2016 02:22:37 +0200
>> > Subject: [PATCH 2/3] gnu: lua: Add lua-lgi.
>> >
>> > * gnu/packages/lua.scm (lua-lgi): New variable.
>> > ---
>> >  gnu/packages/lua.scm | 71
>> > +++- 1 file
>> > changed, 70 insertions(+), 1 deletion(-)
>> >
>> > diff --git a/gnu/packages/lua.scm b/gnu/packages/lua.scm
>> > index c68a3ff..8af0318 100644
>> > --- a/gnu/packages/lua.scm
>> > +++ b/gnu/packages/lua.scm
>> > @@ -27,7 +27,12 @@
>> >#:use-module (guix download)
>> >#:use-module (guix build-system gnu)
>> >#:use-module (gnu packages)
>> > -  #:use-module (gnu packages readline))
>> > +  #:use-module (gnu packages readline)
>> > +  #:use-module (gnu packages glib)
>> > +  #:use-module (gnu packages libffi)
>> > +  #:use-module (gnu 

Re: [PATCH] gnu: awesome: Add awesome-3.5

[ng0]

ng0  writes:

>> Works for me (written from inside a running awesome-3.5.9).
>
> ng0@shadowwalker ~$ awesome --version
> awesome v3.5.9 (Mighty Ravendark)
> • Build: Sun Mar 06 14:05:54Z 2016 for x86_64 by gcc version 4.9.3 (@)
> • Compiled against Lua 5.2.4 (running with Lua 5.2)
> • D-Bus support: ✔

Great, the joy of a limited font... Nevermind this message then for
obvious reasons but rather take it as a note that dbus and hardening is
something we need to watch in the future ;)

> Having no dbus support will help with eventual hardening of Guix,
> but why do we not have it in awesome? 
> And why would we we need it (dbus support) at all? I don't even know why
> I used to build it with dbus support before. Works either way.

-- 
ng0
For non-prism friendly talk find me on http://www.psyced.org

Re: Store on separate partition

[Tomáš Čech]

On Wed, Aug 24, 2016 at 12:37:49PM +0200, Carlos Sánchez de La Lama wrote:

my (not very big) root partition is almost full, even after
garbage-collecting. I am trying to move the store to a separate
partition, but this is problematic as you need the store at boot time
for the system utilities (and to mount partitions, actually).


I tried to do it recently but failed.  My understanding is that it's
impossible, but I may be wrong.


After giving it some more thinking, I also think this is not
possible. The kernel image itself is in the store (and must be, because
you can have several system generations, each using a different
kernel). Same with initrd images.

I have finally moved the whole root to a bigger disk, not much different
to moving the store as root size (aside from the store) is rather small.


I think it is impossible now but to achieve that you'd need only:

1] to store /gnu/store on separate partition (so grub will find it with its 
--search)
2] and have some bind mounts ready in initrd stage.

It would be nice to have more flexibility in this area.

Best regards,

S_W


signature.asc
Description: Digital signature

Re: [PATCH 0/2] Fix IBus input methods.

[Ricardo Wurmus]

宋文武  writes:

> Ricardo Wurmus  writes:
>
>>   gnu: gtk+-2: Add patch to support GUIX_GTK2_IM_MODULE_FILE.
>>   gnu: gtk+: Add patch to support GUIX_GTK3_IM_MODULE_FILE.
>
> Look good to me!

Thanks!

What do you think: should this be a separate branch (e.g. “gtk-rebuild”)
or should it be pushed to “core-updates”?

~~ Ricardo

Re: [PATCH] gnunet-svn, gnunet-gtk-svn

[ng0]

Development of these -svn packages has been moved into guixpkgs, which
currently is a repository in early stages will be fixed up soon, created
for packages around psyced and ultimately the secushare development
prototypes.
This repository will also see some of the ebuild->guix package
transition I am doing for a long time now.

I quote myself:

For tor/onion access take a look at tor.n0.is.
Nixpkgs and Guixpkgs, including the packages for SecuShare, GNUnet,
psyced, libpsyc, psyclpc, and more.
These two repositories are transitioning work and will be functional in
the near future.
For Nix, use:
git://git.far37qbrwiredyo5.onion/nixpkgs.git
https://git.n0.is/nixpkgs.git
git://git.n0.is/nixpkgs.git

And for Guix use:
git://git.far37qbrwiredyo5.onion/guixpkgs.git
https://git.n0.is/guixpkgs.git
git://git.n0.is/guixpkgs.git
-- 
ng0
For non-prism friendly talk find me on http://www.psyced.org

Re: [PATCH] gnu: gnome-screenshot: Update to 3.20.1.

[宋文武]

ren...@openmailbox.org writes:

> This is a patch to update the version of gnome-screenshot to 3.20.1.
> Built, linted and tested.

Applied, thanks!

Re: [PATCH 0/2] Fix IBus input methods.

[宋文武]

Ricardo Wurmus  writes:

>   gnu: gtk+-2: Add patch to support GUIX_GTK2_IM_MODULE_FILE.
>   gnu: gtk+: Add patch to support GUIX_GTK3_IM_MODULE_FILE.

Look good to me!

Re: [PATCH] gnu: awesome: Add awesome-3.5

[ng0]

> Works for me (written from inside a running awesome-3.5.9).

ng0@shadowwalker ~$ awesome --version
awesome v3.5.9 (Mighty Ravendark)
• Build: Sun Mar 06 14:05:54Z 2016 for x86_64 by gcc version 4.9.3 (@)
• Compiled against Lua 5.2.4 (running with Lua 5.2)
• D-Bus support: ✔

Having no dbus support will help with eventual hardening of Guix,
but why do we not have it in awesome? 
And why would we we need it (dbus support) at all? I don't even know why
I used to build it with dbus support before. Works either way.
-- 
ng0
For non-prism friendly talk find me on http://www.psyced.org

Re: pre-release [PATCH] git-service [v2]

[ng0]

Hi,

thanks for finding the errors. I applied your suggestions but the
service still goes into respawn loop when the VM boots. Do you have any
idea why this could happen?

Alex Kost  writes:

> ng0 (2016-08-11 18:55 +0300) wrote:
>
>> ng0  writes:
>>
>>> As I wrote yesterday in freenode, disregard this patch. I
>>> succeeded and currently am debugging the VM.
>>
>> I had it working at some point, but only to find out that I am passing
>> something wrong in the service.
>> Can someone take a look at this service and help me out?
>
> Hi, I didn't try this service, but I see 2 mistakes in the code.
>
> [...]
>> +(define (git-shepherd-service config)
>> +  "Return a  for git with CONFIG."
>> +  (define git (git-configuration-git config))
>> +
>> +  (define git-command
>> +#~(list
>> +   (string-append #$git "/bin/git") "daemon" "--syslog"
>> +   "--informative-errors"
>> +   "--port=" (number->string (git-configuration-port config))
>> +   "--base-path=" (git-configuration-base-path config)))
>
> 1. This should be:
>
>   "--port=" #$(number->string (git-configuration-port config))
>   "--base-path=" #$(git-configuration-base-path config)))
>
> Note ‘#$’ before expressions.  Without it, these expressions will stay
> the same in the final making service code (see below).
>
>> +  (define requires
>> +'(networking syslogd))
>> +
>> +  (list (shepherd-service
>> + (documentation "Git daemon server for git repositories")
>> + (requirement requires)
>> + (provision '(git))
>> + (start #~(make-forkexec-constructor #$@git-command))
>
> 2. This should be:
>
> (start #~(make-forkexec-constructor #$git-command))
>
> Note ‘#$@ → #$’.  With #$@, the list (I mean git-command) is "spliced",
> so the result in "/gnu/store/...-shepherd-git.scm" will be:
>
> (make 
>   ...
>   #:start
>   (make-forkexec-constructor list
>  (string-append "/gnu/store/…" "/bin/git")
>  "daemon" "--syslog" "--informative-errors"
>  "--port=" (number->string
> (git-configuration-port config))
>  "--base-path="
>  (git-configuration-base-path config))
>   ...)
>
> While it should be: (make-forkexec-constructor (list ...))
>
> Also I have a question about the final command to start git daemon.  It
> would look like this:
>
>   git daemon --syslog --informative-errors --port=9418 
> --base-path=/var/git/repositories
>
> Is it intentional?  I mean "/var/git/repositories" does not exist and
> you don't create it at activation time, so the service (with the default
> 'base-path') will fail anyway.
>
> But you create "/var/run/git-daemon".  Is it really needed?  I know
> nothing about "git daemon", but IIUC it starts successfully without this
> directory.
>
> -- 
> Alex

-- 
ng0
For non-prism friendly talk find me on http://www.psyced.org

Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PATCH] gnu: gnu: messaging: Use license: prefix.

[ng0]

ng0  writes:

> These 3 patches enable us to have a functional pybitmessage version
> 0.6.1, released 2 days ago.
>
> For tests you can use either the test channel which can be found on
> bitmessage.org (or in the application itself? I don't know, I'm no
> newcomer to this application) or the channel I did setup a while ago
> (blame my window manager if there's a typo, the copy & paste is
> sometimes stuck):
> BM-2cTPsDEX29yRnrAmyfwZhC3RySsK4wnQUA
> [chan] gnuguixchan
>
> From 8687409cf6f424958e222de9eddf4c77750ecc57 Mon Sep 17 00:00:00 2001
> From: ng0 
> Date: Tue, 23 Aug 2016 10:13:59 +
> Subject: [PATCH 1/3] gnu: Add python2-pyqt-4.
>
> * gnu/packages/qt.scm (python2-pyqt-4): New variable.
> ---
>  gnu/packages/qt.scm | 10 ++
>  1 file changed, 10 insertions(+)
>
> diff --git a/gnu/packages/qt.scm b/gnu/packages/qt.scm
> index a7eee7c..99c12aa 100644
> --- a/gnu/packages/qt.scm
> +++ b/gnu/packages/qt.scm
> @@ -3,6 +3,7 @@
>  ;;; Copyright © 2015 Sou Bunnbu 
>  ;;; Copyright © 2015 Ludovic Courtès 
>  ;;; Copyright © 2015, 2016 Efraim Flashner 
> +;;; Copyright © 2016 ng0 
>  ;;;
>  ;;; This file is part of GNU Guix.
>  ;;;
> @@ -1057,6 +1058,15 @@ contain over 620 classes.")
>   %standard-phases)))
>  (license (list gpl2 gpl3 ; choice of either license
>  
> +(define-public python2-pyqt-4
> +  (package (inherit python-pyqt-4)
> +   (name "python2-pyqt-4")
> +   (native-inputs
> +`(("python-sip" ,python2-sip)
> +  ("qt" ,qt-4)))
> +   (inputs
> +`(("python" ,python-2)
> +
>  (define-public qtkeychain
>(package
>  (name "qtkeychain")
> -- 
> 2.9.3
>
> From 523d7da2b50028826de9f306171a60f77d25625e Mon Sep 17 00:00:00 2001
> From: ng0 
> Date: Tue, 23 Aug 2016 11:07:17 +
> Subject: [PATCH 2/3] gnu: messaging: Use license: prefix.
>
> * gnu/packages/disk.scm (define-module): Import guix licenses with a prefix.
> (libotr): Use the import prefix.
> (bitlbee): Likewise.
> (hexchat): Likewise.
> (ngircd): Likewise.
> (pidgin): Likewise.
> (pidgin-otr): Likewise.
> (znc): Likewise.
> (python-nbxmpp): Likewise.
> (gajim): Likewise.
> ---
>  gnu/packages/messaging.scm | 31 +++
>  1 file changed, 15 insertions(+), 16 deletions(-)
>
> diff --git a/gnu/packages/messaging.scm b/gnu/packages/messaging.scm
> index de9ac17..b0546f2 100644
> --- a/gnu/packages/messaging.scm
> +++ b/gnu/packages/messaging.scm
> @@ -5,6 +5,7 @@
>  ;;; Copyright © 2015 Andreas Enge 
>  ;;; Copyright © 2015 Ricardo Wurmus 
>  ;;; Copyright © 2015 Efraim Flashner 
> +;;; Copyright © 2016 ng0 
>  ;;;
>  ;;; This file is part of GNU Guix.
>  ;;;
> @@ -22,9 +23,7 @@
>  ;;; along with GNU Guix.  If not, see .
>  
>  (define-module (gnu packages messaging)
> -  #:use-module ((guix licenses)
> -#:select (gpl3+ gpl2+ gpl2 lgpl2.1 lgpl2.0+ bsd-2 
> non-copyleft
> -  asl2.0))
> +  #:use-module ((guix licenses) #:prefix license:)
>#:use-module (guix utils)
>#:use-module (guix packages)
>#:use-module (guix download)
> @@ -89,7 +88,7 @@ correspondent is assured the messages he sees are authentic 
> and
>  unmodified.  (4) Perfect forward secrecy: If you lose control of your private
>  keys, no previous conversation is compromised.")
>  (home-page "https://otr.cypherpunks.ca/;)
> -(license (list lgpl2.1 gpl2
> +(license (list license:lgpl2.1 license:gpl2
>  
>  ;; These patches together fix https://github.com/bitlbee/bitlbee/pull/55, are
>  ;; already upstream, and should be unnecessary when the next bitlbee comes
> @@ -153,7 +152,7 @@ Google Talk), MSN Messenger, Yahoo!  Messenger, AIM and 
> ICQ, and the Twitter
>  microblogging network (plus all other Twitter API compatible services like
>  identi.ca and status.net).")
>  (home-page "http://www.bitlbee.org/;)
> -(license (list gpl2+ bsd-2
> +(license (list license:gpl2+ license:bsd-2
>  
>  (define-public hexchat
>(package
> @@ -187,7 +186,7 @@ conversation and the list of users.  It uses colors to 
> differentiate between
>  users and to highlight messages.  It checks spelling using available
>  dictionaries.  HexChat can be extended with multiple addons.")
>  (home-page "http://hexchat.net/;)
> -(license gpl2+)))
> +(license license:gpl2+)))
>  
>  (define-public ngircd
>(package
> @@ -252,7 +251,7 @@ dictionaries.  HexChat can be extended with multiple 
> addons.")
>   "ngIRCd is a lightweight Internet Relay Chat server for small or private
>  networks.  It is easy to configure, can cope with dynamic IP addresses, and
>  supports IPv6, SSL-protected connections as well as PAM for 

Re: [PATCH] gnu: awesome: Add awesome-3.5

[ng0]

ng0  writes:

> Hi,
>
> gno  writes:
>
>> Hi guix !
>>
>> Sure hope I'm doing this right as I'm new to this.
>> These patches add Awesome 3.5.9 to the repository. I decided against
>> updating since it may break peoples configurations. Awesome had API
>> changes in between 3.4 and 3.5.
>>
>> Please have a look.
>
> Awesome! Many thanks for your first patch, I will test this in the next
> days, maybe even today. I still have an 3.5.9 config from another system
> in a backup.
>
> Ah. I see what you mean by you decided against updating. I think this is
> tricky. In my opinion awesome should provide the latest version, while
> for example awesome-3.4.15 would provide an older version. I use
> awesome, and this is what I would expect. When there was a version
> update, it was up to me to figure out if my config still worked and how
> to make it work again.
> I would vote for 3.5 as the new awesome and 3.4 inherits from this. But
> this can be applied after 3.5 is added I think?
>
> I did send in a patch to shorten the bloated description of awesome a
> couple of days ago, please wait with applying my patch. I will send in
> an update once we have this new awesome version update in tree.
>
>> From cd3175f242450169b269ead777be6c7835476fba Mon Sep 17 00:00:00 2001
>> From: doncatnip 
>> Date: Thu, 25 Aug 2016 01:43:53 +0200
>> Subject: [PATCH 1/3] gnu: lua: Enable dynamic library support.
>>
>> * gnu/packages/lua.scm: (lua)[arguments]: Add make flags.
>
> You do more than just adding make flags, maybe let the commit message
> say that you added the CFLAGS: -DLUA_USE_POSIX, -DLUA_USE_DLOPEN and
> added LDFLAGS? I'm not sure how to express that, if at all. the git log
> should have other cases.
> Otherwise it looks good to me, this is just a formality the person
> commiting your patch(es) could also change on your behalf.
>
>> ---
>>  gnu/packages/lua.scm | 6 +-
>>  1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/gnu/packages/lua.scm b/gnu/packages/lua.scm
>> index b4b5dee..c68a3ff 100644
>> --- a/gnu/packages/lua.scm
>> +++ b/gnu/packages/lua.scm
>> @@ -4,6 +4,7 @@
>>  ;;; Copyright © 2014 Mark H Weaver 
>>  ;;; Copyright © 2014 Andreas Enge 
>>  ;;; Copyright © 2016 Efraim Flashner 
>> +;;; Copyright © 2016 doncatnip 
>>  ;;;
>>  ;;; This file is part of GNU Guix.
>>  ;;;
>> @@ -51,7 +52,10 @@
>> (modify-phases %standard-phases
>>   (delete 'configure)
>>   (replace 'build
>> -   (lambda _ (zero? (system* "make" "CFLAGS=-fPIC" "linux"
>> +   (lambda _ (zero? (system*
>> +  "make" "LDFLAGS=-ldl"
>> +  "CFLAGS=-fPIC -DLUA_USE_DLOPEN 
>> -DLUA_USE_POSIX"
>> +  "linux"
>>   (replace 'install
>> (lambda* (#:key outputs #:allow-other-keys)
>>   (let ((out (assoc-ref outputs "out")))
>> -- 
>> 2.9.3
>>
>> From 995b67847508a70782eb522cda52b0aa36a20bd2 Mon Sep 17 00:00:00 2001
>> From: doncatnip 
>> Date: Thu, 25 Aug 2016 02:22:37 +0200
>> Subject: [PATCH 2/3] gnu: lua: Add lua-lgi.
>>
>> * gnu/packages/lua.scm (lua-lgi): New variable.
>> ---
>>  gnu/packages/lua.scm | 71 
>> +++-
>>  1 file changed, 70 insertions(+), 1 deletion(-)
>>
>> diff --git a/gnu/packages/lua.scm b/gnu/packages/lua.scm
>> index c68a3ff..8af0318 100644
>> --- a/gnu/packages/lua.scm
>> +++ b/gnu/packages/lua.scm
>> @@ -27,7 +27,12 @@
>>#:use-module (guix download)
>>#:use-module (guix build-system gnu)
>>#:use-module (gnu packages)
>> -  #:use-module (gnu packages readline))
>> +  #:use-module (gnu packages readline)
>> +  #:use-module (gnu packages glib)
>> +  #:use-module (gnu packages libffi)
>> +  #:use-module (gnu packages xorg)
>> +  #:use-module (gnu packages pkg-config)
>> +  #:use-module (gnu packages gtk))
>>  
>>  (define-public lua
>>(package
>> @@ -111,3 +116,67 @@ programming language.  Lua is a powerful, dynamic and 
>> light-weight programming
>>  language.  It may be embedded or used as a general-purpose, stand-alone
>>  language.")
>>  (license x11)))
>> +
>> +(define-public lua-lgi
>> +  (package
>> +(name "lua-lgi")
>> +(version "0.9.1")
>> +(source
>> +  (origin
>> +(method url-fetch)
>> +(uri (string-append
>> +  "https://github.com/pavouk/lgi/archive/;
>> +  version ".tar.gz"))
>> +(file-name (string-append name "-" version ".tar.gz"))
>> +(sha256 (base32 
>> "1fmgdl5y4ph3yc6ycg865s3vai1rjkyda61cgqxk6zd13hmznw0c"
>> +(build-system gnu-build-system)
>> +(arguments
>> + '(#:phases
>> +   (modify-phases %standard-phases
>> + (replace 'configure
>> +   (lambda* (#:key inputs #:allow-other-keys)
>> + ; needs to 

Re: [PATCH] gnu: awesome: Add awesome-3.5

[ng0]

Hi,

gno  writes:

> Hi guix !
>
> Sure hope I'm doing this right as I'm new to this.
> These patches add Awesome 3.5.9 to the repository. I decided against
> updating since it may break peoples configurations. Awesome had API
> changes in between 3.4 and 3.5.
>
> Please have a look.

Awesome! Many thanks for your first patch, I will test this in the next
days, maybe even today. I still have an 3.5.9 config from another system
in a backup.

Ah. I see what you mean by you decided against updating. I think this is
tricky. In my opinion awesome should provide the latest version, while
for example awesome-3.4.15 would provide an older version. I use
awesome, and this is what I would expect. When there was a version
update, it was up to me to figure out if my config still worked and how
to make it work again.
I would vote for 3.5 as the new awesome and 3.4 inherits from this. But
this can be applied after 3.5 is added I think?

I did send in a patch to shorten the bloated description of awesome a
couple of days ago, please wait with applying my patch. I will send in
an update once we have this new awesome version update in tree.

> From cd3175f242450169b269ead777be6c7835476fba Mon Sep 17 00:00:00 2001
> From: doncatnip 
> Date: Thu, 25 Aug 2016 01:43:53 +0200
> Subject: [PATCH 1/3] gnu: lua: Enable dynamic library support.
>
> * gnu/packages/lua.scm: (lua)[arguments]: Add make flags.

You do more than just adding make flags, maybe let the commit message
say that you added the CFLAGS: -DLUA_USE_POSIX, -DLUA_USE_DLOPEN and
added LDFLAGS? I'm not sure how to express that, if at all. the git log
should have other cases.
Otherwise it looks good to me, this is just a formality the person
commiting your patch(es) could also change on your behalf.

> ---
>  gnu/packages/lua.scm | 6 +-
>  1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/packages/lua.scm b/gnu/packages/lua.scm
> index b4b5dee..c68a3ff 100644
> --- a/gnu/packages/lua.scm
> +++ b/gnu/packages/lua.scm
> @@ -4,6 +4,7 @@
>  ;;; Copyright © 2014 Mark H Weaver 
>  ;;; Copyright © 2014 Andreas Enge 
>  ;;; Copyright © 2016 Efraim Flashner 
> +;;; Copyright © 2016 doncatnip 
>  ;;;
>  ;;; This file is part of GNU Guix.
>  ;;;
> @@ -51,7 +52,10 @@
> (modify-phases %standard-phases
>   (delete 'configure)
>   (replace 'build
> -   (lambda _ (zero? (system* "make" "CFLAGS=-fPIC" "linux"
> +   (lambda _ (zero? (system*
> +  "make" "LDFLAGS=-ldl"
> +  "CFLAGS=-fPIC -DLUA_USE_DLOPEN -DLUA_USE_POSIX"
> +  "linux"
>   (replace 'install
> (lambda* (#:key outputs #:allow-other-keys)
>   (let ((out (assoc-ref outputs "out")))
> -- 
> 2.9.3
>
> From 995b67847508a70782eb522cda52b0aa36a20bd2 Mon Sep 17 00:00:00 2001
> From: doncatnip 
> Date: Thu, 25 Aug 2016 02:22:37 +0200
> Subject: [PATCH 2/3] gnu: lua: Add lua-lgi.
>
> * gnu/packages/lua.scm (lua-lgi): New variable.
> ---
>  gnu/packages/lua.scm | 71 
> +++-
>  1 file changed, 70 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/packages/lua.scm b/gnu/packages/lua.scm
> index c68a3ff..8af0318 100644
> --- a/gnu/packages/lua.scm
> +++ b/gnu/packages/lua.scm
> @@ -27,7 +27,12 @@
>#:use-module (guix download)
>#:use-module (guix build-system gnu)
>#:use-module (gnu packages)
> -  #:use-module (gnu packages readline))
> +  #:use-module (gnu packages readline)
> +  #:use-module (gnu packages glib)
> +  #:use-module (gnu packages libffi)
> +  #:use-module (gnu packages xorg)
> +  #:use-module (gnu packages pkg-config)
> +  #:use-module (gnu packages gtk))
>  
>  (define-public lua
>(package
> @@ -111,3 +116,67 @@ programming language.  Lua is a powerful, dynamic and 
> light-weight programming
>  language.  It may be embedded or used as a general-purpose, stand-alone
>  language.")
>  (license x11)))
> +
> +(define-public lua-lgi
> +  (package
> +(name "lua-lgi")
> +(version "0.9.1")
> +(source
> +  (origin
> +(method url-fetch)
> +(uri (string-append
> +  "https://github.com/pavouk/lgi/archive/;
> +  version ".tar.gz"))
> +(file-name (string-append name "-" version ".tar.gz"))
> +(sha256 (base32 
> "1fmgdl5y4ph3yc6ycg865s3vai1rjkyda61cgqxk6zd13hmznw0c"
> +(build-system gnu-build-system)
> +(arguments
> + '(#:phases
> +   (modify-phases %standard-phases
> + (replace 'configure
> +   (lambda* (#:key inputs #:allow-other-keys)
> + ; needs to load cairo dynamically
> + (let* ((cairo (string-append
> + (assoc-ref inputs "cairo") "/lib" )))
> +   (setenv "LD_LIBRARY_PATH" cairo ))
> +
> 

Re: [PATCH 0/2] Fix IBus input methods.

[Ricardo Wurmus]

Ricardo Wurmus  writes:

> What doesn't yet work is IBus input methods using the simple engine, such as
> Arabic, but this seems unrelated.

That’s been fixed in d37f00b97fc12a677409e13759fe3edc6ffede2c.

IBus had a couple of hard-coded paths and missing
inputs.  Arabic, English Qwerty, English Dvorak, German Qwertz, and
Chinese (via ibus-libpinyin) all work for me now.

Note that “Use system keyboard layout” in the “Advanced” tab of
“ibus-setup” has to be *unchecked* for the simple engine to work right.
With that option checked it would be stuck at English Dvorak, which had
been set via setxkbmap at the start of the session.

~~ Ricardo

Re: [PATCH] gnu: Add capnproto.

[Kenton Varda]

Hi, Cap'n Proto upstream author here. Noticed this thread in a Google
search, thought I'd comment.

To shed some light on the googletest situation:

The googletest maintainers have deemed that googletest should never
ever be system-installed, and have even disabled `make install` in
their build. See:

https://github.com/google/googletest/blob/master/googletest/Makefile.am#L300

I don't really understand what they think they're solving here but it
is what it is and this seems to make it hard to use googletest in a
non-bundled way. It's possible I misunderstood, though.

FWIW, Cap'n Proto only uses googletest to build its tests. It does not
install any artifacts that were influenced by googletest.

In any case, this dependency will be gone once I find time to do the
next release. Sorry for the trouble in the meantime.

-Kenton

PS. regarding the man page, I believe Debian mostly generated this
page from the capnp tool's help text. I'd accept a patch to
c++/src/kj/main.c++ which adds some code to generate man XML format
directly, so that we don't have to maintain the same text in multiple
places.

Re: /var/guix/gcroot/profiles points to non-existing /mnt subdirectory

[Vincent Legoll]

Hi,

> In my Guix SD installation, I have the following contents inside
> /var/guix/gcroots:
>
> lrwxrwxrwx 1 root root 18 ago 24 16:45 booted-system -> /run/booted-system
> lrwxrwxrwx 1 root root 19 ago 24 16:45 current-system -> /run/current-system
> lrwxrwxrwx 1 root root 52 ago 24 16:45 grub.cfg -> 
> /gnu/store/rvcr64gcqvay3g68bsrbcp9kahsnh7an-grub.cfg
> lrwxrwxrwx 1 root root 22 ago 24 16:44 profiles -> /mnt/var/guix/profiles
>
> I have tried a fresh installation, closely following instructions in the
> manual, and it happens there as well. I am using 0.10 installation USB
> image, I don't know if it happens with 0.11.

I'm on 0.11 GuixSD USB install, and I can see the same:

vince@guixsd ~$ l /var/guix/gcroots/profiles
lrwxrwxrwx 1 root root 22 Aug  5 00:29 /var/guix/gcroots/profiles ->
/mnt/var/guix/profiles

-- 
Vincent Legoll

/var/guix/gcroot/profiles points to non-existing /mnt subdirectory

[Carlos Sánchez de La Lama]

Hi,

In my Guix SD installation, I have the following contents inside
/var/guix/gcroots:

lrwxrwxrwx 1 root root 18 ago 24 16:45 booted-system -> /run/booted-system
lrwxrwxrwx 1 root root 19 ago 24 16:45 current-system -> /run/current-system
lrwxrwxrwx 1 root root 52 ago 24 16:45 grub.cfg -> 
/gnu/store/rvcr64gcqvay3g68bsrbcp9kahsnh7an-grub.cfg
lrwxrwxrwx 1 root root 22 ago 24 16:44 profiles -> /mnt/var/guix/profiles

However, /mnt/var/guix/profiles does not exist (there is nothing in
/mnt). Shouldn't it point to /var/guix/profiles?

I have tried a fresh installation, closely following instructions in the
manual, and it happens there as well. I am using 0.10 installation USB
image, I don't know if it happens with 0.11.

Can someone explain if this symlink is correct, and what is its purpose
in that case?

Thanks!

Carlos

[PATCH] gnu: Add emacs-ahungry-theme.

[Alex Vong]

Hi,

This patch adds ahungry theme from elpa, which I am currently using. I
test the patch by `./pre-inst-env guix install emacs-ahungry-theme' and
launching emacs. It works fine on my machine.

Cheers,
Alex

>From ce1481926e96728327bd7e517d8d2bdfa990b989 Mon Sep 17 00:00:00 2001
From: Alex Vong 
Date: Thu, 25 Aug 2016 13:49:31 +0800
Subject: [PATCH] gnu: Add emacs-ahungry-theme.

* gnu/packages/emacs.scm (emacs-ahungry-theme): New variable.
---
 gnu/packages/emacs.scm | 21 +
 1 file changed, 21 insertions(+)

diff --git a/gnu/packages/emacs.scm b/gnu/packages/emacs.scm
index dfe5ce7..d072141 100644
--- a/gnu/packages/emacs.scm
+++ b/gnu/packages/emacs.scm
@@ -15,6 +15,7 @@
 ;;; Copyright © 2016 ng0 
 ;;; Copyright © 2016 Alex Griffin 
 ;;; Copyright © 2016 Nicolas Goaziou 
+;;; Copyright © 2016 Alex Vong 
 ;;;
 ;;; This file is part of GNU Guix.
 ;;;
@@ -2981,3 +2982,23 @@ lists, and project planning with a fast and effective plain-text system.  It
 also is an authoring system with unique support for literate programming and
 reproducible research.")
 (license license:gpl3+)))
+
+(define-public emacs-ahungry-theme
+  (package
+(name "emacs-ahungry-theme")
+(version "1.3.0")
+(source
+ (origin (method url-fetch)
+ (uri (string-append "http://elpa.gnu.org/packages/ahungry-theme-;
+ version ".tar"))
+ (sha256
+  (base32 "1p2zaq0s4bbl5cx6wyab24wamw7m0mysb0v47dqjmnvfc25z84rq"
+(build-system emacs-build-system)
+(home-page "https://github.com/ahungry/color-theme-ahungry;)
+(synopsis
+ "Ahungry color theme for Emacs.  Make sure to (load-theme 'ahungry).")
+(description "Bright and bold color theme for GNU Emacs.
+
+If you load it from a terminal, you will be able to make use of the transparent
+background.  If you load it from a GUI, it will default to a dark background.")
+(license license:gpl3+)))
-- 
2.9.3