* [PATCH 0/3] Fix letsencrypt
@ 2016-03-23 1:46 Leo Famulari
2016-03-23 1:46 ` [PATCH 1/3] gnu: python-pytest: Update to 2.7.3 Leo Famulari
` (5 more replies)
0 siblings, 6 replies; 19+ messages in thread
From: Leo Famulari @ 2016-03-23 1:46 UTC (permalink / raw)
To: guix-devel
Earlier today I found that I could not build letsencrypt.
The recent update to python-hypothesis broke python-pyopenssl, which
blocked the build of letsencrypt.
This patch series seems to be the minimum required to get letsencrypt
building again. I built letsencrypt on these patches and used it to
issue certificates for a new server.
The update to python-pytest and python2-pytest will require ~200
rebuilds [0].
This does not update python-pytest to the latest version, 2.9.1. I could
not get that to work, and I suspect it will require updates to some core
Python packages such as python-setuptools.
In the meantime, I'd like to do this intermediate update to get
letsencrypt building again. Any objections? If it's okay, should it go
on master, or onto a staging branch?
[0] I have re-wrapped this for readability:
$ guix refresh -l python2-pytest python-pytest
Building the following 66 packages would ensure 194 dependent packages
are rebuilt: python2-pickleshare-0.5 python2-scikit-image-0.11.3
python2-statsmodels-0.6.1 python2-seaborn-0.5.1 python2-numexpr-2.4.4
enblend-enfuse-4.1.3 libreoffice-5.0.5.2 seqmagick-0.6.1 pepr-1.0.9
grit-2.0.2 pbtranscript-tofu-2.2.3.8f5467fe6 macs-2.1.0.20151222
crossmap-0.2.1 rseqc-2.6.1 pyicoteo-2.0.7 python2-warpedlmm-0.21
clipper-0.3.0 deeptools-2.1.1 miso-0.5.3 couger-1.8.2 gourmet-0.17.4
python2-rq-0.5.2 python2-urllib3-1.13.1 python2-ndg-httpsclient-0.4.0
gajim-0.16.5 python2-docopt-0.6.2 python2-pytest-subtesthack-0.1.1
python2-alembic-0.8.4 letsencrypt-0.4.2 python2-rauth-0.7.2
python2-ipython-3.2.1
simp-le-2015-12-07T040251Z-01afa8c64264a7674e51471ea4bf7ce524d8b77e
python2-botocore-1.3.17 python2-bandit-0.13.2 python2-swiftclient-2.6.0
python2-pytest-xdist-1.14 beets-1.3.17 python-flask-0.10.1
python-pickleshare-0.5 python-numexpr-2.4.4 python-h5py-2.4.0
shogun-4.0.0 python-biopython-1.66 python-statsmodels-0.6.1
python-seaborn-0.5.1 python-scikit-learn-0.16.1
python-scikit-image-0.11.3 idr-2.0.0 python-jellyfish-0.5.3
python-rq-0.5.2 python-urllib3-1.13.1 python-bandit-0.13.2
python-pytest-xdist-1.14 awscli-1.9.17 python-alembic-0.8.4
python-pytest-xprocess-0.9.1 livestreamer-1.12.2 python-acme-0.4.2
python-responses-0.5.1 python-ipython-3.2.1 git-annex-remote-hubic-0.3.1
docker-compose-1.5.2 diffoscope-49 python-pylast-1.5.1 khal-0.7.0
autojump-22.2.4
Leo Famulari (3):
gnu: python-pytest: Update to 2.7.3.
gnu: python-cryptography, python-cryptography-vectors: Update to
1.3.1.
gnu: python-pyopenssl: Update to 16.0.0.
gnu/packages/python.scm | 37 ++++++++-----------------------------
1 file changed, 8 insertions(+), 29 deletions(-)
--
2.7.3
^ permalink raw reply [flat|nested] 19+ messages in thread
* [PATCH 1/3] gnu: python-pytest: Update to 2.7.3.
2016-03-23 1:46 [PATCH 0/3] Fix letsencrypt Leo Famulari
@ 2016-03-23 1:46 ` Leo Famulari
2016-03-23 7:16 ` Efraim Flashner
2016-03-23 1:46 ` [PATCH 2/3] gnu: python-cryptography, python-cryptography-vectors: Update to 1.3.1 Leo Famulari
` (4 subsequent siblings)
5 siblings, 1 reply; 19+ messages in thread
From: Leo Famulari @ 2016-03-23 1:46 UTC (permalink / raw)
To: guix-devel
* gnu/packages/python.scm (python-pytest, python2-pytest): Update to 2.7.3.
---
gnu/packages/python.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
index 97a69c3..781a9f6 100644
--- a/gnu/packages/python.scm
+++ b/gnu/packages/python.scm
@@ -1530,7 +1530,7 @@ code introspection, and logging.")
(define-public python-pytest
(package
(name "python-pytest")
- (version "2.6.1")
+ (version "2.7.3")
(source
(origin
(method url-fetch)
@@ -1539,7 +1539,7 @@ code introspection, and logging.")
version ".tar.gz"))
(sha256
(base32
- "0g2w4p0n42wvz8rq4k6gnzpkakgz3g8sfanxk8jrsra9675snkcr"))
+ "1z4yi986f9n0p8qmzmn21m21m8j1x78hk3505f89baqm6pdw7afm"))
(modules '((guix build utils)))
(snippet
;; One of the tests involves the /usr directory, so it fails.
--
2.7.3
^ permalink raw reply related [flat|nested] 19+ messages in thread
* [PATCH 2/3] gnu: python-cryptography, python-cryptography-vectors: Update to 1.3.1.
2016-03-23 1:46 [PATCH 0/3] Fix letsencrypt Leo Famulari
2016-03-23 1:46 ` [PATCH 1/3] gnu: python-pytest: Update to 2.7.3 Leo Famulari
@ 2016-03-23 1:46 ` Leo Famulari
2016-03-23 7:16 ` Efraim Flashner
2016-03-23 1:46 ` [PATCH 3/3] gnu: python-pyopenssl: Update to 16.0.0 Leo Famulari
` (3 subsequent siblings)
5 siblings, 1 reply; 19+ messages in thread
From: Leo Famulari @ 2016-03-23 1:46 UTC (permalink / raw)
To: guix-devel
These packages should be udpated together.
* gnu/packages/python.scm (python-cryptography): Update to 1.3.1.
(python-cryptogprahy-vectors): Update to 1.3.1.
---
gnu/packages/python.scm | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
index 781a9f6..571b26b 100644
--- a/gnu/packages/python.scm
+++ b/gnu/packages/python.scm
@@ -5771,7 +5771,7 @@ responses, rather than doing any computation.")
(define-public python-cryptography-vectors
(package
(name "python-cryptography-vectors")
- (version "1.2.3")
+ (version "1.3.1")
(source
(origin
(method url-fetch)
@@ -5780,7 +5780,7 @@ responses, rather than doing any computation.")
version ".tar.gz"))
(sha256
(base32
- "0shawgpax79gvjrj0a313sll9gaqys7q1hxngn6j4k24lmz7bwki"))))
+ "1144l3ypz3bngxd59lb4y74xa401w92lhvvjgxzglmvbh8wzkcbb"))))
(build-system python-build-system)
(native-inputs
`(("python-setuptools" ,python-setuptools)))
@@ -5797,14 +5797,14 @@ responses, rather than doing any computation.")
(define-public python-cryptography
(package
(name "python-cryptography")
- (version "1.2.3")
+ (version "1.3.1")
(source
(origin
(method url-fetch)
(uri (pypi-uri "cryptography" version))
(sha256
(base32
- "0kj511z4g21fhcr649pyzpl0zzkkc7hsgxxjys6z8wwfvmvirccf"))))
+ "1qjkrpfvxcyd0kal3zpm5y7f9p3y77ixn9jw8f4dqpgrw1sn3cxl"))))
(build-system python-build-system)
(inputs
`(("openssl" ,openssl)))
--
2.7.3
^ permalink raw reply related [flat|nested] 19+ messages in thread
* [PATCH 3/3] gnu: python-pyopenssl: Update to 16.0.0.
2016-03-23 1:46 [PATCH 0/3] Fix letsencrypt Leo Famulari
2016-03-23 1:46 ` [PATCH 1/3] gnu: python-pytest: Update to 2.7.3 Leo Famulari
2016-03-23 1:46 ` [PATCH 2/3] gnu: python-cryptography, python-cryptography-vectors: Update to 1.3.1 Leo Famulari
@ 2016-03-23 1:46 ` Leo Famulari
2016-03-23 7:16 ` Efraim Flashner
2016-03-23 16:12 ` [PATCH 0/3] Fix letsencrypt Leo Famulari
` (2 subsequent siblings)
5 siblings, 1 reply; 19+ messages in thread
From: Leo Famulari @ 2016-03-23 1:46 UTC (permalink / raw)
To: guix-devel
* gnu/packages/python.scm (python-pyopenssl, python2-pyopenssl): Update to
16.0.0.
[arguments]: Remove field.
---
gnu/packages/python.scm | 25 ++-----------------------
1 file changed, 2 insertions(+), 23 deletions(-)
diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
index 571b26b..2238ae2 100644
--- a/gnu/packages/python.scm
+++ b/gnu/packages/python.scm
@@ -5848,7 +5848,7 @@ message digests and key derivation functions.")
(define-public python-pyopenssl
(package
(name "python-pyopenssl")
- (version "0.15.1")
+ (version "16.0.0")
(source
(origin
(method url-fetch)
@@ -5856,29 +5856,8 @@ message digests and key derivation functions.")
"pyOpenSSL/pyOpenSSL-" version ".tar.gz"))
(sha256
(base32
- "0wnnq15rhj7fhdcd8ycwiw6r6g3w9f9lcy6cigg8226vsrq618ph"))))
+ "0zfijaxlq4vgi6jz0d4i5xq9ygqnyps6br7lmigjhqnh8gp10g9n"))))
(build-system python-build-system)
- (arguments
- `(#:phases
- (modify-phases %standard-phases
- (add-after 'unpack 'fix-tests
- (lambda* (#:key inputs #:allow-other-keys)
- (substitute* "OpenSSL/test/test_ssl.py"
- (("client\\.connect\\(\\('verisign\\.com', 443\\)\\)")
- "return True")
- ;; FIXME: disable broken test
- (("test_set_tmp_ecdh") "disabled__set_tmp_ecdh"))
- (substitute* "OpenSSL/test/test_crypto.py"
- (("command = b\"openssl \"")
- (string-append "command = b\""
- (assoc-ref inputs "openssl")
- "/bin/openssl" " \""))
- ;; FIXME: disable four broken tests
- (("test_der") "disabled__der")
- (("test_digest") "disabled__digest")
- (("test_get_extension") "disabled__get_extension")
- (("test_extension_count") "disabled__extension_count"))
- #t)))))
(propagated-inputs
`(("python-cryptography" ,python-cryptography)
("python-six" ,python-six)))
--
2.7.3
^ permalink raw reply related [flat|nested] 19+ messages in thread
* Re: [PATCH 1/3] gnu: python-pytest: Update to 2.7.3.
2016-03-23 1:46 ` [PATCH 1/3] gnu: python-pytest: Update to 2.7.3 Leo Famulari
@ 2016-03-23 7:16 ` Efraim Flashner
0 siblings, 0 replies; 19+ messages in thread
From: Efraim Flashner @ 2016-03-23 7:16 UTC (permalink / raw)
To: Leo Famulari; +Cc: guix-devel
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
On Tue, Mar 22, 2016 at 09:46:10PM -0400, Leo Famulari wrote:
> * gnu/packages/python.scm (python-pytest, python2-pytest): Update to 2.7.3.
> ---
> gnu/packages/python.scm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
> index 97a69c3..781a9f6 100644
> --- a/gnu/packages/python.scm
> +++ b/gnu/packages/python.scm
> @@ -1530,7 +1530,7 @@ code introspection, and logging.")
> (define-public python-pytest
> (package
> (name "python-pytest")
> - (version "2.6.1")
> + (version "2.7.3")
> (source
> (origin
> (method url-fetch)
> @@ -1539,7 +1539,7 @@ code introspection, and logging.")
> version ".tar.gz"))
> (sha256
> (base32
> - "0g2w4p0n42wvz8rq4k6gnzpkakgz3g8sfanxk8jrsra9675snkcr"))
> + "1z4yi986f9n0p8qmzmn21m21m8j1x78hk3505f89baqm6pdw7afm"))
> (modules '((guix build utils)))
> (snippet
> ;; One of the tests involves the /usr directory, so it fails.
> --
> 2.7.3
>
>
LGTM!
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH 2/3] gnu: python-cryptography, python-cryptography-vectors: Update to 1.3.1.
2016-03-23 1:46 ` [PATCH 2/3] gnu: python-cryptography, python-cryptography-vectors: Update to 1.3.1 Leo Famulari
@ 2016-03-23 7:16 ` Efraim Flashner
0 siblings, 0 replies; 19+ messages in thread
From: Efraim Flashner @ 2016-03-23 7:16 UTC (permalink / raw)
To: Leo Famulari; +Cc: guix-devel
[-- Attachment #1: Type: text/plain, Size: 2078 bytes --]
On Tue, Mar 22, 2016 at 09:46:11PM -0400, Leo Famulari wrote:
> These packages should be udpated together.
>
> * gnu/packages/python.scm (python-cryptography): Update to 1.3.1.
> (python-cryptogprahy-vectors): Update to 1.3.1.
> ---
> gnu/packages/python.scm | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
> index 781a9f6..571b26b 100644
> --- a/gnu/packages/python.scm
> +++ b/gnu/packages/python.scm
> @@ -5771,7 +5771,7 @@ responses, rather than doing any computation.")
> (define-public python-cryptography-vectors
> (package
> (name "python-cryptography-vectors")
> - (version "1.2.3")
> + (version "1.3.1")
> (source
> (origin
> (method url-fetch)
> @@ -5780,7 +5780,7 @@ responses, rather than doing any computation.")
> version ".tar.gz"))
> (sha256
> (base32
> - "0shawgpax79gvjrj0a313sll9gaqys7q1hxngn6j4k24lmz7bwki"))))
> + "1144l3ypz3bngxd59lb4y74xa401w92lhvvjgxzglmvbh8wzkcbb"))))
> (build-system python-build-system)
> (native-inputs
> `(("python-setuptools" ,python-setuptools)))
> @@ -5797,14 +5797,14 @@ responses, rather than doing any computation.")
> (define-public python-cryptography
> (package
> (name "python-cryptography")
> - (version "1.2.3")
> + (version "1.3.1")
> (source
> (origin
> (method url-fetch)
> (uri (pypi-uri "cryptography" version))
> (sha256
> (base32
> - "0kj511z4g21fhcr649pyzpl0zzkkc7hsgxxjys6z8wwfvmvirccf"))))
> + "1qjkrpfvxcyd0kal3zpm5y7f9p3y77ixn9jw8f4dqpgrw1sn3cxl"))))
> (build-system python-build-system)
> (inputs
> `(("openssl" ,openssl)))
> --
> 2.7.3
>
>
LGTM!
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH 3/3] gnu: python-pyopenssl: Update to 16.0.0.
2016-03-23 1:46 ` [PATCH 3/3] gnu: python-pyopenssl: Update to 16.0.0 Leo Famulari
@ 2016-03-23 7:16 ` Efraim Flashner
2016-03-23 16:05 ` Leo Famulari
0 siblings, 1 reply; 19+ messages in thread
From: Efraim Flashner @ 2016-03-23 7:16 UTC (permalink / raw)
To: Leo Famulari; +Cc: guix-devel
[-- Attachment #1: Type: text/plain, Size: 2631 bytes --]
On Tue, Mar 22, 2016 at 09:46:12PM -0400, Leo Famulari wrote:
> * gnu/packages/python.scm (python-pyopenssl, python2-pyopenssl): Update to
> 16.0.0.
> [arguments]: Remove field.
> ---
> gnu/packages/python.scm | 25 ++-----------------------
> 1 file changed, 2 insertions(+), 23 deletions(-)
>
> diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
> index 571b26b..2238ae2 100644
> --- a/gnu/packages/python.scm
> +++ b/gnu/packages/python.scm
> @@ -5848,7 +5848,7 @@ message digests and key derivation functions.")
> (define-public python-pyopenssl
> (package
> (name "python-pyopenssl")
> - (version "0.15.1")
> + (version "16.0.0")
> (source
> (origin
> (method url-fetch)
> @@ -5856,29 +5856,8 @@ message digests and key derivation functions.")
> "pyOpenSSL/pyOpenSSL-" version ".tar.gz"))
> (sha256
> (base32
> - "0wnnq15rhj7fhdcd8ycwiw6r6g3w9f9lcy6cigg8226vsrq618ph"))))
> + "0zfijaxlq4vgi6jz0d4i5xq9ygqnyps6br7lmigjhqnh8gp10g9n"))))
> (build-system python-build-system)
> - (arguments
> - `(#:phases
> - (modify-phases %standard-phases
> - (add-after 'unpack 'fix-tests
> - (lambda* (#:key inputs #:allow-other-keys)
> - (substitute* "OpenSSL/test/test_ssl.py"
> - (("client\\.connect\\(\\('verisign\\.com', 443\\)\\)")
> - "return True")
> - ;; FIXME: disable broken test
> - (("test_set_tmp_ecdh") "disabled__set_tmp_ecdh"))
> - (substitute* "OpenSSL/test/test_crypto.py"
> - (("command = b\"openssl \"")
> - (string-append "command = b\""
> - (assoc-ref inputs "openssl")
> - "/bin/openssl" " \""))
> - ;; FIXME: disable four broken tests
> - (("test_der") "disabled__der")
> - (("test_digest") "disabled__digest")
> - (("test_get_extension") "disabled__get_extension")
> - (("test_extension_count") "disabled__extension_count"))
> - #t)))))
> (propagated-inputs
> `(("python-cryptography" ,python-cryptography)
> ("python-six" ,python-six)))
> --
> 2.7.3
>
its always nice to see work-around phases getting removed.
LGTM!
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH 3/3] gnu: python-pyopenssl: Update to 16.0.0.
2016-03-23 7:16 ` Efraim Flashner
@ 2016-03-23 16:05 ` Leo Famulari
0 siblings, 0 replies; 19+ messages in thread
From: Leo Famulari @ 2016-03-23 16:05 UTC (permalink / raw)
To: Efraim Flashner; +Cc: guix-devel
On Wed, Mar 23, 2016 at 09:16:42AM +0200, Efraim Flashner wrote:
> On Tue, Mar 22, 2016 at 09:46:12PM -0400, Leo Famulari wrote:
> > * gnu/packages/python.scm (python-pyopenssl, python2-pyopenssl): Update to
> > 16.0.0.
> > [arguments]: Remove field.
> > - (arguments
> > - `(#:phases
> > - (modify-phases %standard-phases
> > - (add-after 'unpack 'fix-tests
> > - (lambda* (#:key inputs #:allow-other-keys)
> > - (substitute* "OpenSSL/test/test_ssl.py"
> > - (("client\\.connect\\(\\('verisign\\.com', 443\\)\\)")
> > - "return True")
> > - ;; FIXME: disable broken test
> > - (("test_set_tmp_ecdh") "disabled__set_tmp_ecdh"))
> > - (substitute* "OpenSSL/test/test_crypto.py"
> > - (("command = b\"openssl \"")
> > - (string-append "command = b\""
> > - (assoc-ref inputs "openssl")
> > - "/bin/openssl" " \""))
> > - ;; FIXME: disable four broken tests
> > - (("test_der") "disabled__der")
> > - (("test_digest") "disabled__digest")
> > - (("test_get_extension") "disabled__get_extension")
> > - (("test_extension_count") "disabled__extension_count"))
> > - #t)))))
> > (propagated-inputs
> > `(("python-cryptography" ,python-cryptography)
> > ("python-six" ,python-six)))
> > --
> > 2.7.3
> >
>
> its always nice to see work-around phases getting removed.
Indeed!
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH 0/3] Fix letsencrypt
2016-03-23 1:46 [PATCH 0/3] Fix letsencrypt Leo Famulari
` (2 preceding siblings ...)
2016-03-23 1:46 ` [PATCH 3/3] gnu: python-pyopenssl: Update to 16.0.0 Leo Famulari
@ 2016-03-23 16:12 ` Leo Famulari
2016-03-25 16:29 ` Leo Famulari
2016-03-23 20:44 ` Ricardo Wurmus
2016-03-27 22:02 ` Leo Famulari
5 siblings, 1 reply; 19+ messages in thread
From: Leo Famulari @ 2016-03-23 16:12 UTC (permalink / raw)
To: guix-devel
On Tue, Mar 22, 2016 at 09:46:09PM -0400, Leo Famulari wrote:
> Earlier today I found that I could not build letsencrypt.
>
> The recent update to python-hypothesis broke python-pyopenssl, which
> blocked the build of letsencrypt.
>
> This patch series seems to be the minimum required to get letsencrypt
> building again. I built letsencrypt on these patches and used it to
> issue certificates for a new server.
>
> The update to python-pytest and python2-pytest will require ~200
> rebuilds [0].
Any advice on where to apply these patches?
>
> This does not update python-pytest to the latest version, 2.9.1. I could
> not get that to work, and I suspect it will require updates to some core
> Python packages such as python-setuptools.
>
> In the meantime, I'd like to do this intermediate update to get
> letsencrypt building again. Any objections? If it's okay, should it go
> on master, or onto a staging branch?
>
> [0] I have re-wrapped this for readability:
>
> $ guix refresh -l python2-pytest python-pytest
> Building the following 66 packages would ensure 194 dependent packages
> are rebuilt: python2-pickleshare-0.5 python2-scikit-image-0.11.3
> python2-statsmodels-0.6.1 python2-seaborn-0.5.1 python2-numexpr-2.4.4
> enblend-enfuse-4.1.3 libreoffice-5.0.5.2 seqmagick-0.6.1 pepr-1.0.9
> grit-2.0.2 pbtranscript-tofu-2.2.3.8f5467fe6 macs-2.1.0.20151222
> crossmap-0.2.1 rseqc-2.6.1 pyicoteo-2.0.7 python2-warpedlmm-0.21
> clipper-0.3.0 deeptools-2.1.1 miso-0.5.3 couger-1.8.2 gourmet-0.17.4
> python2-rq-0.5.2 python2-urllib3-1.13.1 python2-ndg-httpsclient-0.4.0
> gajim-0.16.5 python2-docopt-0.6.2 python2-pytest-subtesthack-0.1.1
> python2-alembic-0.8.4 letsencrypt-0.4.2 python2-rauth-0.7.2
> python2-ipython-3.2.1
> simp-le-2015-12-07T040251Z-01afa8c64264a7674e51471ea4bf7ce524d8b77e
> python2-botocore-1.3.17 python2-bandit-0.13.2 python2-swiftclient-2.6.0
> python2-pytest-xdist-1.14 beets-1.3.17 python-flask-0.10.1
> python-pickleshare-0.5 python-numexpr-2.4.4 python-h5py-2.4.0
> shogun-4.0.0 python-biopython-1.66 python-statsmodels-0.6.1
> python-seaborn-0.5.1 python-scikit-learn-0.16.1
> python-scikit-image-0.11.3 idr-2.0.0 python-jellyfish-0.5.3
> python-rq-0.5.2 python-urllib3-1.13.1 python-bandit-0.13.2
> python-pytest-xdist-1.14 awscli-1.9.17 python-alembic-0.8.4
> python-pytest-xprocess-0.9.1 livestreamer-1.12.2 python-acme-0.4.2
> python-responses-0.5.1 python-ipython-3.2.1 git-annex-remote-hubic-0.3.1
> docker-compose-1.5.2 diffoscope-49 python-pylast-1.5.1 khal-0.7.0
> autojump-22.2.4
>
> Leo Famulari (3):
> gnu: python-pytest: Update to 2.7.3.
> gnu: python-cryptography, python-cryptography-vectors: Update to
> 1.3.1.
> gnu: python-pyopenssl: Update to 16.0.0.
>
> gnu/packages/python.scm | 37 ++++++++-----------------------------
> 1 file changed, 8 insertions(+), 29 deletions(-)
>
> --
> 2.7.3
>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH 0/3] Fix letsencrypt
2016-03-23 1:46 [PATCH 0/3] Fix letsencrypt Leo Famulari
` (3 preceding siblings ...)
2016-03-23 16:12 ` [PATCH 0/3] Fix letsencrypt Leo Famulari
@ 2016-03-23 20:44 ` Ricardo Wurmus
2016-03-27 22:02 ` Leo Famulari
5 siblings, 0 replies; 19+ messages in thread
From: Ricardo Wurmus @ 2016-03-23 20:44 UTC (permalink / raw)
To: Leo Famulari; +Cc: guix-devel
Leo Famulari <leo@famulari.name> writes:
> Earlier today I found that I could not build letsencrypt.
>
> The recent update to python-hypothesis broke python-pyopenssl, which
> blocked the build of letsencrypt.
>
> This patch series seems to be the minimum required to get letsencrypt
> building again. I built letsencrypt on these patches and used it to
> issue certificates for a new server.
>
> The update to python-pytest and python2-pytest will require ~200
> rebuilds [0].
>
> This does not update python-pytest to the latest version, 2.9.1. I could
> not get that to work, and I suspect it will require updates to some core
> Python packages such as python-setuptools.
>
> In the meantime, I'd like to do this intermediate update to get
> letsencrypt building again. Any objections? If it's okay, should it go
> on master, or onto a staging branch?
I’m okay with this. Thanks for taking it on!
I hope not too many of the bioinfo packages fail to build because of
this, but we’ll see ... :)
~~ Ricardo
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH 0/3] Fix letsencrypt
2016-03-23 16:12 ` [PATCH 0/3] Fix letsencrypt Leo Famulari
@ 2016-03-25 16:29 ` Leo Famulari
2016-03-25 23:06 ` Ludovic Courtès
0 siblings, 1 reply; 19+ messages in thread
From: Leo Famulari @ 2016-03-25 16:29 UTC (permalink / raw)
To: guix-devel
On Wed, Mar 23, 2016 at 12:12:20PM -0400, Leo Famulari wrote:
> On Tue, Mar 22, 2016 at 09:46:09PM -0400, Leo Famulari wrote:
> > Earlier today I found that I could not build letsencrypt.
> >
> > The recent update to python-hypothesis broke python-pyopenssl, which
> > blocked the build of letsencrypt.
> >
> > This patch series seems to be the minimum required to get letsencrypt
> > building again. I built letsencrypt on these patches and used it to
> > issue certificates for a new server.
> >
> > The update to python-pytest and python2-pytest will require ~200
> > rebuilds [0].
>
> Any advice on where to apply these patches?
I pushed the branch 'fix-letsencrypt' to Savannah. My understanding is
that we will merge it after the next release.
>
> >
> > This does not update python-pytest to the latest version, 2.9.1. I could
> > not get that to work, and I suspect it will require updates to some core
> > Python packages such as python-setuptools.
> >
> > In the meantime, I'd like to do this intermediate update to get
> > letsencrypt building again. Any objections? If it's okay, should it go
> > on master, or onto a staging branch?
> >
> > [0] I have re-wrapped this for readability:
> >
> > $ guix refresh -l python2-pytest python-pytest
> > Building the following 66 packages would ensure 194 dependent packages
> > are rebuilt: python2-pickleshare-0.5 python2-scikit-image-0.11.3
> > python2-statsmodels-0.6.1 python2-seaborn-0.5.1 python2-numexpr-2.4.4
> > enblend-enfuse-4.1.3 libreoffice-5.0.5.2 seqmagick-0.6.1 pepr-1.0.9
> > grit-2.0.2 pbtranscript-tofu-2.2.3.8f5467fe6 macs-2.1.0.20151222
> > crossmap-0.2.1 rseqc-2.6.1 pyicoteo-2.0.7 python2-warpedlmm-0.21
> > clipper-0.3.0 deeptools-2.1.1 miso-0.5.3 couger-1.8.2 gourmet-0.17.4
> > python2-rq-0.5.2 python2-urllib3-1.13.1 python2-ndg-httpsclient-0.4.0
> > gajim-0.16.5 python2-docopt-0.6.2 python2-pytest-subtesthack-0.1.1
> > python2-alembic-0.8.4 letsencrypt-0.4.2 python2-rauth-0.7.2
> > python2-ipython-3.2.1
> > simp-le-2015-12-07T040251Z-01afa8c64264a7674e51471ea4bf7ce524d8b77e
> > python2-botocore-1.3.17 python2-bandit-0.13.2 python2-swiftclient-2.6.0
> > python2-pytest-xdist-1.14 beets-1.3.17 python-flask-0.10.1
> > python-pickleshare-0.5 python-numexpr-2.4.4 python-h5py-2.4.0
> > shogun-4.0.0 python-biopython-1.66 python-statsmodels-0.6.1
> > python-seaborn-0.5.1 python-scikit-learn-0.16.1
> > python-scikit-image-0.11.3 idr-2.0.0 python-jellyfish-0.5.3
> > python-rq-0.5.2 python-urllib3-1.13.1 python-bandit-0.13.2
> > python-pytest-xdist-1.14 awscli-1.9.17 python-alembic-0.8.4
> > python-pytest-xprocess-0.9.1 livestreamer-1.12.2 python-acme-0.4.2
> > python-responses-0.5.1 python-ipython-3.2.1 git-annex-remote-hubic-0.3.1
> > docker-compose-1.5.2 diffoscope-49 python-pylast-1.5.1 khal-0.7.0
> > autojump-22.2.4
> >
> > Leo Famulari (3):
> > gnu: python-pytest: Update to 2.7.3.
> > gnu: python-cryptography, python-cryptography-vectors: Update to
> > 1.3.1.
> > gnu: python-pyopenssl: Update to 16.0.0.
> >
> > gnu/packages/python.scm | 37 ++++++++-----------------------------
> > 1 file changed, 8 insertions(+), 29 deletions(-)
> >
> > --
> > 2.7.3
> >
>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH 0/3] Fix letsencrypt
2016-03-25 16:29 ` Leo Famulari
@ 2016-03-25 23:06 ` Ludovic Courtès
2016-03-29 19:56 ` Leo Famulari
0 siblings, 1 reply; 19+ messages in thread
From: Ludovic Courtès @ 2016-03-25 23:06 UTC (permalink / raw)
To: Leo Famulari; +Cc: guix-devel
Leo Famulari <leo@famulari.name> skribis:
> On Wed, Mar 23, 2016 at 12:12:20PM -0400, Leo Famulari wrote:
>> On Tue, Mar 22, 2016 at 09:46:09PM -0400, Leo Famulari wrote:
>> > Earlier today I found that I could not build letsencrypt.
>> >
>> > The recent update to python-hypothesis broke python-pyopenssl, which
>> > blocked the build of letsencrypt.
>> >
>> > This patch series seems to be the minimum required to get letsencrypt
>> > building again. I built letsencrypt on these patches and used it to
>> > issue certificates for a new server.
>> >
>> > The update to python-pytest and python2-pytest will require ~200
>> > rebuilds [0].
>>
>> Any advice on where to apply these patches?
>
> I pushed the branch 'fix-letsencrypt' to Savannah. My understanding is
> that we will merge it after the next release.
Yes, I think that’s a reasonable approach.
Thank you, and sorry for the delay!
Ludo’.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH 0/3] Fix letsencrypt
2016-03-23 1:46 [PATCH 0/3] Fix letsencrypt Leo Famulari
` (4 preceding siblings ...)
2016-03-23 20:44 ` Ricardo Wurmus
@ 2016-03-27 22:02 ` Leo Famulari
5 siblings, 0 replies; 19+ messages in thread
From: Leo Famulari @ 2016-03-27 22:02 UTC (permalink / raw)
To: guix-devel
On Tue, Mar 22, 2016 at 09:46:09PM -0400, Leo Famulari wrote:
> Earlier today I found that I could not build letsencrypt.
>
> The recent update to python-hypothesis broke python-pyopenssl, which
> blocked the build of letsencrypt.
>
> This patch series seems to be the minimum required to get letsencrypt
> building again. I built letsencrypt on these patches and used it to
> issue certificates for a new server.
>
> The update to python-pytest and python2-pytest will require ~200
> rebuilds [0].
With these changes, libreoffice continues to build successfully for me
on x86-64. I'm currently attempting to cross-build to i686.
>
> This does not update python-pytest to the latest version, 2.9.1. I could
> not get that to work, and I suspect it will require updates to some core
> Python packages such as python-setuptools.
>
> In the meantime, I'd like to do this intermediate update to get
> letsencrypt building again. Any objections? If it's okay, should it go
> on master, or onto a staging branch?
>
> [0] I have re-wrapped this for readability:
>
> $ guix refresh -l python2-pytest python-pytest
> Building the following 66 packages would ensure 194 dependent packages
> are rebuilt: python2-pickleshare-0.5 python2-scikit-image-0.11.3
> python2-statsmodels-0.6.1 python2-seaborn-0.5.1 python2-numexpr-2.4.4
> enblend-enfuse-4.1.3 libreoffice-5.0.5.2 seqmagick-0.6.1 pepr-1.0.9
> grit-2.0.2 pbtranscript-tofu-2.2.3.8f5467fe6 macs-2.1.0.20151222
> crossmap-0.2.1 rseqc-2.6.1 pyicoteo-2.0.7 python2-warpedlmm-0.21
> clipper-0.3.0 deeptools-2.1.1 miso-0.5.3 couger-1.8.2 gourmet-0.17.4
> python2-rq-0.5.2 python2-urllib3-1.13.1 python2-ndg-httpsclient-0.4.0
> gajim-0.16.5 python2-docopt-0.6.2 python2-pytest-subtesthack-0.1.1
> python2-alembic-0.8.4 letsencrypt-0.4.2 python2-rauth-0.7.2
> python2-ipython-3.2.1
> simp-le-2015-12-07T040251Z-01afa8c64264a7674e51471ea4bf7ce524d8b77e
> python2-botocore-1.3.17 python2-bandit-0.13.2 python2-swiftclient-2.6.0
> python2-pytest-xdist-1.14 beets-1.3.17 python-flask-0.10.1
> python-pickleshare-0.5 python-numexpr-2.4.4 python-h5py-2.4.0
> shogun-4.0.0 python-biopython-1.66 python-statsmodels-0.6.1
> python-seaborn-0.5.1 python-scikit-learn-0.16.1
> python-scikit-image-0.11.3 idr-2.0.0 python-jellyfish-0.5.3
> python-rq-0.5.2 python-urllib3-1.13.1 python-bandit-0.13.2
> python-pytest-xdist-1.14 awscli-1.9.17 python-alembic-0.8.4
> python-pytest-xprocess-0.9.1 livestreamer-1.12.2 python-acme-0.4.2
> python-responses-0.5.1 python-ipython-3.2.1 git-annex-remote-hubic-0.3.1
> docker-compose-1.5.2 diffoscope-49 python-pylast-1.5.1 khal-0.7.0
> autojump-22.2.4
>
> Leo Famulari (3):
> gnu: python-pytest: Update to 2.7.3.
> gnu: python-cryptography, python-cryptography-vectors: Update to
> 1.3.1.
> gnu: python-pyopenssl: Update to 16.0.0.
>
> gnu/packages/python.scm | 37 ++++++++-----------------------------
> 1 file changed, 8 insertions(+), 29 deletions(-)
>
> --
> 2.7.3
>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH 0/3] Fix letsencrypt
2016-03-25 23:06 ` Ludovic Courtès
@ 2016-03-29 19:56 ` Leo Famulari
2016-03-31 21:48 ` Ludovic Courtès
0 siblings, 1 reply; 19+ messages in thread
From: Leo Famulari @ 2016-03-29 19:56 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: guix-devel
On Sat, Mar 26, 2016 at 12:06:06AM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
>
> > On Wed, Mar 23, 2016 at 12:12:20PM -0400, Leo Famulari wrote:
> >> On Tue, Mar 22, 2016 at 09:46:09PM -0400, Leo Famulari wrote:
> >> > Earlier today I found that I could not build letsencrypt.
> >> >
> >> > The recent update to python-hypothesis broke python-pyopenssl, which
> >> > blocked the build of letsencrypt.
> >> >
> >> > This patch series seems to be the minimum required to get letsencrypt
> >> > building again. I built letsencrypt on these patches and used it to
> >> > issue certificates for a new server.
> >> >
> >> > The update to python-pytest and python2-pytest will require ~200
> >> > rebuilds [0].
> >>
> >> Any advice on where to apply these patches?
> >
> > I pushed the branch 'fix-letsencrypt' to Savannah. My understanding is
> > that we will merge it after the next release.
>
> Yes, I think that’s a reasonable approach.
>
> Thank you, and sorry for the delay!
Okay, now that we have released, what should we do about this branch?
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH 0/3] Fix letsencrypt
2016-03-29 19:56 ` Leo Famulari
@ 2016-03-31 21:48 ` Ludovic Courtès
2016-04-03 0:30 ` Leo Famulari
0 siblings, 1 reply; 19+ messages in thread
From: Ludovic Courtès @ 2016-03-31 21:48 UTC (permalink / raw)
To: Leo Famulari; +Cc: guix-devel
Leo Famulari <leo@famulari.name> skribis:
> On Sat, Mar 26, 2016 at 12:06:06AM +0100, Ludovic Courtès wrote:
>> Leo Famulari <leo@famulari.name> skribis:
>>
>> > On Wed, Mar 23, 2016 at 12:12:20PM -0400, Leo Famulari wrote:
>> >> On Tue, Mar 22, 2016 at 09:46:09PM -0400, Leo Famulari wrote:
>> >> > Earlier today I found that I could not build letsencrypt.
>> >> >
>> >> > The recent update to python-hypothesis broke python-pyopenssl, which
>> >> > blocked the build of letsencrypt.
>> >> >
>> >> > This patch series seems to be the minimum required to get letsencrypt
>> >> > building again. I built letsencrypt on these patches and used it to
>> >> > issue certificates for a new server.
>> >> >
>> >> > The update to python-pytest and python2-pytest will require ~200
>> >> > rebuilds [0].
>> >>
>> >> Any advice on where to apply these patches?
>> >
>> > I pushed the branch 'fix-letsencrypt' to Savannah. My understanding is
>> > that we will merge it after the next release.
>>
>> Yes, I think that’s a reasonable approach.
>>
>> Thank you, and sorry for the delay!
>
> Okay, now that we have released, what should we do about this branch?
Could you rebase it on top of current master, and then ask Mark to set
it up on Hydra? (I can take care of Hydra tomorrow if Mark is
unavailable now.)
Thanks!
Ludo’.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH 0/3] Fix letsencrypt
2016-03-31 21:48 ` Ludovic Courtès
@ 2016-04-03 0:30 ` Leo Famulari
2016-04-03 6:14 ` Efraim Flashner
0 siblings, 1 reply; 19+ messages in thread
From: Leo Famulari @ 2016-04-03 0:30 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: guix-devel
On Thu, Mar 31, 2016 at 11:48:30PM +0200, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
>
> > On Sat, Mar 26, 2016 at 12:06:06AM +0100, Ludovic Courtès wrote:
> >> Leo Famulari <leo@famulari.name> skribis:
> >>
> >> > On Wed, Mar 23, 2016 at 12:12:20PM -0400, Leo Famulari wrote:
> >> >> On Tue, Mar 22, 2016 at 09:46:09PM -0400, Leo Famulari wrote:
> >> >> > Earlier today I found that I could not build letsencrypt.
> >> >> >
> >> >> > The recent update to python-hypothesis broke python-pyopenssl, which
> >> >> > blocked the build of letsencrypt.
> >> >> >
> >> >> > This patch series seems to be the minimum required to get letsencrypt
> >> >> > building again. I built letsencrypt on these patches and used it to
> >> >> > issue certificates for a new server.
> >> >> >
> >> >> > The update to python-pytest and python2-pytest will require ~200
> >> >> > rebuilds [0].
> >> >>
> >> >> Any advice on where to apply these patches?
> >> >
> >> > I pushed the branch 'fix-letsencrypt' to Savannah. My understanding is
> >> > that we will merge it after the next release.
> >>
> >> Yes, I think that’s a reasonable approach.
> >>
> >> Thank you, and sorry for the delay!
> >
> > Okay, now that we have released, what should we do about this branch?
>
> Could you rebase it on top of current master, and then ask Mark to set
> it up on Hydra? (I can take care of Hydra tomorrow if Mark is
> unavailable now.)
I think the job is complete, although I don't understand Hydra's
interface very well:
http://hydra.gnu.org/jobset/gnu/fix-letsencrypt/
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH 0/3] Fix letsencrypt
2016-04-03 0:30 ` Leo Famulari
@ 2016-04-03 6:14 ` Efraim Flashner
2016-04-04 17:52 ` Leo Famulari
0 siblings, 1 reply; 19+ messages in thread
From: Efraim Flashner @ 2016-04-03 6:14 UTC (permalink / raw)
To: Leo Famulari; +Cc: guix-devel
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
On Sat, 2 Apr 2016 20:30:33 -0400
Leo Famulari <leo@famulari.name> wrote:
> On Thu, Mar 31, 2016 at 11:48:30PM +0200, Ludovic Courtès wrote:
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
>
> I think the job is complete, although I don't understand Hydra's
> interface very well:
>
> http://hydra.gnu.org/jobset/gnu/fix-letsencrypt/
>
of the three new failures (compared to master), one built successfully and
two lost their lsh connection during building
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH 0/3] Fix letsencrypt
2016-04-03 6:14 ` Efraim Flashner
@ 2016-04-04 17:52 ` Leo Famulari
2016-04-04 18:12 ` Leo Famulari
0 siblings, 1 reply; 19+ messages in thread
From: Leo Famulari @ 2016-04-04 17:52 UTC (permalink / raw)
To: Efraim Flashner; +Cc: guix-devel
On Sun, Apr 03, 2016 at 09:14:52AM +0300, Efraim Flashner wrote:
> On Sat, 2 Apr 2016 20:30:33 -0400
> Leo Famulari <leo@famulari.name> wrote:
>
> > On Thu, Mar 31, 2016 at 11:48:30PM +0200, Ludovic Courtès wrote:
> > [...]
> > [...]
> > [...]
> > [...]
> > [...]
> > [...]
> > [...]
> > [...]
> > [...]
> > [...]
> > [...]
> >
> > I think the job is complete, although I don't understand Hydra's
> > interface very well:
> >
> > http://hydra.gnu.org/jobset/gnu/fix-letsencrypt/
> >
>
> of the three new failures (compared to master), one built successfully and
> two lost their lsh connection during building
How can I see what the new failures are?
>
> --
> Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
> GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
> Confidentiality cannot be guaranteed on emails sent or received unencrypted
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH 0/3] Fix letsencrypt
2016-04-04 17:52 ` Leo Famulari
@ 2016-04-04 18:12 ` Leo Famulari
0 siblings, 0 replies; 19+ messages in thread
From: Leo Famulari @ 2016-04-04 18:12 UTC (permalink / raw)
To: Efraim Flashner; +Cc: guix-devel
On Mon, Apr 04, 2016 at 01:52:24PM -0400, Leo Famulari wrote:
> On Sun, Apr 03, 2016 at 09:14:52AM +0300, Efraim Flashner wrote:
> > On Sat, 2 Apr 2016 20:30:33 -0400
> > Leo Famulari <leo@famulari.name> wrote:
> >
> > > On Thu, Mar 31, 2016 at 11:48:30PM +0200, Ludovic Courtès wrote:
> > > [...]
> > > [...]
> > > [...]
> > > [...]
> > > [...]
> > > [...]
> > > [...]
> > > [...]
> > > [...]
> > > [...]
> > > [...]
> > >
> > > I think the job is complete, although I don't understand Hydra's
> > > interface very well:
> > >
> > > http://hydra.gnu.org/jobset/gnu/fix-letsencrypt/
> > >
> >
> > of the three new failures (compared to master), one built successfully and
> > two lost their lsh connection during building
>
> How can I see what the new failures are?
Never mind, Mark explained it on IRC.
>
> >
> > --
> > Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
> > GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
> > Confidentiality cannot be guaranteed on emails sent or received unencrypted
>
>
>
^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2016-04-04 18:12 UTC | newest]
Thread overview: 19+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-03-23 1:46 [PATCH 0/3] Fix letsencrypt Leo Famulari
2016-03-23 1:46 ` [PATCH 1/3] gnu: python-pytest: Update to 2.7.3 Leo Famulari
2016-03-23 7:16 ` Efraim Flashner
2016-03-23 1:46 ` [PATCH 2/3] gnu: python-cryptography, python-cryptography-vectors: Update to 1.3.1 Leo Famulari
2016-03-23 7:16 ` Efraim Flashner
2016-03-23 1:46 ` [PATCH 3/3] gnu: python-pyopenssl: Update to 16.0.0 Leo Famulari
2016-03-23 7:16 ` Efraim Flashner
2016-03-23 16:05 ` Leo Famulari
2016-03-23 16:12 ` [PATCH 0/3] Fix letsencrypt Leo Famulari
2016-03-25 16:29 ` Leo Famulari
2016-03-25 23:06 ` Ludovic Courtès
2016-03-29 19:56 ` Leo Famulari
2016-03-31 21:48 ` Ludovic Courtès
2016-04-03 0:30 ` Leo Famulari
2016-04-03 6:14 ` Efraim Flashner
2016-04-04 17:52 ` Leo Famulari
2016-04-04 18:12 ` Leo Famulari
2016-03-23 20:44 ` Ricardo Wurmus
2016-03-27 22:02 ` Leo Famulari
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).