[PATCH] gnu: Add python-pypump

[Dylan Jeffers]

When submitting patches that require other patches I've submitted,
should I put them together in a single patch, or keep them separate
like this?

DylanFrom 05af66570794e80b4e8ce2447152eba251d67759 Mon Sep 17 00:00:00 2001
From: Dylan Jeffers 
Date: Fri, 12 Aug 2016 18:26:18 -0700
Subject: [PATCH] gnu: Add python-pypump

* gnu/packages/python.scm (python-pypump, python2-pypump): New
* variables.
---
 gnu/packages/python.scm | 32 
 1 file changed, 32 insertions(+)

diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
index 6ff1c5c..2f67ab7 100644
--- a/gnu/packages/python.scm
+++ b/gnu/packages/python.scm
@@ -24,6 +24,7 @@
 ;;; Copyright © 2016 Sou Bunnbu 
 ;;; Copyright © 2016 Troy Sankey 
 ;;; Copyright © 2016 ng0 
+;;; Copyright © 2016 Dylan Jeffers 
 ;;;
 ;;; This file is part of GNU Guix.
 ;;;
@@ -9852,3 +9853,34 @@ etc.")
 (package
   (inherit base)
   (name "ptpython2"
+
+(define-public python-pypump
+  (package
+(name "python-pypump")
+(version "0.6")
+(source
+ (origin
+   (method git-fetch)
+   (uri (git-reference
+ (url "https://github.com/xray7224/PyPump";)
+ (commit  "6b612a7ed3c5a9b0a0190f3999fcddb851d1900f")))
+   (file-name (string-append name "-" version))
+   (sha256
+(base32
+ "0xy9kw54a2dasc5jig1rmllwv6y3pngbw8pvi0yx2qfpswgr5qbg"
+(build-system python-build-system)
+(native-inputs
+ `(("pkg-config" ,pkg-config)))
+(inputs
+ `(("python-requests" ,python-requests)
+   ("python-oauthlib" ,python-oauthlib)
+   ("python-requests-oauthlib" ,python-requests-oauthlib)
+   ("python-dateutil-2" ,python-dateutil-2)))
+(home-page "https://github.com/xray7224/PyPump";)
+(synopsis "Python Pump.io library")
+(description "PyPump is a simple but powerful and pythonic
+way of interfacing with the pump.io API.")
+(license gpl3+)))
+
+(define-public python2-pypump
+  (package-with-python2 python-pypump))
-- 
2.7.3

[PATCH] gnu: Add python-requests-oauthlib

[Dylan Jeffers]

From 5d475aff4eb6e9ec9058b80e5a40bb0cff6f5d9d Mon Sep 17 00:00:00 2001
From: Dylan Jeffers 
Date: Fri, 12 Aug 2016 18:10:16 -0700
Subject: [PATCH] gnu: Add python-requests-oauthlib.

* gnu/packages/python.scm (python-requests-oauthlib,
python2-requests-oauthlib): New variables.
---
 gnu/packages/python.scm | 40 +++-
 1 file changed, 39 insertions(+), 1 deletion(-)

diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
index 6ff1c5c..db0388e 100644
--- a/gnu/packages/python.scm
+++ b/gnu/packages/python.scm
@@ -1,4 +1,3 @@
-;;; GNU Guix --- Functional package management for GNU
 ;;; Copyright © 2013 Nikita Karetnikov 
 ;;; Copyright © 2013, 2014, 2015, 2016 Ludovic Courtès 
 ;;; Copyright © 2013, 2014, 2015, 2016 Andreas Enge 
@@ -24,6 +23,7 @@
 ;;; Copyright © 2016 Sou Bunnbu 
 ;;; Copyright © 2016 Troy Sankey 
 ;;; Copyright © 2016 ng0 
+;;; Copyright © 2016 Dylan Jeffers 
 ;;;
 ;;; This file is part of GNU Guix.
 ;;;
@@ -70,6 +70,7 @@
   #:use-module (gnu packages multiprecision)
   #:use-module (gnu packages networking)
   #:use-module (gnu packages ncurses)
+  #:use-module (gnu packages openstack)
   #:use-module (gnu packages pcre)
   #:use-module (gnu packages perl)
   #:use-module (gnu packages pkg-config)
@@ -9852,3 +9853,40 @@ etc.")
 (package
   (inherit base)
   (name "ptpython2"
+
+(define-public python-requests-oauthlib
+  (package
+(name "python-requests-oauthlib")
+(version "0.6.2")
+(source
+ (origin
+   (method url-fetch)
+   (uri (pypi-uri "requests-oauthlib" version))
+   (sha256
+(base32
+ "0ykff67sjcl227c23g0rxzfx34rr5bf21kwv0z3zmgk0lfmch7hn"
+(build-system python-build-system)
+(arguments
+ `(#:phases
+   (modify-phases %standard-phases
+ ;; removes tests that require network access
+ (add-before 'check 'pre-check
+   (lambda _ (delete-file "tests/test_core.py")
+   #t)
+(native-inputs
+ `(("python-requests-mock" ,python-requests-mock)
+   ("python-mock" ,python-mock)))
+(inputs
+ `(("python-oauthlib" ,python-oauthlib)
+   ("python-requests" ,python-requests)))
+(home-page
+ "https://github.com/requests/requests-oauthlib";)
+(synopsis
+ "OAuthlib authentication support for Requests")
+(description
+ "This package provides first-class OAuth library
+support for python-requests.")
+(license isc)))
+
+(define-public python2-requests-oauthlib
+  (package-with-python2 python-requests-oauthlib))
-- 
2.7.3

Re: [PATCH 05/26] gnu: kde-frameworks: Add bluez-qt.

[宋文武]

David Craven  writes:

>> I'll use 'BlueZ', the description of bluez uses it.
>
> Does this mean you are applying the patch or that you want me to resubmit?

Oh, sorry for the confusing, I think you will push them yourself.

And those KDE patches all look good to me, I haven't build them but
think they're ready to be commited (not by me).

Thanks for your hard work!

Re: [PATCH 2/2] gnu: Add python-kivy

[Dylan Jeffers]

On Fri, 12 Aug 2016 17:21:31 -0700
Dylan Jeffers  wrote:

> On Fri, 12 Aug 2016 02:06:48 -0400
> Mark H Weaver  wrote:
> 
> > Dylan Jeffers  writes:
> >   
> > > From 25cd777ff3a2429cbb257e02603d6bef78d1564f Mon Sep 17 00:00:00
> > > 2001 From: Dylan Jeffers 
> > > Date: Thu, 11 Aug 2016 17:15:47 -0700
> > > Subject: [PATCH] gnu: Add python-kivy.
> > >
> > > * gnu/packages/python.scm (python-kivy): New variable.
> > > * gnu/packages/python.scm (python2-kivy: New variable.
> > 
> > This should be:
> > 
> > * gnu/packages/python.scm (python-kivy, python2-kivy): New
> > variables. 
> > > ---
> > >  gnu/packages/python.scm | 54
> > > + 1 file changed,
> > > 54 insertions(+)
> > >
> > > diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
> > > index 6ff1c5c..9f14e80 100644
> > > --- a/gnu/packages/python.scm
> > > +++ b/gnu/packages/python.scm
> > > @@ -24,6 +24,7 @@
> > >  ;;; Copyright © 2016 Sou Bunnbu 
> > >  ;;; Copyright © 2016 Troy Sankey 
> > >  ;;; Copyright © 2016 ng0 
> > > +;;; Copyright © 2016 Dylan Jeffers
> > > 
> > 
> > Your mail client failed to specify UTF-8 encoding for this
> > attachment, so the copyright symbols above are coming through as
> > pairs of raw octets.  We can fix this up manually if needed, but it
> > would be great if you could fix your mail client configuration.
> >   
> > >  ;;;
> > >  ;;; This file is part of GNU Guix.
> > >  ;;;
> > > @@ -88,6 +89,9 @@
> > >#:use-module (gnu packages tcl)
> > >#:use-module (gnu packages bdw-gc)
> > >#:use-module (gnu packages pcre)
> > > +  #:use-module (gnu packages gstreamer)
> > > +  #:use-module (gnu packages sdl)
> > > +  #:use-module (gnu packages gl)
> > >#:use-module (guix packages)
> > >#:use-module (guix download)
> > >#:use-module (guix git-download)
> > > @@ -9852,3 +9856,53 @@ etc.")
> > >  (package
> > >(inherit base)
> > >(name "ptpython2"
> > > +
> > > +(define-public python-kivy
> > > +  (let ((commit
> > > + "a988c5e7a47da56263ff39514264a3de516ef2fe"))
> > > +(package
> > > +  (name "python-kivy")
> > > +  (version "1.9.1")
> > > +  (source
> > > +   (origin
> > > + (method git-fetch)
> > > + (uri (git-reference
> > > +   (url "https://github.com/kivy/kivy";)
> > > +   (commit commit)))
> > > + (file-name (string-append name "-" version
> > > "-dev.tar.gz"))
> > > + (sha256
> > > +  (base32
> > > +
> > > "0jk92b4a8l7blkvkgkjihk171s0dfnq582cckff5srwc8kal5m0p"
> > 
> > This commit does not match the version string.  Version 1.9.1
> > corresponds to commit 7e789b24cdb0ee044469d7bc42da9e4146674a18, from
> > 1 January 2016, but the commit you've selected is much later, from
> > 26 July 2016.
> > 
> > We generally prefer to use tarball releases, unless there is a
> > compelling reason to use a non-release commit.
> > 
> > Is there a compelling reason?  If not, please use the 1.9.1 release
> > tarball from ,
> > along with the 'file-name' field.  
> 
> Yes, the new dev version of kivy has a number of important
> enhancements that are not available in 1.9.1.
> 
> > > +  (build-system python-build-system)
> > > +  (arguments
> > > +   `(#:tests? #f  ; Tests require many optional
> > > packages
> > > + #:phases
> > > + (modify-phases %standard-phases
> > > +   (replace 'build (lambda _ (zero? (system* "make"
> > > "force"
> > > +   (add-after 'patch-generated-file-shebangs
> > > 'set-sdl-paths
> > > + (lambda* (#:key inputs #:allow-other-keys)
> > > +   (setenv "KIVY_SDL2_PATH"
> > > +   (string-append (assoc-ref inputs
> > > "sdl-union")
> > > +  "/include/SDL2"))
> > > +   #t)
> > > +  (native-inputs
> > > +   `( ("pkg-config" ,pkg-config)))
> > 
> > Please remove the space between the open parentheses above.
> >   
> > > +  (inputs
> > > +   `(("python-cython" ,python-cython)
> > > + ("gstreamer" ,gstreamer)
> > > + ("mesa" ,mesa)
> > > + ("sdl-union"
> > > +  ,(sdl-union (list sdl2 sdl2-image sdl2-mixer
> > > sdl2-ttf)
> > > +  (home-page "http://kivy.org";)
> > > +  (synopsis
> > > +   "Multitouch application framework")
> > > +  (description
> > > +   "A software library for rapid development of
> > > +hardware-accelerated multitouch applications.")
> > > +  (license license:expat
> > > +
> > > +(define-public python2-kivy
> > > +  (let ((base (package-with-python2 (strip-python2-variant
> > > python-kivy
> > > +(package
> > > +  (inherit base)
> > > +  (name "python2-kivy"
> > 
> > Can you send an updated patch?
> > 
> >   Thanks,
> > Mark  
> 
> Updated python-kivy.patch
> 
> Best,
> Dylan

Re: [PATCH 2/2] python-kivy

[Dylan Jeffers]

On Fri, 12 Aug 2016 02:06:48 -0400
Mark H Weaver  wrote:

> Dylan Jeffers  writes:
> 
> > From 25cd777ff3a2429cbb257e02603d6bef78d1564f Mon Sep 17 00:00:00
> > 2001 From: Dylan Jeffers 
> > Date: Thu, 11 Aug 2016 17:15:47 -0700
> > Subject: [PATCH] gnu: Add python-kivy.
> >
> > * gnu/packages/python.scm (python-kivy): New variable.
> > * gnu/packages/python.scm (python2-kivy: New variable.  
> 
> This should be:
> 
> * gnu/packages/python.scm (python-kivy, python2-kivy): New variables.
> 
> > ---
> >  gnu/packages/python.scm | 54
> > + 1 file changed,
> > 54 insertions(+)
> >
> > diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
> > index 6ff1c5c..9f14e80 100644
> > --- a/gnu/packages/python.scm
> > +++ b/gnu/packages/python.scm
> > @@ -24,6 +24,7 @@
> >  ;;; Copyright © 2016 Sou Bunnbu 
> >  ;;; Copyright © 2016 Troy Sankey 
> >  ;;; Copyright © 2016 ng0 
> > +;;; Copyright © 2016 Dylan Jeffers   
> 
> Your mail client failed to specify UTF-8 encoding for this attachment,
> so the copyright symbols above are coming through as pairs of raw
> octets.  We can fix this up manually if needed, but it would be great
> if you could fix your mail client configuration.
> 
> >  ;;;
> >  ;;; This file is part of GNU Guix.
> >  ;;;
> > @@ -88,6 +89,9 @@
> >#:use-module (gnu packages tcl)
> >#:use-module (gnu packages bdw-gc)
> >#:use-module (gnu packages pcre)
> > +  #:use-module (gnu packages gstreamer)
> > +  #:use-module (gnu packages sdl)
> > +  #:use-module (gnu packages gl)
> >#:use-module (guix packages)
> >#:use-module (guix download)
> >#:use-module (guix git-download)
> > @@ -9852,3 +9856,53 @@ etc.")
> >  (package
> >(inherit base)
> >(name "ptpython2"
> > +
> > +(define-public python-kivy
> > +  (let ((commit
> > + "a988c5e7a47da56263ff39514264a3de516ef2fe"))
> > +(package
> > +  (name "python-kivy")
> > +  (version "1.9.1")
> > +  (source
> > +   (origin
> > + (method git-fetch)
> > + (uri (git-reference
> > +   (url "https://github.com/kivy/kivy";)
> > +   (commit commit)))
> > + (file-name (string-append name "-" version "-dev.tar.gz"))
> > + (sha256
> > +  (base32
> > +
> > "0jk92b4a8l7blkvkgkjihk171s0dfnq582cckff5srwc8kal5m0p"  
> 
> This commit does not match the version string.  Version 1.9.1
> corresponds to commit 7e789b24cdb0ee044469d7bc42da9e4146674a18, from
> 1 January 2016, but the commit you've selected is much later, from
> 26 July 2016.
> 
> We generally prefer to use tarball releases, unless there is a
> compelling reason to use a non-release commit.
> 
> Is there a compelling reason?  If not, please use the 1.9.1 release
> tarball from ,
> along with the 'file-name' field.

Yes, the new dev version of kivy has a number of important enhancements
that are not available in 1.9.1.

> > +  (build-system python-build-system)
> > +  (arguments
> > +   `(#:tests? #f  ; Tests require many optional
> > packages
> > + #:phases
> > + (modify-phases %standard-phases
> > +   (replace 'build (lambda _ (zero? (system* "make"
> > "force"
> > +   (add-after 'patch-generated-file-shebangs 'set-sdl-paths
> > + (lambda* (#:key inputs #:allow-other-keys)
> > +   (setenv "KIVY_SDL2_PATH"
> > +   (string-append (assoc-ref inputs
> > "sdl-union")
> > +  "/include/SDL2"))
> > +   #t)
> > +  (native-inputs
> > +   `( ("pkg-config" ,pkg-config)))  
> 
> Please remove the space between the open parentheses above.
> 
> > +  (inputs
> > +   `(("python-cython" ,python-cython)
> > + ("gstreamer" ,gstreamer)
> > + ("mesa" ,mesa)
> > + ("sdl-union"
> > +  ,(sdl-union (list sdl2 sdl2-image sdl2-mixer
> > sdl2-ttf)
> > +  (home-page "http://kivy.org";)
> > +  (synopsis
> > +   "Multitouch application framework")
> > +  (description
> > +   "A software library for rapid development of
> > +hardware-accelerated multitouch applications.")
> > +  (license license:expat
> > +
> > +(define-public python2-kivy
> > +  (let ((base (package-with-python2 (strip-python2-variant
> > python-kivy
> > +(package
> > +  (inherit base)
> > +  (name "python2-kivy"  
> 
> Can you send an updated patch?
> 
>   Thanks,
> Mark

Updated python-kivy.patch

Best,
Dylan
From 67b0945f98836cfcac605c366f0ae8f8c8ccab56 Mon Sep 17 00:00:00 2001
From: Dylan Jeffers 
Date: Thu, 11 Aug 2016 17:15:47 -0700
Subject: [PATCH] gnu: Add python-kivy.

* gnu/packages/python.scm (python-kivy, python2-kivy): New variables.
---
 gnu/packages/python.scm | 54 +
 1 file changed, 54 insertions(+)

diff --git a/gnu

Re: [PATCH] gnu: Add python-stem.

[Leo Famulari]

On Fri, Aug 12, 2016 at 06:52:39PM +, ng0 wrote:
> > Setuptools was not used, so I removed it.
> 
> So python-setuptools is not needed all the when a setup.py is in place?

Sometimes it's needed, sometimes not. This time, I tried removing it,
and both python-stem and python2-stem still built.

> Do we already have a logo which is the size of all other systems listed
> on the download page of stem? I'd notify stem.torproject.org about the
> addition. I know we have svg graphics and some png graphics.
> For curl applies the same, I'd like to point them to a usable logo for a
> web site.

Take a look in the guix-artwork Git repo:

http://git.savannah.gnu.org/cgit/guix/guix-artwork.git

Re: [PATCH] gnu: Add p7zip.

[Kei Kebreau]

Ricardo Wurmus  writes:

> Kei Kebreau  writes:
>
>> Ricardo Wurmus  writes:
>>
>>> k...@openmailbox.org writes:
>>>
 On 2016-08-09 04:05, Ricardo Wurmus wrote:
> Leo Famulari  writes:
> 
>>> > I see that you took care of removing non-free parts in a patch and a
>>> > build phase.  Since “guix build -S p7zip” doesn’t run the build phase
>>> > users would still end up with a source archive containing the non-free
>>> > parts.  The best way is thus to remove things in a snippet.
>>> >
>>> > In “shogun” from the “machine-learning” module we remove supporting 
>>> > code
>>> > for non-free features in a snippet by cutting out anything between 
>>> > some
>>> > ifdef markers, but looking at the patch I see that it wouldn’t be
>>> > feasible for p7zip.
>>> 
>>> Also note that it is not completely desirable for nonfree code to be 
>>> removed
>>> with a patch, and is one of the reasons Guix supports snippets in the 
>>> first
>>> place.
>> 
>> Is there a reason to not use a patch in this case? Or can we proceed
>> with packaging p7zip, using a patch to remove non-free parts?
> 
> We don’t want to have a “reverse image” of the non-free code in a 
> patch.
> Arguably that would just be a derivative of the non-free code, so we
> also couldn’t freely distribute it.
> 
 If this is the case, then should we alert the Parabola GNU/Linux-libre 
 packagers?
 The patch I submitted is the same one they use when installing p7zip 
 from the
 source code (see 
 https://git.parabola.nu/abslibre.git/tree/libre/p7zip/libre.patch).
>>>
>>> I see.  I think we first need to figure out exactly what license applies
>>> to which part of the code.  A big chunk of the patch is to remove
>>> references to RAR stuff in the build system and the documentation; that
>>> could probably be removed with a patch.  What is critical is code that’s
>>> actually under the unRAR license.
>>>
>>> A quick look at the patch shows me this:
>>>
 -  Licenses for files are:
 -
 -1) CPP/7zip/Compress/Rar* files:  GNU LGPL + unRAR restriction
 -2) All other files:  GNU LGPL
>>>
>>> (https://git.parabola.nu/abslibre.git/tree/libre/p7zip/libre.patch#n540)
>>>
>>> This means that we need to delete all files in (1) — for everything else
>>> it’s just a matter of patching the files.  If I’m not mistaken this
>>> means that deleting the files in a snippet and applying this patch on
>>> top of it would be okay.
>>>
>>> What do others think?
>>>
>>> ~~ Ricardo
>>
>> Just to clarify, I'm interpreting what you are saying as:
>>
>> (1) Remove proprietary files in a snippet so "guix build -S p7zip" only
>> returns free source code, and
>>
>> (2) Apply the patch to get rid of the resultant unused code.
>>
>> If you mean those two things, then it sounds like a fine solution to
>> me. :-)
>
> Yes, that’s what I meant.  I hope I didn’t overlook anything here, so
> I’d be happy if someone else could check that this is fine.
>
> ~~ Ricardo

Here's the corresponding patch. Maybe you or someone else can double (or 
triple?)
check and make sure there are no proprietary files the source after running
"./pre-inst-env guix build -S p7zip."

From 10133e613714b3a59af18e5f579c596362b7ec9c Mon Sep 17 00:00:00 2001
From: Kei Kebreau 
Date: Fri, 12 Aug 2016 15:20:19 -0400
Subject: [PATCH] [PATCH] gnu: Add p7zip.

* gnu/packages/compression.scm (p7zip): New variable.
* gnu/packages/patches/remove-unused-p7zip-code.patch: New patch.
* gnu/local.mk (dist_patch_DATA): Add it.
---
 gnu/local.mk   |   1 +
 gnu/packages/compression.scm   |  69 ++
 .../patches/remove-unused-p7zip-code.patch | 959 +
 3 files changed, 1029 insertions(+)
 create mode 100644 gnu/packages/patches/remove-unused-p7zip-code.patch

diff --git a/gnu/local.mk b/gnu/local.mk
index 44ace61..62832c7 100644
--- a/gnu/local.mk
+++ b/gnu/local.mk
@@ -752,6 +752,7 @@ dist_patch_DATA =   
\
   %D%/packages/patches/rapicorn-isnan.patch\
   %D%/packages/patches/ratpoison-shell.patch   \
   %D%/packages/patches/readline-link-ncurses.patch \
+  %D%/packages/patches/remove-unused-p7zip-code.patch  \
   %D%/packages/patches/ripperx-missing-file.patch  \
   %D%/packages/patches/rpm-CVE-2014-8118.patch \
   %D%/packages/patches/rsem-makefile.patch \
diff --git a/gnu/packages/compression.scm b/gnu/packages/compression.scm
index e63c1af..b42996c 100644
--- a/gnu/packages/compression.scm
+++ b/gnu/packages/compression.scm
@@ -11,6 +11,7 @@
 ;;; Copyright © 2016 Ben Woodcroft 
 ;;; Copyright © 2016 Danny Milosavljevic 
 ;;; Copyright © 2016 Tobias Geerinckx-Rice 
+;;; Copyright © 2016 Kei Kebreau 
 ;;;
 ;;; This file is part of GNU Guix.
 ;;;
@@ -871,3 +872,71 

Re: [PATCH] gnu: Add proxychains-ng.

[ng0]

Leo Famulari  writes:

> On Fri, Aug 12, 2016 at 05:50:15PM +, ng0 wrote:
>> * gnu/packages/networking.scm (proxychains-ng): New variable.
>
>> +(arguments
>> + `(#:tests? #f
>> +   #:make-flags (list "CC=gcc")
>> +   #:phases
>> +   (modify-phases %standard-phases
>> + ;; Needs to be configured through the configure script.
>> + (replace 'configure
>> +   (lambda* (#:key outputs #:allow-other-keys)
>> + (let ((out (assoc-ref outputs "out")))
>> +   (zero? (system* "./configure"
>> +   (string-append "--prefix=" out)
>
> Does #:configure-flags not work in this case?

I have build it this way before, but it did not seem like it applied.

patch applied, maybe there was a mistake in this patch i had earlier:

>From 65184392aeef2582786192c2e7e3d8f2e704eb25 Mon Sep 17 00:00:00 2001
From: ng0 
Date: Fri, 12 Aug 2016 17:47:41 +
Subject: [PATCH] gnu: Add proxychains-ng.

* gnu/packages/networking.scm (proxychains-ng): New variable.
---
 gnu/packages/networking.scm | 25 +
 1 file changed, 25 insertions(+)

diff --git a/gnu/packages/networking.scm b/gnu/packages/networking.scm
index 77207c0..5177bdb 100644
--- a/gnu/packages/networking.scm
+++ b/gnu/packages/networking.scm
@@ -7,6 +7,7 @@
 ;;; Copyright © 2016 Tobias Geerinckx-Rice 
 ;;; Copyright © 2016 John Darrington 
 ;;; Copyright © 2016 Nicolas Goaziou 
+;;; Copyright © 2016 ng0 
 ;;;
 ;;; This file is part of GNU Guix.
 ;;;
@@ -635,3 +636,27 @@ information by IP Address.")
   (description "IO::Socket::INET6 is an interface for AF_INET/AF_INET6 domain
 sockets in Perl.")
   (license (package-license perl
+
+(define-public proxychains-ng
+  (package
+(name "proxychains-ng")
+(version "4.11")
+(source (origin
+  (method url-fetch)
+  (uri (string-append "https://github.com/rofl0r/"; name "/releases/"
+  "download/v" version "/" name "-" version
+  ".tar.bz2"))
+  (sha256
+   (base32
+"1dkncdzw852488gkh5zhn4b5i03qyj8rgh1wcvcva7yd12c19i6w"
+(build-system gnu-build-system)
+(arguments
+ `(#:tests? #f
+   #:make-flags (list "CC=gcc")
+   #:configure-flags (list (string-append "--prefix="
+  (assoc-ref %outputs "out")
+(synopsis "Force any tcp connections to flow through a proxy or proxy chain")
+(description "Preloader which hooks calls to sockets in dynamically linked programs
+and redirects them through one or more socks or http proxies.")
+(home-page "https://github.com/rofl0r/proxychains-ng";)
+(license license:gpl2)))
-- 
2.9.2


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

Re: [PACKAGE] musl libc

[Ricardo Wurmus]

David Craven  writes:

>> I just built musl and found that it also installs ?bin/musl-gcc?, a
>> wrapper of sorts, but it doesn?t work as it depends on a ?gcc?
>> executable to be available.
>
> With gcc 6 the wrapper isn't necessary anymore. You can disable it
> with "--disable-gcc-wrapper". Other configure-flags that we probably
> want are "--enable-shared" "--enable-static".

Thank you for the hint.  I’ll add “--disable-gcc-wrapper” and push to
master.  We can add other configure flags once it becomes apparent that
they are needed.

Thank you, Vincent, for the contribution!

~~ Ricardo

Re: [PATCH] gnu: Add python-stem.

[ng0]

Leo Famulari  writes:

> On Thu, Aug 11, 2016 at 04:26:03PM +, ng0 wrote:
>> From d6a5487d361eb667448871c42c96d9007a264214 Mon Sep 17 00:00:00 2001
>> From: ng0 
>> Date: Thu, 11 Aug 2016 13:42:22 +
>> Subject: [PATCH] gnu: Add python-stem.
>> 
>> * gnu/packages/python.scm (python-stem): New variable.
>> * gnu/packages/python.scm (python2-stem): New variable.
>
> Thank you for these patches!
>
> Setuptools was not used, so I removed it.

So python-setuptools is not needed all the when a setup.py is in place?

> I changed 'alist-replace' to 'modify-phases'.
>
> I added some dependencies that were missing. The tests passed without
> them, but they did print some warnings.
>
> I shortened the synopsis to satisfy `guix lint`.
>
> I also squashed the two patches into one. That is our convention when
> adding Python 2 and 3 versions of packages.

I see. Thank you, I wasn't sure about this.

> I pushed the result as b227f0be89.

Thanks!


Do we already have a logo which is the size of all other systems listed
on the download page of stem? I'd notify stem.torproject.org about the
addition. I know we have svg graphics and some png graphics.
For curl applies the same, I'd like to point them to a usable logo for a
web site.
-- 
♥Ⓐ  ng0
For non-prism friendly talk find me on http://www.psyced.org

Re: [PATCH] gnu: cross-libc: Use the correct libc.

[Leo Famulari]

On Thu, Aug 11, 2016 at 09:56:27PM +0300, Manolis Ragkousis wrote:
> Hello everyone,
> 
> I noticed that in commit ef21276053b980 from core-updates-next I am
> using (cross-libc-for-target ...) only in one place while I should have
> used (let ((libc (cross-libc-for-target target))) (package ...

Can you try applying it on top of WIP-core-updates [0]?

And perhaps reviewing the new branch as requested in [0], while you're
at it?

[0]
http://lists.gnu.org/archive/html/guix-devel/2016-08/msg00731.html

Re: [PATCH] gnu: cross-libc: Use the correct libc.

[Manolis Ragkousis]

Hey Leo,

On 08/12/16 21:40, Leo Famulari wrote:
> Can you try applying it on top of WIP-core-updates [0]?
> 
> And perhaps reviewing the new branch as requested in [0], while you're
> at it?
> 
> [0]
> http://lists.gnu.org/archive/html/guix-devel/2016-08/msg00731.html
> 

The patch applied cleanly to WIP-core-updates and I am currently
checking the new branch.

Manolis

Re: [PATCH] gnu: Add Aircrack-ng.

[Eric Bavier]

On 2016-08-12 13:01, Leo Famulari wrote:
On Thu, Aug 11, 2016 at 07:58:17AM -0500, ericbav...@openmailbox.org 
wrote:

* gnu/packages/networking.scm (aircrack-ng): New variable.



+(inputs
+ `(("libgcrypt" ,libgcrypt)
+   ("libnl" ,libnl)
+   ("ethtool" ,ethtool)
+   ("pcre" ,pcre)
+   ("sqlite" ,sqlite)
+   ("zlib" ,zlib)))


The output does not refer to ethtool:
$ guix gc --references $(./pre-inst-env guix build aircrack-ng)
/gnu/store/5992iq1v7arqa14ym3di58n4la0893nv-zlib-1.2.8
/gnu/store/9nifwk709wajpyfwa0jzaa3p6mf10vxs-gcc-4.9.3-lib
/gnu/store/m9vxvhdj691bq1f85lpflvnhcvrdilih-glibc-2.23
/gnu/store/mpm281yzwcxzfc9n86krr61yhs2ja6gd-libgcrypt-1.7.0
/gnu/store/xiskld167yl4nqy57glqmcl3yp3bknh0-sqlite-3.12.2
/gnu/store/ykzwykkvr2c80rw4l1qh3mvfdkl7jibi-bash-4.3.42
/gnu/store/yydfpvk513c16ixgq8kdvi3g4l6clw2w-libnl-3.2.25
/gnu/store/zwc6ck9j0wv80kz5snw5acwb39ws88m1-pcre-8.38

Do you think that's a problem?


I realize now after testing the tools some more that ethtool is a 
runtime script dependency that gets called as just "ethtool".  I think 
I'll try to track down the reference and substitute the absolute file 
name.





+(arguments
+ `(#:make-flags `("sqlite=true"
+  "gcrypt=true"
+  "libnl=true"
+  "pcre=true"
+  "experimental=true"


I think this flag deserves an explanatory comment.


Sure.  The "experimental" flag builds a few extra tools like 
"wesside-ng" and "easside-ng".


Thanks for checking it out!

`~Eric

Re: [PATCH 2/5] gnu: Add libosinfo.

[Ricardo Wurmus]

Leo Famulari  writes:

> On Wed, Aug 03, 2016 at 05:46:00PM +0200, Ricardo Wurmus wrote:
>> * gnu/packages/qemu.scm (libosinfo): New variable.
>
>> +   ("usb.ids"
>> +,(origin
>> +   (method url-fetch)
>> +   ;; FIXME: there is no versioned URL
>> +   (uri "http://www.linux-usb.org/usb.ids";)
>
> Is it worth sending them a message asking for a version URL?

They already replied to my message and I updated the patch to use the
versioned URL.  I’ll push the patches in a moment.

~~ Ricardo

Re: [PATCH] gnu: Add proxychains-ng.

[Leo Famulari]

On Fri, Aug 12, 2016 at 05:50:15PM +, ng0 wrote:
> * gnu/packages/networking.scm (proxychains-ng): New variable.

> +(arguments
> + `(#:tests? #f
> +   #:make-flags (list "CC=gcc")
> +   #:phases
> +   (modify-phases %standard-phases
> + ;; Needs to be configured through the configure script.
> + (replace 'configure
> +   (lambda* (#:key outputs #:allow-other-keys)
> + (let ((out (assoc-ref outputs "out")))
> +   (zero? (system* "./configure"
> +   (string-append "--prefix=" out)

Does #:configure-flags not work in this case?

Re: [PATCH] gnu: Add stagit.

[Leo Famulari]

On Wed, Aug 10, 2016 at 10:18:31AM +, ng0 wrote:
> * gnu/packages/version-control.scm (stagit): New variable.

Thank you for this!

I added some more licensing information, and cleaned up the synopsis and
description a little bit.

Pushed as b3885778.


signature.asc
Description: PGP signature

Re: [PATCH] gnu: Add Aircrack-ng.

[Leo Famulari]

On Thu, Aug 11, 2016 at 07:58:17AM -0500, ericbav...@openmailbox.org wrote:
> * gnu/packages/networking.scm (aircrack-ng): New variable.

> +(inputs
> + `(("libgcrypt" ,libgcrypt)
> +   ("libnl" ,libnl)
> +   ("ethtool" ,ethtool)
> +   ("pcre" ,pcre)
> +   ("sqlite" ,sqlite)
> +   ("zlib" ,zlib)))

The output does not refer to ethtool:
$ guix gc --references $(./pre-inst-env guix build aircrack-ng)
/gnu/store/5992iq1v7arqa14ym3di58n4la0893nv-zlib-1.2.8
/gnu/store/9nifwk709wajpyfwa0jzaa3p6mf10vxs-gcc-4.9.3-lib
/gnu/store/m9vxvhdj691bq1f85lpflvnhcvrdilih-glibc-2.23
/gnu/store/mpm281yzwcxzfc9n86krr61yhs2ja6gd-libgcrypt-1.7.0
/gnu/store/xiskld167yl4nqy57glqmcl3yp3bknh0-sqlite-3.12.2
/gnu/store/ykzwykkvr2c80rw4l1qh3mvfdkl7jibi-bash-4.3.42
/gnu/store/yydfpvk513c16ixgq8kdvi3g4l6clw2w-libnl-3.2.25
/gnu/store/zwc6ck9j0wv80kz5snw5acwb39ws88m1-pcre-8.38

Do you think that's a problem?

> +(arguments
> + `(#:make-flags `("sqlite=true"
> +  "gcrypt=true"
> +  "libnl=true"
> +  "pcre=true"
> +  "experimental=true"

I think this flag deserves an explanatory comment.

Re: [PATCH] gnu: Add python-stem.

[Leo Famulari]

On Thu, Aug 11, 2016 at 04:26:03PM +, ng0 wrote:
> From d6a5487d361eb667448871c42c96d9007a264214 Mon Sep 17 00:00:00 2001
> From: ng0 
> Date: Thu, 11 Aug 2016 13:42:22 +
> Subject: [PATCH] gnu: Add python-stem.
> 
> * gnu/packages/python.scm (python-stem): New variable.
> * gnu/packages/python.scm (python2-stem): New variable.

Thank you for these patches!

Setuptools was not used, so I removed it.

I changed 'alist-replace' to 'modify-phases'.

I added some dependencies that were missing. The tests passed without
them, but they did print some warnings.

I shortened the synopsis to satisfy `guix lint`.

I also squashed the two patches into one. That is our convention when
adding Python 2 and 3 versions of packages.

I pushed the result as b227f0be89.

[PATCH] gnu: Add proxychains-ng.

[ng0]

>From 895ddace3e0645683adb07a05406419b58e42b01 Mon Sep 17 00:00:00 2001
From: ng0 
Date: Fri, 12 Aug 2016 17:47:41 +
Subject: [PATCH] gnu: Add proxychains-ng.

* gnu/packages/networking.scm (proxychains-ng): New variable.
---
 gnu/packages/networking.scm | 31 +++
 1 file changed, 31 insertions(+)

diff --git a/gnu/packages/networking.scm b/gnu/packages/networking.scm
index 77207c0..78790f4 100644
--- a/gnu/packages/networking.scm
+++ b/gnu/packages/networking.scm
@@ -7,6 +7,7 @@
 ;;; Copyright © 2016 Tobias Geerinckx-Rice 
 ;;; Copyright © 2016 John Darrington 
 ;;; Copyright © 2016 Nicolas Goaziou 
+;;; Copyright © 2016 ng0 
 ;;;
 ;;; This file is part of GNU Guix.
 ;;;
@@ -635,3 +636,33 @@ information by IP Address.")
   (description "IO::Socket::INET6 is an interface for AF_INET/AF_INET6 domain
 sockets in Perl.")
   (license (package-license perl
+
+(define-public proxychains-ng
+  (package
+(name "proxychains-ng")
+(version "4.11")
+(source (origin
+  (method url-fetch)
+  (uri (string-append "https://github.com/rofl0r/"; name "/releases/"
+  "download/v" version "/" name "-" version
+  ".tar.bz2"))
+  (sha256
+   (base32
+"1dkncdzw852488gkh5zhn4b5i03qyj8rgh1wcvcva7yd12c19i6w"
+(build-system gnu-build-system)
+(arguments
+ `(#:tests? #f
+   #:make-flags (list "CC=gcc")
+   #:phases
+   (modify-phases %standard-phases
+ ;; Needs to be configured through the configure script.
+ (replace 'configure
+   (lambda* (#:key outputs #:allow-other-keys)
+ (let ((out (assoc-ref outputs "out")))
+   (zero? (system* "./configure"
+   (string-append "--prefix=" out)
+(synopsis "Force any tcp connections to flow through a proxy or proxy chain")
+(description "Preloader which hooks calls to sockets in dynamically linked programs
+and redirects them through one or more socks or http proxies.")
+(home-page "https://github.com/rofl0r/proxychains-ng";)
+(license license:gpl2)))
-- 
2.9.2


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

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

[Leo Famulari]

On Tue, Aug 09, 2016 at 03:13:31PM +0200, Jelle Licht wrote:
> Attached you will find the updated version of this patch. Please let me
> know what you think.

> From 798d0888cc57a18ab31fa546a94932476e39088e Mon Sep 17 00:00:00 2001
> From: Jelle Licht 
> Date: Fri, 5 Aug 2016 12:51:15 +0200
> Subject: [PATCH] gnu: node: Update to 6.3.1.
> To: guix-devel@gnu.org
> 
> Remove  and
>  workaround.
> 
> * gnu/packages/node.scm (node): Update to 6.3.1.
>   (node)[arguments]: Disabled more tests. Remove custom 'patch-shebangs'
>   phase. Manually patch npm script shebang in new 'patch-npm-shebang'
>   phase.
> ---
>  gnu/packages/node.scm | 32 ++--
>  1 file changed, 14 insertions(+), 18 deletions(-)

I applied this patch on top of commit 939111ca9. Unfortunately, node
fails its test suite on my x86_64 machine. Can you look into it?

starting phase `check'
make -C out BUILDTYPE=Release V=1
make[1]: Entering directory '/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/out'
  touch 
_tmp_guix_build_node_6_3_1_drv_0_node_v6_3_1_deps_v8_inspector_platform_v8_inspector_v8_inspector_gyp_protocol_sources_target_generateV8InspectorProtocolBackendSources.intermediate
  
LD_LIBRARY_PATH=/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/out/Release/lib.host:/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/out/Release/lib.target:$LD_LIBRARY_PATH;
 export LD_LIBRARY_PATH; cd ../deps/v8_inspector/platform/v8_inspector; mkdir 
-p 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/out/Release/obj/gen/blink/platform/v8_inspector/protocol;
 python ../inspector_protocol/CodeGenerator.py --protocol js_protocol.json 
--string_type String16 --export_macro PLATFORM_EXPORT --output_dir 
"/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/out/Release/obj/gen/blink/platform/v8_inspector/protocol"
 --output_package platform/v8_inspector/protocol
rm 
_tmp_guix_build_node_6_3_1_drv_0_node_v6_3_1_deps_v8_inspector_platform_v8_inspector_v8_inspector_gyp_protocol_sources_target_generateV8InspectorProtocolBackendSources.intermediate
make[1]: Leaving directory '/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/out'
ln -fs out/Release/node node
make build-addons
make[1]: Entering directory '/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1'
make -C out BUILDTYPE=Release V=1
rm -f -r test/addons/??_*/
./node tools/doc/addon-verify.js
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/01_callbacks/addon.cc
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/01_callbacks/test.js
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/01_callbacks/binding.gyp
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/02_object_factory/addon.cc
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/02_object_factory/test.js
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/02_object_factory/binding.gyp
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/03_function_factory/addon.cc
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/03_function_factory/test.js
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/03_function_factory/binding.gyp
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/04_wrapping_c_objects/addon.cc
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/04_wrapping_c_objects/test.js
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/04_wrapping_c_objects/binding.gyp
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/05_factory_of_wrapped_objects/addon.cc
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/05_factory_of_wrapped_objects/myobject.h
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/05_factory_of_wrapped_objects/myobject.cc
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/05_factory_of_wrapped_objects/test.js
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/05_factory_of_wrapped_objects/binding.gyp
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/06_passing_wrapped_objects_around/addon.cc
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/06_passing_wrapped_objects_around/myobject.h
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/06_passing_wrapped_objects_around/binding.gyp
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/07_atexit_hooks/addon.cc
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/07_atexit_hooks/myobject.h
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/07_atexit_hooks/myobject.cc
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/07_atexit_hooks/test.js
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/07_atexit_hooks/binding.gyp
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/06_passing_wrapped_objects_around/myobject.cc
wrote 
/tmp/guix-build-node-6.3.1.drv-0/node-v6.3.1/test/addons/06_passing_wrapped_objects_around/t

Re: JIT compiling

[Oliver Heimlich]

On 12.08.2016 17:08, Sergei Steshenko wrote:
>> 
>> From: Jordi Gutiérrez Hermoso 
>> To: Alex Vong  
>> Cc: Ricardo Wurmus ; guix-devel@gnu.org; Leo Famulari 
>> ; help-oct...@gnu.org; Mike Miller 
>> Sent: Friday, August 12, 2016 2:45 PM
>> Subject: JIT compiling
>>
>>
>> On Thu, 2016-08-11 at 23:27 +0800, Alex Vong wrote:
>>> Finally, some unrelated stuff, I hope octave would have a byte code
>>> interpreter soon. I would suggest to write it in rpython, it seems
>>> to be the easiest way to have jit these days.
>>
>> That is a faraway pipe dream. Can you help?
>>
>> - Jordi G. H.
>>
>>
> 
> 
> Julia ( http://julialang.org/ ) quite developed since it's been discussed 
> here. They claim to have close to "C" performance and JIT.
> 

There is a good language introduction available as a talk from JuliaCon:
https://youtu.be/rAxzR7lMGDM

As far as I can see, Julia compiles the code if it can predict the types
of the variables. Otherwise, it is slow. This is explained in the first
part of the talk.

Best
Oliver

Re: [PATCH 05/26] gnu: kde-frameworks: Add bluez-qt.

[David Craven]

> I'll use 'BlueZ', the description of bluez uses it.

Does this mean you are applying the patch or that you want me to resubmit?

Re: Trying to fix IBus

[Chris Marusich]

Ricardo Wurmus  writes:

> Ricardo Wurmus  writes:
>
>> Chris Marusich  writes:
>>
>>> One last thing: it seems that the NixOS devs' choice of solution was
>>> influenced by a desire not to require users to rebuild programs that
>>> were previously installed in their profiles [1].  They almost chose a
>>> solution like the one you are proposing, but they changed their minds to
>>> avoid requiring users to rebuild existing programs in their profiles.
>>> GuixSD is still Beta, so I don't think that's an issue for us at all.
>>>
>>> [1] See abbradar's comment on April 8th, 2016:
>>>
>>> https://github.com/NixOS/nixpkgs/pull/14417#issuecomment-207362530
>>>
>>> "This patch would break all such software that uses old (unpatched)
>>> GTK+3."
>>>
>>> This appears to be the primary reason why they chose to patch GTK+2 and
>>> GTK+3 to search NIX_PROFILES for an immodules.cache file instead of
>>> patching it to use separate environment variables for GTK+2 and GTK+3.
>>
>> Right, I saw that too, but I really don’t think it applies to us.  I’m
>> not familiar with the state of IBus in NixOS before the change to
>> NIX_PROFILES, but I don’t see how this would break existing software.
>>
>> The reason for crashes is that GTK2 software is made to load GTK3 input
>> method modules (and vice versa).  We don’t set any variables right now
>> that could have this effect.  When adding the “GUIX_GTK{2,3}_*”
>> variables, software built with the unpatched GTK would just ignore input
>> methods.
>>
>> If I understand correctly, NixOS installs (or used to install) IBus
>> system-wide and has system-wide caches (at /etc/…/immodules.cache).  Our
>> caches would exist on a per-profile base.
>>
>> If you are more familiar with this problem in NixOS and you think I’m
>> overlooking something I’d be happy if you could show me what I’m
>> missing, but I really think that we wouldn’t be bitten by a problem like
>> this.  In our case software using the pre-patch GTK versions would
>> behave just like they do now: simply without IBus support.

I might be mistaken, but the patch which the NixOS devs originally
considered in pull request 14417 removed code that appears to
automatically overwrite $out/lib/gtk-3.0/3.0.0/immodules.cache in the
store every time someone installs something that depends on GTK+3:

https://github.com/NixOS/nixpkgs/pull/14417/files#diff-9be1673bb42206c648aec0c894c231deL54

It's possible that is the reason why astsmtl observed that pasystray
worked before the patch, but not after.  I'm not exactly sure.

In any case, I agree we probably don't have to worry about it.

> One more thing: we could also preempt the decision of GTK upstream and
> hardcode IBus as the only possible input method system (as has been
> suggested on the NixOS discussion), but I think that we should rather
> avoid patching things more than absolutely necessary.
>
> (Some people prefer fcitx over IBus; I don’t want to force them to
> migrate to IBus when there’s a simple alternative.)

I agree.

-- 
Chris


signature.asc
Description: PGP signature

Re: [PATCH] ui: 'package->recutils' serializes the source field.

[Ricardo Wurmus]

Alex Kost  writes:

> Yes, I agree that it's a good demonstration of using Scheme API to get
> any package info you need.  But many (probably most) people do not know
> Guile and this Guix package API well enough, and for them it may be much
> easier to operate on the recutils output of "guix package --show" in
> their scripts.  If I understand correctly, that's why David suggested
> that patch.

Yes, the recutils output could be used in scripts.  My recommendation
when dealing with source tarballs, however, is to call “guix build -S”
on the package name that recutils provides — this gives the user the
actual corresponding source.  This seems to be sufficient for shell
scripting purposes.

~~ Ricardo

Re: [PATCH] ui: 'package->recutils' serializes the source field.

[Alex Kost]

David Craven (2016-08-11 19:19 +0300) wrote:

> How invested are you in this patch? I decided that I wasn't that
> invested and it isn't worth the trouble. Some things are not meant to
> be.

Invested?  Sorry, I don't understand.  Do you mean how much I need this
patch?  Well, I don't need it at all, since I never use "guix package
--show".  I just don't see a problem in accepting this patch as I don't
understand Mathieu's and Mark's concerns about FSDG compliance, but I'm
not competent in this area, so I let other people judge.

-- 
Alex

Re: [PATCH] gnu: Add stagit.

[ng0]

ng0  writes:

> [ Unknown signature status ]
> Same as sic, I am not sure if the description could be extended. This is
> what I could come up with.
>
> If you have trouble testing it, consider this commit which is not in 0.4
> release:
> http://git.2f30.org/stagit/commit/44a49f51db565cbfc31f31393d8dcdec1cdc8167.html

Should this go into gnu/packages/suckless.scm then? Seems more
appropriate after the last comments on suckless.scm.

> From d2a2dd0b6f831f8a1ecc09794c44d6ea2b3992b5 Mon Sep 17 00:00:00 2001
> From: ng0 
> Date: Wed, 10 Aug 2016 10:04:29 +
> Subject: [PATCH] gnu: Add stagit.
>
> * gnu/packages/version-control.scm (stagit): New variable.
> ---
>  gnu/packages/version-control.scm | 30 +-
>  1 file changed, 29 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/packages/version-control.scm 
> b/gnu/packages/version-control.scm
> index 767715d..b12c53a 100644
> --- a/gnu/packages/version-control.scm
> +++ b/gnu/packages/version-control.scm
> @@ -9,6 +9,7 @@
>  ;;; Copyright © 2015, 2016 Efraim Flashner 
>  ;;; Copyright © 2015 Kyle Meyer 
>  ;;; Copyright © 2015 Ricardo Wurmus 
> +;;; Coypright © 2016 ng0 
>  ;;;
>  ;;; This file is part of GNU Guix.
>  ;;;
> @@ -29,7 +30,7 @@
>#:use-module ((guix licenses)
>  #:select (asl2.0 bsd-2 bsd-3
>gpl1+ gpl2 gpl2+ gpl3+ lgpl2.1
> -  public-domain x11-style))
> +  public-domain x11-style expat))
>#:use-module (guix utils)
>#:use-module (guix packages)
>#:use-module (guix download)
> @@ -1250,3 +1251,30 @@ access and administration over HTTP CGI or via a 
> built-in HTTP server.  It has
>  a built-in wiki, built-in file browsing, built-in tickets system, etc.")
>  (license (list public-domain;src/miniz.c, src/shell.c
> bsd-2
> +
> +(define-public stagit
> +  (package
> +(name "stagit")
> +(version "0.4")
> +(source (origin
> +  (method url-fetch)
> +  (uri (string-append "http://dl.2f30.org/releases/";
> +  name "-" version ".tar.gz"))
> +  (sha256
> +   (base32
> +"0z5r06wqrfnsz24ci4hjqbd62svclvhkgzaq9npsyjcp6jnf7izc"
> +(build-system gnu-build-system)
> +(arguments
> + `(#:tests? #f ; no tests
> +   #:make-flags (list "CC=gcc"
> +  (string-append "PREFIX=" %output))
> +   #:phases
> +   (modify-phases %standard-phases
> + (delete 'configure ; no configure
> +(inputs
> + `(("libgit2" ,libgit2)))
> +(home-page "http://2f30.org";)
> +(synopsis "Static git page generator")
> +(description "Stagit creates static pages for git repositories, the 
> results can
> +be served with a HTTP file server.")
> +(license expat)))
> -- 
> 2.9.2
>
>
> -- 
> ♥Ⓐ  ng0
> Current Keys: https://we.make.ritual.n0.is/ng0.txt
> For non-prism friendly talk find me on http://www.psyced.org

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

Re: [PATCH] ui: 'package->recutils' serializes the source field.

[David Craven]

> Invested?  Sorry, I don't understand.

One definition of invest is:
devote (one's time, effort, or energy) to a particular undertaking
with the expectation of a worthwhile result.

I just thought that you had invested some time and energy with this
issue, and don't know what your expectation of a worthwhile result is.
The question was mainly intended to say - I can't be bothered to start
a discussion on a different mailing list, but I'll offer my support if
you think it's worthwhile...

Re: [PATCH] (3 patches): move dwm+dmenu to wm, move slock to xdisorg.

[ng0]

This comment updates the state of the patches I now no longer track:

Web view of guix-devel at gnu.org server is currently unreachable.
With two voices against/concerned about the suckless move, these patches
need no longer to be applied.
-- 
♥Ⓐ  ng0
For non-prism friendly talk find me on http://www.psyced.org

Re: [PATCH] gnu: st: Mov to terminals.scm.

[ng0]

Hi,

Mark H Weaver  writes:

> Mathieu Lirzin  writes:
>
>> iyzs...@member.fsf.org (宋文武) writes:
>>
>>> ng0  writes:
>>>
 Hi,

 I think it's pointless to have a suckless.scm which bundles all software
 which just happens to follow suckless ideology/goals or be hosted
 there.
 That's why I did not commit ii to suckless but to irc.scm, no one will
 look into suckless.scm when what they really are looking for is not
 $suckless but application xy.
 I try to unbundle and remove suckless.scm with the next patches.
>>>
>>> Well, it's difficult to choose the "right" category for packages.
>>> For example, 'dmenu' shouldn't go to 'wm.scm', it has nothing to
>>> do with window managers.
>>>
>>> When a project makes multiple softwares, I think it's easier to
>>> put all of them in one project file, eg: gnome and freedesktop.
>>
>> So you are in favour of keeping (gnu packages suckless)?
>
> Fwiw, I'm in favor of keeping suckless.scm, and rejecting these proposed
> package moves.
>
>  Mark
>

Thanks for the comments, I did not see your replies until today.

Okay, I'd say with your replied that we do not move it.
The latest update of st I did in suckless.scm, so anyone who wants to
update that can aply the patch.

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

Re: node FTBFS

[Alex Vong]

Jelle Licht  writes:

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

> Thanks,
> Jelle
>
> [0]:
> https://lists.gnu.org/archive/html/guix-devel/2016-08/msg00351.html
>
> 2016-08-11 14:15 GMT+02:00 Alex Vong :
>
> Just to be complete, this is the error obtained when building on
> local
> machine:
> 
> 
> === release test-tls-alpn-server-client ===
> Path: parallel/test-tls-alpn-server-client
> assert.js:90
> throw new assert.AssertionError({
> ^
> AssertionError: 'first-priority-unsupported' === false
> at checkResults
> 
> (/tmp/guix-build-node-6.0.0.drv-0/node-v6.0.0/test/parallel/test-tls-alpn-server-
>client.js:32:10)
> at
> 
> /tmp/guix-build-node-6.0.0.drv-0/node-v6.0.0/test/parallel/test-tls-alpn-server-
>client.js:101:5
> at TLSSocket.
> 
> (/tmp/guix-build-node-6.0.0.drv-0/node-v6.0.0/test/parallel/test-tls-alpn-server-
>client.js:66:9)
> at TLSSocket.g (events.js:286:16)
> at emitNone (events.js:86:13)
> at TLSSocket.emit (events.js:185:7)
> at TLSSocket. (_tls_wrap.js:1072:16)
> at emitNone (events.js:86:13)
> at TLSSocket.emit (events.js:185:7)
> at TLSSocket._finishInit (_tls_wrap.js:580:8)
> Command: out/Release/node
> 
> /tmp/guix-build-node-6.0.0.drv-0/node-v6.0.0/test/parallel/test-tls-alpn-server-
>client.js
> 
> 
> 
> 
> Alex Vong  writes:
> 
> > Hi guixers,
> >
> > Node now fails 1 test more, in addition to some of the already
> disabled
> > tests. Perhaps someone interested can have a look. Node fails to
> build
> > in hydra since 2/8.
> >
> > Thanks,
> > Alex
> 
> 

Re: [PATCH] st: Update to 0.7.

[宋文武]

ng0  writes:

> ng0  writes:
>
>> This patch updates st, still in the suckless.scm.
>>
>> I can adjust whatever patchset gets applied first.
>
> Correction: I sent this patch before the email on the release got out,
> release email says the dependency on libxext got dropped.
>

Applied, thanks!

Re: [PATCH] gnu: add xlsx2csv.

[Catonano]

2016-08-12 14:42 GMT+02:00 Ben Woodcroft :

> Hi,
>
> On 11/08/16 23:02, Catonano wrote:
>
>
>
> 2016-08-11 14:11 GMT+02:00 Jan Nieuwenhuizen :
>
>> Ben Woodcroft writes:
>>
>> [..]
>
>
>> > However, I note that while the check phase passes, many of the tests
>> > are reported as being failed. Could you look into it?
>>
> That's trying to run them with non-installed python versions.  Patched
> the test script to only use `python.'
>
>
> Ah, I see. Better.
>
> [..]
>
> >> +(synopsis "xlsx to csv converter")
>> >> +(description
>> >> + "Xls2csv converts xslx files to csv format.  Handles large
>> >> xlsx-files.")
>>
>> > How about "Xlsx2csv is a program to convert Open Office XML (XLSX)
>> > format spreadsheets into plaintext @dfn{comma separated values} (CSV)
>> > files.  It was designed to be fast and to handle large input files."
>>
>> Better, thanks.
>>
>
> for what it matters, I would leave the original wording in place.
>
> It's important that people know that this packages deals also with
> Microsoft Excel files.
>
> There are tons of such files around and people struggle with them
>
> It happened to me recently. I had to convert a bunch of those files and
> the tools I found were not adequate.
>
> I did it by hand and then discovered xlsx2csv
>
> If someone (especially from the data journalism or open data camps)
> casually browses the Guix packages list, I think it's important that it's
> clear that this package deals with xlsx files
>
> The OpenOffce name could be misleading to not too tech oriented people.
>
> I understand there's the problem of not steering people to non free
> software. But this package is supposed to help people trying to bring data
> outside of that realm.
>
> They don't need not be steered to Excel, they are already trying to get
> away, if they come to this package.
>
>
> OK, I see your point, and we have other packages that mention Excel
> already. It is frustrating that the official name is misleading.
>

Eh. People identify software projects/products with file formats.


> Would either of you like to suggest an alternative wording?
>
> Thanks,
> ben
>

I would say

> "Xlsx2csv is a program to convert xlsx
> format files into plaintext @dfn{comma separated values} (CSV)
> files.  It was designed to be fast and to handle large files."

In this way they could search on tne internet the meaning of xlsx and csv
and know exactly what ths package is about.

Even the original wording proposed by Jan isn't bad, in my opinion. But
admittedly I didn't check whether it conforms to synopses guidelines.

JIT compiling

[Jordi Gutiérrez Hermoso]

On Thu, 2016-08-11 at 23:27 +0800, Alex Vong wrote:
> Finally, some unrelated stuff, I hope octave would have a byte code
> interpreter soon. I would suggest to write it in rpython, it seems
> to be the easiest way to have jit these days.

That is a faraway pipe dream. Can you help?

- Jordi G. H.

Re: [PATCH] gnu: add xlsx2csv.

[Ben Woodcroft]

Hi,


On 11/08/16 23:02, Catonano wrote:



2016-08-11 14:11 GMT+02:00 Jan Nieuwenhuizen >:


Ben Woodcroft writes:


[..]



> However, I note that while the check phase passes, many of the tests
> are reported as being failed. Could you look into it?

That's trying to run them with non-installed python versions.  Patched
the test script to only use `python.'


Ah, I see. Better.

[..]


>> +(synopsis "xlsx to csv converter")
>> +(description
>> + "Xls2csv converts xslx files to csv format.  Handles large
>> xlsx-files.")

> How about "Xlsx2csv is a program to convert Open Office XML (XLSX)
> format spreadsheets into plaintext @dfn{comma separated values}
(CSV)
> files.  It was designed to be fast and to handle large input files."

Better, thanks.


for what it matters, I would leave the original wording in place.

It's important that people know that this packages deals also with 
Microsoft Excel files.


There are tons of such files around and people struggle with them

It happened to me recently. I had to convert a bunch of those files 
and the tools I found were not adequate.


I did it by hand and then discovered xlsx2csv

If someone (especially from the data journalism or open data camps) 
casually browses the Guix packages list, I think it's important that 
it's clear that this package deals with xlsx files


The OpenOffce name could be misleading to not too tech oriented people.

I understand there's the problem of not steering people to non free 
software. But this package is supposed to help people trying to bring 
data outside of that realm.


They don't need not be steered to Excel, they are already trying to 
get away, if they come to this package.


OK, I see your point, and we have other packages that mention Excel 
already. It is frustrating that the official name is misleading. Would 
either of you like to suggest an alternative wording?


Thanks,
ben

Re: [PATCH] ui: 'package->recutils' serializes the source field.

[Alex Kost]

Ricardo Wurmus (2016-08-11 19:42 +0300) wrote:

> Alex Kost  writes:
>
>> David Craven (2016-08-10 17:13 +0300) wrote:
>>
 Even so, if one insisted on using the recutils output in a programmatic
 fashion (e.g. in a bash script), it would be best to run “guix build
 --source” on the package names to obtain the actual source tarballs that
 are used by Guix.
>>>
>>> I don't disagree. Alex what do you think?
>>
>> Do you mean about your original proposal?  I am for it: I don't
>> comprehend why the source URL can't be displayed (especially since a
>> user can easily find it anyway), but I don't understand FSDG well enough
>> to judge, so I prefer not to participate in this discussion.
>
> I have previously stated that I’m not convinced that we really need a
> serialisation of the “source” field in the user-facing recutils output.
> The patch was a welcome demonstration of how this feature would look
> like.

Yes, I agree that it's a good demonstration of using Scheme API to get
any package info you need.  But many (probably most) people do not know
Guile and this Guix package API well enough, and for them it may be much
easier to operate on the recutils output of "guix package --show" in
their scripts.  If I understand correctly, that's why David suggested
that patch.

P.S.  I don't want to raise another wave of messages in this thread :-)
If I understand it right, everyone agreed on not merging the patch.

-- 
Alex