From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:32972) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gvwda-000438-Gt for guix-patches@gnu.org; Mon, 18 Feb 2019 23:04:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gvwdZ-0002W1-CV for guix-patches@gnu.org; Mon, 18 Feb 2019 23:04:06 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:54403) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gvwdW-0002V0-CJ for guix-patches@gnu.org; Mon, 18 Feb 2019 23:04:04 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gvwdW-0007iu-4m for guix-patches@gnu.org; Mon, 18 Feb 2019 23:04:02 -0500 Subject: [bug#34515] [PATCH 09/13] gnu: Add python-txtorcon. Resent-Message-ID: Date: Mon, 18 Feb 2019 23:03:06 -0500 From: Leo Famulari Message-ID: <20190219040306.GC2718@jasmine.lan> References: <2518dc3323426f31209dcc5f2a53539baad32058.1550437064.git.leo@famulari.name> <87y36dwlik.fsf@elephly.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0lnxQi9hkpPO77W3" Content-Disposition: inline In-Reply-To: <87y36dwlik.fsf@elephly.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ricardo Wurmus Cc: 34515@debbugs.gnu.org --0lnxQi9hkpPO77W3 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 18, 2019 at 09:25:55AM +0100, Ricardo Wurmus wrote: > Leo Famulari writes: > > * gnu/packages/python-crypto.scm (python-txtorcon): New variable. > [=E2=80=A6] > > + (arguments > > + `(#:tests? #f)) ; fail silently >=20 > Could you please elaborate on this? Do all tests fail? Would it make > sense to disable the broken tests? Are test failures known to upstream? Basically, the first test that runs looks for a file 'release-announce-test' in the root of the tarball. This file does not exist in the PyPi or GitHub releases (they are identical). I checked several releases going back to December 2015, and none of them contain this file, so I'm not sure what's going on. Reported upstream at . I'll add a comment explaining this. Also, while skimming some other tests I began to suspect they require internet access, although I'm not sure. --0lnxQi9hkpPO77W3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlxrf/cACgkQJkb6MLrK fwiIJw//fXNaGL14KatUhB6CKctRBHZRfTWXhOt4BcnxV0ypGosVxBW9wr5gVZeL qaddVwh9iJPJFr9rFjucAuKS/zmP+xaAhov96ZbjvJXTkCRWNRYfiCAQQ08ER1yl s/vv3VIWeS7vLHGmuQY/VSIMEDnuqfMfP9YEJDv93rZDJpDn2C8pO6TKLK55Xe6E Vkwf4/CV9y/IGLpKpDfFvGOoJj7vZNrhtDLm3cwz0Q5CKZRrNwudYsIBJxMJDkDK /z19OD4BVx2i7OZc3rHJEA2jxSs/1ehc2dCUuzYpzFGDEndv9ILHWGO/Oe6+kHVL fiWL/HnjQpDWxG83m/gqf+Vzj3K66KmTJ/Kkp18aTDyiRndM/HzzUQ22U/nKYQ60 PXWnBPpkQfh2ZilqRkoHm69zQNs0erAvdYYn+/EGU3l01HMcPMlHLCnlCfDkg4w8 Hr5vxo8jqb+MSOLj4WMs8fxH0PyMFkC/WjFZnq2dfBjQQRm7HcQC5Oc0AbU21dy2 OsAlqtHv1NdBGONxyHBpHvk203nvUOUhUZ9MS3oXzB5QzVRLXrFlM4ATBJybG8tV pHWULA8GEf04Vtr9f81+jSscRVSKITsJ484EFCGmr+AJRzl/MTrEAV+NIA+B4Mzq tivoCtOONxdMCwYG7TNRfJoIxzzqXkhRpyZEMHvWhVM8+zTmLIU= =z84W -----END PGP SIGNATURE----- --0lnxQi9hkpPO77W3--