From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Re: [PATCH 0/3] Fix letsencrypt
Date: Sun, 27 Mar 2016 18:02:13 -0400 [thread overview]
Message-ID: <20160327220213.GA17279@jasmine> (raw)
In-Reply-To: <cover.1458697233.git.leo@famulari.name>
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
>
prev parent reply other threads:[~2016-03-27 22:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160327220213.GA17279@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).