Required by restic-rest-server; see following commit.
* gnu/packages/golang.scm (go-github-com-coreos-go-systemd-activation):
New variable.
Signed-off-by: Leo Famulari <leo@famulari.name>
These packages are needed by syncthing and the new restic-rest-server package,
so put them in (gnu packages golang) instead.
* gnu/packages/syncthing.scm (go-github-com-prometheus-common,
go-github-com-prometheus-procfs, go-github-com-prometheus-client-golang):
Move variables ...
* gnu/packages/golang.scm (go-github-com-prometheus-common,
go-github-com-prometheus-procfs, go-github-com-prometheus-client-golang):
... to here.
Signed-off-by: Leo Famulari <leo@famulari.name>
Fix for the broken build on master.
* gnu/packages/fonts.scm (font-amiri): Update to 1.000.
[arguments](%standard-phases): Add 'patch-source' to hard-code version.
Signed-off-by: Nicolas Goaziou <mail@nicolasgoaziou.fr>
* gnu/packages/web.scm (wabt): Update to 1.0.32.
[source]: Fetch sources recursively; delete bundled gtest sources.
[arguments]: Do build and run tests; add phase to set CC variable, and another
phase to delete a broken test.
[native-inputs]: Add python and googletest.
[inputs]: Remove.
The timezone database should not be depended on by packages, but rather found at
runtime in the environment. Otherwise, this package will eventually report the
incorrect time, because time zones change regularly.
This reverts commit 99c1c7a30c.
Add a new 'proxy' field to openssh-host to allow ProxyCommand or
ProxyJump, but not both, to be configured. Configuring both would cause
the serialization order to determine which one is used. Deprecate the
'proxy-command' field because the 'proxy' field replaces it.
* gnu/home/services/ssh.scm (proxy-jump->string,
proxy-command-or-jump-list?, serialize-proxy-command-or-jump-list,
sanitize-proxy-command): New procedure.
(proxy-jump, proxy-command): New record type.
(openssh-host)[proxy-command]: Mark field as deprecated because OpenSSH
can't have ProxyCommand and ProxyJump configured at the same time.
* doc/guix.texi (Secure Shell): Update to match the changes to the
service.
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
Previously 'package-direct-sources' would trigger a wrong-type-arg error
when passed a package whose 'source' is not an origin, such as
'ruby-sorbet-runtime'.
* guix/packages.scm (package-direct-sources): Call 'expand' if and only
if (package-source package) is an origin.
* tests/guix-package-aliases.sh: "guix upgrade foo bar" has always
returned zero; adjust accordingly.
* tests/guix-refresh.sh: "guix refresh -t test idutils" and similar
return zero; adjust accordingly.
Addresses <https://issues.guix.gnu.org/62406>.
With 'set -e', a return status inverted with '!' does not cause the shell to
exit immediately. Instead use '&& false' to indicate an expected failure.
* tests/guix-archive.sh, tests/guix-build-branch.sh, tests/guix-build.sh,
tests/guix-daemon.sh, tests/guix-download.sh,
tests/guix-environment-container.sh, tests/guix-environment.sh,
tests/guix-gc.sh, tests/guix-git-authenticate.sh, tests/guix-graph.sh,
tests/guix-hash.sh, tests/guix-home.sh, tests/guix-pack-relocatable.sh,
tests/guix-pack.sh, tests/guix-package-aliases.sh, tests/guix-package-net.sh,
tests/guix-package.sh, tests/guix-refresh.sh, tests/guix-shell.sh,
tests/guix-style.sh, tests/guix-system.sh: Replace uses of '! ...' with
'... && false' or `test ! ...` as appropriate.
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
By merely forking PID 1, details from PID 1 (shepherd) would leak into
the marionette process, such as the set of modules in scope and state
inherited from the shepherd process (<service> instances, fibers,
etc.). Running a fresh Guile instance avoids that.
* gnu/tests.scm (marionette-program): New procedure.
(marionette-shepherd-service): Change 'start' to use
'make-forkexec-constructor', and run the result of 'marionette-program'.
The previous code worked "by chance": 'start' from (shepherd service)
happened to be in scope because the marionette REPL is created by a mere
'primitive-fork', and 'start' happened to kinda work.
* gnu/tests/base.scm (run-basic-test): Use 'start-service' from (gnu
services herd), not 'start' from (shepherd service), which is not
supposed to work.
* gnu/tests/install.scm (run-install): Likewise.
Nicolas Graves