From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: gnu: python-pytest: Update to 5.2.1. Date: Wed, 23 Oct 2019 19:47:11 +0200 Message-ID: <87r233we00.fsf@devup.no> References: <20191023072243.comuq7dmvnl67reo@rafflesia> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:33460) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iNKj7-0007Mh-MT for guix-devel@gnu.org; Wed, 23 Oct 2019 13:47:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iNKj5-0001Mb-HA for guix-devel@gnu.org; Wed, 23 Oct 2019 13:47:17 -0400 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]:56341) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iNKj5-0001M0-9f for guix-devel@gnu.org; Wed, 23 Oct 2019 13:47:15 -0400 In-Reply-To: <20191023072243.comuq7dmvnl67reo@rafflesia> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Tanguy Le Carrour , Guix --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Tanguy Le Carrour writes: > Hi Guix! > > I'm working on updating python-pytest and=E2=80=A6 not everything is goin= g as > smoothly as I was expecting! :-( > > Pytest 5.2.1 depends on Pluggy >=3D0.12.0=E2=80=A6 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 us= ed by > Pytest but stripped of Pytest specific details.") > > The problem seems to be that python-importlib-metadata's dependency graph > contains=E2=80=A6 python-pluggy! > > How am I supposed to fix this chicken and egg situation?! Is this > something that should be notified to upstream?! It would be great if you can make upstream aware of the issue. Note that if you just want to be able to use Pytest 5.x on the master branch, you can instead add a separate 'python-pluggy-0.13' variable and use that for 'python-pytest-5'. We'll still need to break the cycle in 'core-updates' though... --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl2wkh8ACgkQoqBt8qM6 VPrnZAgAgCU7clUPO7oQYqUBnXJeE7GLPXpC6Iszlj2OtR/BD0Hf9Dyyyx8q1bR3 Un9McTo6YKwQTD9cJYAIKCOexCpsbY8mF55Wj3REbfSgYetZ8xoAeZctC3Tm8pDm /5ROzPJH+A6XIRWMzX4PrCp8YvENUSH7w5zss/fahgHSbLOSWdZPzOR/qFCHe29z HDbqoT1m5J3IJno1fX3Ugyylqqr4t1eI/6+KR28zWEIJlxBCDYc1P4rlK6ZkvWFv 9VD5jhbcHa9cpghDxUsKAVKJ4x5E4Z29J17nnS27zp6FIksEyQPnhLv8ty5banKw fB+6T7vdd5RI5OC7Mzr71Rq4c3FDNg== =oVic -----END PGP SIGNATURE----- --=-=-=--