unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Frederick Muriithi <fredmanglis@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/4] gnu: Add python-pytest-3.0.7
Date: Tue, 28 Mar 2017 16:05:20 -0400	[thread overview]
Message-ID: <20170328200520.GE13687@jasmine> (raw)
In-Reply-To: <20170327150924.GA16027@jasmine>

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

On Mon, Mar 27, 2017 at 11:09:24AM -0400, Leo Famulari wrote:
> From f44c8d0dec2af7677ad16cfad877fb73407b6c30 Mon Sep 17 00:00:00 2001
> From: Leo Famulari <leo@famulari.name>
> Date: Mon, 27 Mar 2017 03:10:53 -0400
> Subject: [PATCH] gnu: python-pytest-2.9.2: Replace with python-pytest-3.0.
> 
> * gnu/packages/python.scm (python-pytest-2.9.2): Replace with ...
> (python-pytest-3.0): ... new variable.
> (python2-pytest-3.0): New variable.
> (python-cryptography, python2-cryptography)[native-inputs]: Replace
> python-pytest-2.9.2 with python-pytest-3.0.
> * gnu/packages/backup.scm (borg)[native-inputs]: Likewise.
> gnu/packages/calendar.scm (khal)[native-inputs]: Likewise.

I pushed a variant of this patch, so now there is one old pytest, and
one new pytest. Hopefully we can clean all these different versions of
pytest, sphinx, etc soon!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-03-28 20:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-26  9:23 [PATCH 1/4] gnu: Add python-pytest-3.0.7 Muriithi Frederick Muriuki
2017-03-26  9:23 ` [PATCH 2/4] gnu: Add python-sphinx-1.5.2, python-sphinx-1.5.3 Muriithi Frederick Muriuki
2017-03-26 15:10   ` Pjotr Prins
2017-03-26 15:32     ` Frederick Muriithi
2017-03-26 16:40       ` Pjotr Prins
2017-03-27 19:10         ` Ricardo Wurmus
2017-03-27 15:11       ` Leo Famulari
2017-03-27 15:12         ` Leo Famulari
2017-03-28 20:03           ` Leo Famulari
2017-03-26  9:23 ` [PATCH 3/4] gnu: Add python-paramunittest Muriithi Frederick Muriuki
2017-03-26 15:12   ` Pjotr Prins
2017-03-26 15:47     ` Frederick Muriithi
2017-03-26 23:32       ` Chris Marusich
2017-03-27  2:41         ` Frederick Muriithi
2017-03-28  5:16           ` Frederick Muriithi
2017-03-28 19:25             ` Ludovic Courtès
2017-03-28 20:03   ` Leo Famulari
2017-03-26  9:23 ` [PATCH 4/4] gnu: Add python-mando Muriithi Frederick Muriuki
2017-03-26 15:16   ` Pjotr Prins
2017-03-27 15:14   ` Leo Famulari
2017-03-28 19:28     ` Ludovic Courtès
2017-03-28 20:04   ` Leo Famulari
2017-03-26 15:10 ` [PATCH 1/4] gnu: Add python-pytest-3.0.7 Pjotr Prins
     [not found]   ` <CALjrZwaRUvrctcwwFQ_5isqwoaaEq=77P2qFHwk1FL2mJ5T-dg@mail.gmail.com>
     [not found]     ` <CALjrZwaah9_Vv+MVTm2aiA_-WHycYhn=KCnk5KjsXo=8z0+QDA@mail.gmail.com>
2017-03-26 15:29       ` Frederick Muriithi
2017-03-27 15:09         ` Leo Famulari
2017-03-28 20:05           ` Leo Famulari [this message]
2017-03-28 20:04 ` Leo Famulari

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=20170328200520.GE13687@jasmine \
    --to=leo@famulari.name \
    --cc=fredmanglis@gmail.com \
    --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).