<Apteryx>substitute* also chokes and dies on it with a "string contains #\\nul character:".
<Apteryx>I think I know where to fix it. I must skip lines containing #\\nul characters in the `substitute' procedure of (guix build utils).
<marusich>pkill9, at the level of derivations, there are only "inputs", which are things that might be required to build the derivation (the intent is that they are precisely the things required, but you can over-specify and the build can still succeed).
<marusich>In addition, any references that are "retained" by the output of the derivation are things that might be required for running the software that was built.
<marusich>At the level of packages, there are more concepts: inputs and native-inputs. These are multiple layers above the derivation level of abstraction. Ultimately they will be translated into inputs - just inputs - of some derivation or derivations.
<marusich>I believe those - inputs vs. native inputs - matter only when cross-compiling. The distinction only matters for the higher-level machinery in Guix which is responsible for execuitng the cross compilation. That machinery implements the cross-compilation in terms of the lower-level concepts of derivations and their (the derivations') inputs.
<marusich>That is my understanding, although I might be wrong. It wouldn't be the first time.
<t0167641>i have already read this doc but doesn't understand how to use it. then i have use the guix build -f command
<nee`>t0167641: where did you save your package definition? If you wrote it to a file you can use `guix package -f`. Alternatively you can add the directory with your package definitions to the GUIX_PACKAGE_PATH env variable. If you are using the guix git repository user `./pre-install-env guix package -i`
<roptat>I found an issue with claws-mail: when you update it, it still fetches its plugins in the old version (its configuration file references the store), so after a guix gc, the plugins disappear and I get an error message
<roptat>also that means the old version is still in use until the next guix gc, which is bad (compatibility, vulnerability...)
<roptat>should I report it to bug-guix even though I don't think there's a solution?
<civodul>rekado_: we could do nifty things by integrating guile-debbugs + guile-git + guix pull
<civodul>like displaying a list of fixed security vulnerabilities
<groffer>I'm using gnu-build-system but the generated Makefile does not contain a usable "install:" target. Should I just "(modify-phases %standard-phases ..." and "(replace 'install ..." with "(system* "install" "-m" "555" "-o" "root" "-g" "root" ...)" or is there some guix-way to copy the executable (which is only linked to /gnu/store/... libs and linux-vdso.so.1)?