<Steap>Has anyone found a workaround for "#<gnutls-error-enum The TLS connection was non-properly terminated.> fill_session_record_port_input" which denotes a server-side error when downloading tarballs ?
<Steap>civodul: I get the error when building python-setuptools
<Steap>Isn't it even possible to ignore the error ?
<mark_weaver>well, the error happens within low-level IO routines, while trying to fill an input buffer.
<mark_weaver>afaik, there's no way to ignore it at the scheme level. something probably needs to be changed in the C code.
<mark_weaver>for now, you can use 'wget' to download from the bad server and then use 'guix download file:...' to put it in the store, no?
<mark_weaver>The server really is misbehaving, and it's probably good that GnuTLS is strict about such things by default. The only reason we can safely ignore it is because we really don't need the protection of TLS anyway, since we later check the hash.
<sriharsha>How the macro 'GUIX_ASSERT_LIBGCRYPT_USABLE' from configure.ac work? I have never seen anything like that before in autoconf
<Steap>mark_weaver: I think this will happen for all download on pypi.python.org
<mark_weaver>it uses GUILE_CHECK, which is defined in guile.m4 (normally installed in $PREFIX/share/aclocal/guile.m4)
<Steap>Is there a way to show this error so that a bug report can be submitted to the people at PyPI ?
<sriharsha>mark_weaver, true; I allmost forgot we can do custom m4; the ones from autoconf were sufficient, until now :)
<mark_weaver>Steap: pypi.python.org is extremely broken. even 'wget' won't download from it, at least not on my system, because the certificate common name ("*.a.ssl.fastly.net") doesn't match the host name. that's just totally broken.
<mark_weaver>I have to completely disable all certificate checks to download from that site at all.
<mark_weaver>sriharsha: custom autoconf tests are needed fairly regularly, in practice. in fact, there's a whole project "autoconf-archive" aimed toward helping with that.
<Steap>mark_weaver: that's gonna be an issue for most Python packages, though
<mark_weaver>davexunit: btw, I just pushed a patch to stable-2.0 that changes repl/server.scm a bit. it doesn't directly affect your coop-repl, but it's probably close enough to cause a merge conflict.
<mark_weaver>ah, of course. shoot texinfo in the head. sounds like something esr would say, since he's also into guns :)