Because p11-kit appears in the gnutls.pc file, it needs to be a propagated
input.
This was a regression introduced in 28a13226fd
which broke things like HTTPS support in curl, which then broke Git clones
from repositories using HTTPS.
* gnu/packages/tls.scm (gnutls)[inputs]: Move p11-kit from here.
[propagated-inputs]: To here.
Reported by Vagrant Cascadian <vagrant@debian.org>
in <https://bugs.gnu.org/44626>.
* guix/build/utils.scm (wrap-script): Use 'display' instead of passing a
non-literal string to 'format'.
Fixes <https://bugs.gnu.org/25304>.
* gnu/packages/autotools.scm (libtool)[restore-build-aux-shebang]: New
phase after install.
[restore-ltmain-shebang]: Remove phase, it is now performed by the phase
restore-build-aux-shebang.
Because the debug files are read-only, the strip-runpath procedure would throw
an exception when attempting to open them.
* guix/build/meson-build-system.scm (shrink-runpath): Remove "debug" from the
list of outputs to be processed.
* gnu/packages/patches/python-3-configure-hurd.patch: this New file.
* gnu/local.mk (dist_patch_DATA): Add it.
* gnu/packages/python.scm (python-3.8)[source]: Use it.
[arguments]: Remove "support-hurd-cross-compile" stage.
Without the shadow input, configure doesn't find login and sets PATH_LOGIN to a
(wrong) default value, which means that rlogind and telnetd doesn't work.
* gnu/packages/admin.scm (inetutils): Let telnetd and rlogind find login.
[inputs]: Add shadow.
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
Everywhere except mips64el, where a comment says it doesn't work. I can't test
as I can't build this on mips64el anyway.
This change will enable running the tests for libcacard.
* gnu/packages/tls.scm (gnutls)[arguments]: Only specify --without-p11-kit on
mips64el.
[inputs]: Include the p11-kit for all systems except mips64el.
* gnu/packages/python.scm (python-2.7)[phases]{rebuild-bytecode}: Byte compile
using optimization level, -OO. Provide the output directory as the source
argument to 'compileall', instead of looping over each individual source file.
Commit c94a2864d4 moved the 'check' phase back into its original place before
the 'install' phase, but such a change would require adapting the definition
of many Python packages which have come to rely on such phase ordering.
* guix/build/python-build-system.scm (%standard-phases): Move the check phase
back after the install phase, and update comment.
Fixes <https://issues.guix.gnu.org/22129>.
A previously worked around problem where running the test suite after byte
compiling the sources in commit 6bbb37a545 could
be broken by adding built sources to the PYTHONPATH, as is done for
python-matplotlib and many others. This seems to be caused by the timestamps
embedded in the sources (mtime), that can somehow change when running the
tests, or by picking up the different installed source files mtimes when their
location is added to the PYTHONPATH.
Since Python 3.7.0, it is possible to produce .pyc byte code files that do not
embed any timestamp, which solves the problem in a definitive way. This patch
makes use of this new feature.
* guix/build/python-build-system.scm (install): Add '--no-compile' parameter
to setup.py, and instead invoke the 'compileall' module with the
"--invalidation-mode=unchecked-hash" option to byte compile the source files.
(%standard-phases): Revert the workaround that moved the check phase after the
install phase, as it is no longer necessary. Update comment.
Reported-by: Mark H Weaver <mhw@netris.org>
Miguel Ángel Arruga Vivas
Martin Becze
Christopher Baines
Ludovic Courtès
Maxim Cournoyer
Jan (janneke) Nieuwenhuizen
Simon South
Andreas Enge
Michael Rohleder
Marius Bakke
Vinicius Monego
Peng Mei Yu