Until now, using any package transformation would disable the automatic
GC root creation and caching in ‘guix shell’. This change introduces a
finer-grain distinction: a command like:
guix shell --tune inkscape
is now subject to caching, whereas:
guix shell --with-latest=inkscape inkscape
remains non-cacheable.
* guix/transformations.scm (%transformations-with-external-dependencies):
New variable.
(cacheable-transformation-option-key?): New procedure.
* guix/scripts/shell.scm (profile-cached-gc-root): In the
‘transformation-option-key?’ clause, call ‘loop’ when
‘cacheable-transformation-option-key?’ returns true.
Change-Id: I847b661dfea20ecf851db2023a5c7ea8c5b5ca7c
As seen in python-team build
<https://ci.guix.gnu.org/build/6091717/log/raw>.
* gnu/packages/python-xyz.scm (python-lazy-loader) [native-inputs]: Add
python-setuptools.
Change-Id: Id8c4eb18f0d2622a1d3270ad29653ef27dcd2fe3
As seen in python-team build
<https://ci.guix.gnu.org/build/6091629/log/raw>.
* gnu/packages/python-xyz.scm (python-mpv) [native-inputs]: Add
python-setuptools.
Change-Id: I3a43904057c2b3f77833372e2be68280f95189a2
As seen in python-team build
<https://ci.guix.gnu.org/build/6099416/log/raw>.
* gnu/packages/game-development.scm (python-sge): Adjust inputs.
[arguments]<#:tests>: Disable as they are not provided.
[native-inputs]: Add python-setuptools.
Change-Id: I46a83e8ebb0b25ff7d3895334bef257ce98da20f
There is currently a window of time between when the build outputs are exposed
and when their metadata is canonicalized.
* nix/libstore/build.cc (DerivationGoal::registerOutputs): wait until after
metadata canonicalization to move successful build outputs to the store.
Change-Id: Ia995136f3f965eaf7b0e1d92af964b816f3fb276
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
The only thing keeping a rogue builder and a local user from collaborating to
usurp control over the builder's user during the build is the fact that
whatever files the builder may produce are not accessible to any other users
yet. If we're going to make them accessible, we should probably do some
sanity checking to ensure that sort of collaborating can't happen.
Currently this isn't happening when failed build outputs are moved from the
chroot as an aid to debugging.
* nix/libstore/build.cc (secureFilePerms): new function.
(DerivationGoal::buildDone): use it.
Change-Id: I9dce1e3d8813b31cabd87a0e3219bf9830d8be96
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
This fixes CVE-2023-25149.
* gnu/packages/databases.scm (timescaledb): Update to 2.16.1.
[arguments]<#:phases>: Remove comment and symlink trick in
'prepare-tests phase.
* gnu/packages/fpga.scm (iverilog): Update to 12.0.
[source]: Switch to git-fetch.
[arguments]: Use G-expressions.
Set #:bootstrap-scripts to #~(list "autoconf.sh").
Set #:test-target to "check".
[home-page]: Update to new home page.
[native-inputs]: Add autoconf, gperf, remove ghostscript and zlib.
Change-Id: I55c3142aa41b190fef79572576cac6fc02473645
* doc/guix.texi (Miscellaneous Services)[DLNA/UPnP Services]: Use string value
"60" instead of numeric value 60 in extra-config.
Change-Id: Iea05409bb2f36fc4d0caafa375f0307bfae64a08
* gnu/packages/language.scm (libchewing): Update to 0.9.0.
[build-system]: Switch to cargo-build-system.
[arguments]: Adjust for switch to cargo-build-system. Enable
parallel-tests. Add a phase to allow older versions of
rust-clap-mangen. Add the cmake version of 'configure after 'configure.
Use the cmake versions of 'build, 'check and 'install.
[native-inputs]: Add corrosion, cmake-minimal. Remove autoconf,
automake, libtool, perl, pkg-config, python-wrapper, texinfo.
Co-authored-by: Charles <charles@charje.net>
Change-Id: Ic11e38646fc47cfc2c575320f43b9355a1c83b39
Signed-off-by: jgart <jgart@dismail.de>
* guix/upstream.scm (%updaters): Ensure the updaters with a name starting by
'generic' appear last in the list.
Fixes: <https://issues.guix.gnu.org/73508>
Change-Id: I98977f6c925c14303273755b5b4dc36035f78bda
