From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tanguy Le Carrour <tanguy@bioneland.org>
Subject: gnu: python-pytest: Update to 5.2.1.
Date: Wed, 23 Oct 2019 09:22:43 +0200
Message-ID: <20191023072243.comuq7dmvnl67reo@rafflesia>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:41579)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <tanguy@bioneland.org>) id 1iNAyo-0001Ns-1q
 for guix-devel@gnu.org; Wed, 23 Oct 2019 03:22:50 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <tanguy@bioneland.org>) id 1iNAym-0005pr-QX
 for guix-devel@gnu.org; Wed, 23 Oct 2019 03:22:49 -0400
Received: from relay4-d.mail.gandi.net ([217.70.183.196]:52115)
 by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
 (Exim 4.71) (envelope-from <tanguy@bioneland.org>)
 id 1iNAym-0005ng-Ke
 for guix-devel@gnu.org; Wed, 23 Oct 2019 03:22:48 -0400
Content-Disposition: inline
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Guix <guix-devel@gnu.org>

Hi Guix!

I'm working on updating python-pytest and… not everything is going as
smoothly as I was expecting! :-(

Pytest 5.2.1 depends on Pluggy >=0.12.0… which depends on
importlib-metadata. But when I had the latter as a propagated-input to
python-pluggy, then `guix build` gets stuck.

    diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm
    index a7f83dcd31..ab80cdebf9 100644
    --- a/gnu/packages/python-xyz.scm
    +++ b/gnu/packages/python-xyz.scm
    @@ -8914,17 +8914,19 @@ library as well as on the command line.")
     (define-public python-pluggy
       (package
        (name "python-pluggy")
    -   (version "0.11.0")
    +   (version "0.13.0")
        (source
         (origin
          (method url-fetch)
          (uri (pypi-uri "pluggy" version))
          (sha256
           (base32
    -       "10511a54dvafw1jrk75mrhml53c7b7w4yaw7241696lc2hfvr895"))))
    +       "0d4gsvb4kjqhiqqi4bbsdp7s1xlyl5phibcw1q1mrpd65xia2pzs"))))
        (build-system python-build-system)
        (native-inputs
         `(("python-setuptools-scm" ,python-setuptools-scm)))
    +   (propagated-inputs
    +    `(("python-importlib-metadata" ,python-importlib-metadata)))
        (synopsis "Plugin and hook calling mechanism for Python")
        (description "Pluggy is an extraction of the plugin manager as used by
     Pytest but stripped of Pytest specific details.")

The problem seems to be that python-importlib-metadata's dependency graph
contains… python-pluggy!

How am I supposed to fix this chicken and egg situation?! Is this
something that should be notified to upstream?!

Regards

-- 
Tanguy