jiebi/CodeConvo huggingface dataset:
Change:
running nix-shell . with that sets enableCuda to true causes opencv to fail building with impure path `' used in link collect2: error: ld returned 1 exit status nix-shell . System: (NixOS: , Ubuntu/Fedora: , ...) Centos 7 10.0-327.22.2.el7.x8664 Nix version: (run ) nix-env (Nix) 1.11.4 Nixpkgs version: (run ) 03pre97542.
I forgot to mention that I had to add this file { allowUnfree = true; }
I also encountered the exact same problem on Arch Linux. I would guess causes problem, because Arch Linux also have and opencv's cmake detects it.
Status? No matter how I run or modify opencv always finds and fails
cc opencv maintainers Maybe patch opencv's CMakeLists to stop it from using libraries in /lib/ is a possible solution?

Discussion:
ln -s "${bootdescFiles}/$name" "$NIX_BUILD_TOP/opencv_contrib/xfeatures2d/src/$name" done ''); <ins> # This prevents cmake from using libraries in impure paths (which causes build failure on non NixOS) postPatch = '' sed -i '/Add these standard paths to the search paths for FIND_LIBRARY/,/^s*$/{d}' CMakeLists.txt ''; </ins> preConfigure = (let version  = "20151201"; md5      = "808b791a6eac9ed78d32a7666804320e";

./no-build-info.patch ]; <ins> # This prevents cmake from using libraries in impure paths (which causes build failure on non NixOS) postPatch = '' sed -i '/Add these standard paths to the search paths for FIND_LIBRARY/,/^s*$/{d}' CMakeLists.txt ''; </ins> outputs = [ "out" "dev" ]; buildInputs =
Change:
What I expected: I installed vimconfigurable and I should have expected python to work arrording shlevy it is on by default. What I got: What I got was pythong did not work either :python print "hi" or plugins that needed python. What I expected: After getting python working by adding ; to I expected removing ; would remove vim's access to python after nix-env -i vimconfigurable. What I got: Vim still had access to python. The step below demonstrate the above and an additional difference between my nixos 1.1pre2714... and nix 1.1 on ubuntu. Nixpkgs "remembers" ; after it is removed form Reproduced in NixOS on VMware and nix on Ubuntu: Each invocation of vim happens in a new shell created after the nix-env install is finished. nix-env -i vimconfigurable.  Vim can not access python test by :python print "Hi" in vim. Should result in error. Add ; to nix-env -i vimconfigurable.  Vim can now access python test by :python print "Hi" in vim. nix-env -e vimconfigurable. Remove ; in nix-env -i vimconfigurable  Vim can still access python test by :python print "Hi" in vim. Add ; to nix-env -i vimconfigurable.  Vim can not access python test by :python print "Hi" in vim. -"Sorry, the command is not available in this version remove ; in nix-env -i vimconfigurable.  :python print "Hi" in vim. -(ubuntu nix 1.0: vim crashes and gives error report) (nixos 1.1pre27142f3f413: vim has acces to python) Add ; to nix-env -i vimconfigurable.  :python print "Hi" in vim. -(ubuntu nix 1.0: vim crashes and gives error report) (nixos 1.1pre2714_2f3f413: vim has acces to python) There is some some state that is saved in-between installs which seems undesirable.
There's something strange happening here, but I don't think it's due to (and it's definitely not due to nixpkgs config being saved somewhere). has: , which means that if is not set it defaults to true. Perhaps vim_configurable needs some other flag for python support to be on? ? I'll try to reproduce this later.
I will document here as I did on irc that I could not get my test of :python print "hi", or a pandoc extension that called on python, to work before either adding "python" to the flags in all-packages or setting ; in on nixos 1.1pre2714... or on my ubuntu nix 1.1 install.
Do I remember correctly that we resolved this?
The symptom has been resolved with this merge: There is still probably an under lying problem/issue. I don't know if it is worth keeping open though. , Shea Levy wrote:

Discussion:
, libaio }: stdenv.mkDerivation rec { <del> name = "sysbench-1.0.14"; </del> <ins> name = "sysbench-1.0.15"; </ins> nativeBuildInputs = [ autoreconfHook pkgconfig ]; buildInputs = [ vim mysql.connector-c libaio ];

src = fetchFromGitHub { owner = "akopytov"; repo = "sysbench"; <del> rev = "1.0.14"; sha256 = "0mp1wqdm87zqyn55z23qf1izqz7ijgcbsysdwqndd98w6m5d86rp"; </del> <ins> rev = "1.0.15"; sha256 = "0ddj4mxxqlnlp817ix2qad0v3p83azi9wyz4h7mffchgp3mndp9z"; </ins> }; meta = {
Change:
Despite being referenced by the aria2c path patching step, xivlauncher's closure (as seen by running ) does not contain aria2, allowing it to be garbage collected if nothing else on the system requires it, breaking patch downloads if that happens. Steps to reproduce the behavior: xivlauncher into a profile. that patch downloads work. garbage collect the store, or wait until after an automatic collection. downloads now fail with an "path not found" error for aria2c. Workaround: Install aria2c to a profile explicitly, to ensure that it has a GC root. (ping per bug template instructions)
(My gut instinct here is that the process of compiling to CLR is, as an unintentional side effect, obfuscating the path enough that nix doesn't pick up on it, but I'm not sure how I'd go about verifying that, nor how to get nix to pick up the path anyway.)
argh, that's annoying. fixing the missing dependency should be fairly easy – you need to make a file as part of the xivlauncher build that contains the path to aria2c as ASCII/UTF-8 so that nix will see it. there's an idiomatic way to do this (ending up with a file under ), but I can't remember the details; if you feel like looking into it, feel free to open a PR, else I'll try to get around to it at some point.
ok, seems like maybe there is not actually an idiomatic way to do it...

Discussion:
--replace 'exec' 'exec ${steam-run}/bin/steam-run' '' + '' wrapProgram $out/bin/XIVLauncher.Core --prefix GST_PLUGIN_SYSTEM_PATH_1_0 ":" "$GST_PLUGIN_SYSTEM_PATH_1_0" <ins> # the reference to aria2 gets mangled as UTF-16LE and isn't detectable by nix: https://github.com/NixOS/nixpkgs/issues/220065 mkdir -p $out/nix-support echo ${aria2} >> $out/nix-support/depends </ins> ''; executables = [ "XIVLauncher.Core" ];
Change:
Steps to reproduce the behavior: a system configuration with plausible as a service (I'm on NixOS 22.11) I'm new to Nix, so I can't make the changes myself, but I've analyzed the issue and have found the problem. The issue is that when the package was made, nodejs included an older npm version (<9) which still had the command. This has been removed in newer nodejs versions however. This causes an error, because is used in the repository of plausible (atleast for the version that is pinned here). It can either be fixed by using an older nodejs package, using a newer version of the plausible repository or not using the deploy script from the repository and instead calling webpack manually using npm exec. Unfortunately, there are currently no maintainers. was originally a maintainer, but has removed himself. Please run and paste the result.
I'd be willing to help here in some capacity, but as I've said I'm new to Nix, so I would atleast need some guidance. I feel there are two ways of going forward here: either updating the package to not use while still pinning the same underlying version of plausible OR updating the package to use a newer version of plausible, which would mitigate the issue. With the first solution, I'm not sure what would happen with the version number. Would it stay the same, basically applying a fix for the already released version so it works again? Or would the version be incremented to something else (1.4.4.2?) to reflect the change, with the already published version remaining in a broken state? It would be helpful if someone with more experience could comment on this topic, or atleast point me in the right direction. I saw some stuff in the docs about backporting, but I'm not sure if this applies here.
can you test
Hey, thank you for working on this. Unfortunately, it does not seem to be working for me. Behaviour is as before. I ran on your branch.
can you provide exact commands you used to get right version of nixpkgs, including full command for nixos-rebuild
Sure. My config for plausible looks like this:
there is a typo should be
Ahh, sorry. With the correct command the build works now. Thank you. I'm still getting another error when the unit is actually started, but it seems unrelated and probably has something to do with my config.
were you successful at starting plausible ? if so could you share your configuration ?

Discussion:
nativeBuildInputs = [ nodejs ]; <ins> # https://github.com/whitfin/cachex/issues/205 stripDebug = false; </ins> passthru = { tests = { inherit (nixosTests) plausible; }; updateScript = ./update.sh; }; postBuild = '' <ins> export HOME=$TMPDIR </ins> export NODE_OPTIONS=--openssl-legacy-provider # required for webpack compatibility with OpenSSL 3 (https://github.com/webpack/webpack/issues/14532) ln -sf ${yarnDeps}/node_modules assets/node_modules npm run deploy --prefix ./assets

play-with-mpv = callPackage ../tools/video/play-with-mpv { }; <del> plausible = callPackage ../servers/web-apps/plausible { }; </del> <ins> plausible = callPackage ../servers/web-apps/plausible { nodejs = nodejs-16_x; }; </ins> pam-reattach = callPackage ../os-specific/darwin/pam-reattach { };
Change:
When Neovim and associated vim plugins are installed, the help docs for some of the plugins is missing Steps to reproduce the behavior: Neovim and plugins Neovim and try to pull up help for the listed plugins. Help is missing when trying to pull them up using for these plugins Help is available for all the plugins. If applicable, add screenshots to help explain your problem. I have verified that the plugins are loaded using command Please run and paste the result.
I think this is an issue specific to neovim plugins from luarocks-packages, cc
doc is generated via the maybe it's missing from the close (should be though) or it doesn't work as expected. Feel free to have a look, else I will have a look when I've time. I've noticed it too. Note to myself: vim plugins depend on vim and neovim because of so maybe we should address that too
and do not have documentation, so there is no issue there. However, should have it, but it doesn't. I looked at other plugins using luarocks packages and noticed that there are 3 that are missing in their rockspec: However, this does not fully solve the issue since on the side the documentation tags are still missing. For instance, has a correct rockspec which includes the folder, but the documentation tags are still not generated: The relevant error is here: It seems that looks for $out/doc, but at the moment it is run in a luarocks plugin, the structure is as follows: Seems that should happen before but the former is in and the latter is in . Alternatively, looking at , maybe we could override the substitution so that it points to inside the rocks.

Discussion:
''; }); <ins> # check that the vim-doc hook correctly generates the tag # for neovim packages from luaPackages # we know for a fact gitsigns-nvim has a doc folder and comes from luaPackages checkForTagsLuaPackages = vimPlugins.gitsigns-nvim.overrideAttrs(oldAttrs: { doInstallCheck = true; installCheckPhase = '' [ -f $out/doc/tags ] ''; }); nvim_with_gitsigns_plugin = neovim.override { extraName = "-with-gitsigns-plugin"; configure.packages.plugins = { start = [ vimPlugins.gitsigns-nvim ]; }; }; checkHelpLuaPackages = runTest nvim_with_gitsigns_plugin '' export HOME=$TMPDIR ${nvim_with_gitsigns_plugin}/bin/nvim -i NONE -c 'help gitsigns' +quitall! -e ''; </ins> # nixpkgs should detect that no wrapping is necessary nvimShouldntWrap = wrapNeovim2 "-should-not-wrap" nvimAutoDisableWrap;

} echo "Using luarocksMoveDataHook" <del> preDistPhases+=" luarocksMoveDataHook" </del> <ins> preFixupHooks+=(luarocksMoveDataHook) </ins>
Change:
nixos-install script calls and but does not depend on them On some systems, nixos-install will fail to find the mount and umount binaries on the system and therefore the install will get in a undesirable state. And the root password will not be prompted to the user. suggested to use Please run and paste the result.
Ah. If we're talking about host system executables, I'm not sure resholve is going to be much help. It'll complain about the missing commands and rewrite them to absolute paths if provided. We'd either have to prebuild for different systems or bring resholve to the system. If the problem is just weird/inconsistent user paths, and if and are in ~normal locations, using to discover and set the ~normal system PATH may help?
nixos-install is always installed with Nix, or at least should be, so we can (and should!) make it use Nix provided tools.
if it helps, on host was both in and in , but I think we should not rely on host having/providing
I don't really know, but I at least found two sources that make me think the specific uses of mount/umount here will work without a setuid wrapper: I decided to see how a naive attempt at using resholve would work but stopped when it was obvious that there's some dynamic behavior in the script (stringly-inlining other scripts). resholve won't be able to see through stuff like that without some changes to script source. If you just want to get mount/umount in with minimal effort, I'd just add them to the existing makeBinPath. Note that also appears in nixos-enter. If you're curious, I pushed up my ~starter on resholving it: ()

Discussion:
path = makeBinPath [ pkgs.jq nixos-enter <ins> pkgs.util-linuxMinimal </ins> ]; };

name = "nixos-enter"; src = ./nixos-enter.sh; inherit (pkgs) runtimeShell; <ins> path = makeBinPath [ pkgs.util-linuxMinimal ]; </ins> }; in
Change:
says but in flake mode, it uses , not , and the flag has no effect. I guess this is technically as documented, but a bit surprising. Should it pass to as well?
Is there any workaround for now?

Discussion:
# Parse the command line. origArgs=("$@") <del> copyClosureFlags=() </del> <ins> copyFlags=() </ins> extraBuildFlags=() lockFlags=() flakeFlags=(--extra-experimental-features 'nix-command flakes')

upgrade=1 upgrade_all=1 ;; <del> --use-substitutes|-s) copyClosureFlags+=("$i") </del> <ins> --use-substitutes|--substitute-on-destination|-s) copyFlags+=("-s") </ins> ;; -I|--max-jobs|-j|--cores|--builders|--log-format) j="$1"; shift 1

if ! [ "$targetHost" = "$buildHost" ]; then if [ -z "$targetHost" ]; then logVerbose "Running nix-copy-closure with these NIX_SSHOPTS: $SSHOPTS" <del> NIX_SSHOPTS=$SSHOPTS runCmd nix-copy-closure "${copyClosureFlags[@]}" --from "$buildHost" "$1" </del> <ins> NIX_SSHOPTS=$SSHOPTS runCmd nix-copy-closure "${copyFlags[@]}" --from "$buildHost" "$1" </ins> elif [ -z "$buildHost" ]; then logVerbose "Running nix-copy-closure with these NIX_SSHOPTS: $SSHOPTS" <del> NIX_SSHOPTS=$SSHOPTS runCmd nix-copy-closure "${copyClosureFlags[@]}" --to "$targetHost" "$1" </del> <ins> NIX_SSHOPTS=$SSHOPTS runCmd nix-copy-closure "${copyFlags[@]}" --to "$targetHost" "$1" </ins> else <del> buildHostCmd nix-copy-closure "${copyClosureFlags[@]}" --to "$targetHost" "$1" </del> <ins> buildHostCmd nix-copy-closure "${copyFlags[@]}" --to "$targetHost" "$1" </ins> fi fi }

drv="$(runCmd nix "${flakeFlags[@]}" eval --raw "${attr}.drvPath" "${evalArgs[@]}" "${extraBuildFlags[@]}")" if [ -a "$drv" ]; then logVerbose "Running nix with these NIX_SSHOPTS: $SSHOPTS" <del> NIX_SSHOPTS=$SSHOPTS runCmd nix "${flakeFlags[@]}" copy --derivation --to "ssh://$buildHost" "$drv" </del> <ins> NIX_SSHOPTS=$SSHOPTS runCmd nix "${flakeFlags[@]}" copy "${copyFlags[@]}" --derivation --to "ssh://$buildHost" "$drv" </ins> buildHostCmd nix-store -r "$drv" "${buildArgs[@]}" else log "nix eval failed"

if [ -a "$nixDrv" ]; then nix-store -r "$nixDrv"'!'"out" --add-root "$tmpDir/nix" --indirect >/dev/null if [ -n "$buildHost" ]; then <del> nix-copy-closure "${copyClosureFlags[@]}" --to "$buildHost" "$nixDrv" </del> <ins> nix-copy-closure "${copyFlags[@]}" --to "$buildHost" "$nixDrv" </ins> # The nix build produces multiple outputs, we add them all to the remote path for p in $(buildHostCmd nix-store -r "$(readlink "$nixDrv")" "${buildArgs[@]}"); do remoteNix="$remoteNix${remoteNix:+:}$p/bin"
Change:
As proposed in , should switch to because invoking is manual and can easily cause breakages if files are missed. This is a followup from <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

Discussion:
, backendStdenv , fetchFromGitHub , which <del> , cudaPackages ? { } , addOpenGLRunpath </del> <ins> , autoAddOpenGLRunpathHook , cuda_cccl , cuda_cudart , cuda_nvcc , cudaFlags , cudaVersion </ins> }: <del> with cudaPackages; </del> let # Output looks like "-gencode=arch=compute_86,code=sm_86 -gencode=arch=compute_86,code=compute_86" gencode = lib.concatStringsSep " " cudaFlags.gencode; in <del> backendStdenv.mkDerivation rec { name = "nccl-${version}-cuda-${cudaPackages.cudaMajorVersion}"; </del> <ins> backendStdenv.mkDerivation (finalAttrs: { name = "nccl-${finalAttrs.version}-cuda-${cudaVersion}"; </ins> version = "2.16.5-1"; src = fetchFromGitHub { owner = "NVIDIA"; repo = "nccl"; <del> rev = "v${version}"; </del> <ins> rev = "v${finalAttrs.version}"; </ins> hash = "sha256-JyhhYKSVIqUKIbC1rCJozPT1IrIyRLGrTjdPjJqsYaU="; };

nativeBuildInputs = [ which <del> addOpenGLRunpath </del> <ins> autoAddOpenGLRunpathHook </ins> cuda_nvcc ]; buildInputs = [ cuda_cudart <del> ] ++ lib.optionals (lib.versionAtLeast cudaVersion "12.0.0") [ </del> <ins> ] # NOTE: CUDA versions in Nixpkgs only use a major and minor version. When we do comparisons # against other version, like below, it's important that we use the same format. Otherwise, # we'll get incorrect results. # For example, lib.versionAtLeast "12.0" "12.0.0" == false. ++ lib.optionals (lib.versionAtLeast cudaVersion "12.0") [ </ins> cuda_cccl ];

makeFlags = [ "CUDA_HOME=${cuda_nvcc}" <del> "CUDA_LIB=${cuda_cudart}/lib64" "CUDA_INC=${cuda_cudart}/include" </del> <ins> "CUDA_LIB=${lib.getLib cuda_cudart}/lib" "CUDA_INC=${lib.getDev cuda_cudart}/include" </ins> "PREFIX=$(out)" ]; postFixup = '' moveToOutput lib/libnccl_static.a $dev <del> # Set RUNPATH so that libnvidia-ml in /run/opengl-driver(-32)/lib can be found. # See the explanation in addOpenGLRunpath. addOpenGLRunpath $out/lib/lib*.so </del> ''; env.NIX_CFLAGS_COMPILE = toString [ "-Wno-unused-function" ]; enableParallelBuilding = true; <del> passthru = { inherit cudaPackages; }; </del> meta = with lib; { description = "Multi-GPU and multi-node collective communication primitives for NVIDIA GPUs"; homepage = "https://developer.nvidia.com/nccl";

platforms = [ "x86_64-linux" ]; maintainers = with maintainers; [ mdaiter orivej ]; }; <del> } </del> <ins> }) </ins>
Change:
Currently, there are two almost identical packages for in nixpkgs. They were merged in CC

Discussion:
<del> { lib, stdenv, buildFishPlugin, fetchFromGitHub }: buildFishPlugin rec { pname = "autopair.fish"; version = "1.0.4"; src = fetchFromGitHub { owner = "jorgebucaran"; repo = pname; rev = version; sha256 = "sha256-s1o188TlwpUQEN3X5MxUlD/2CFCpEkWu83U9O+wg3VU="; }; meta = with lib; { description = "Auto-complete matching pairs in the Fish command line."; homepage = "https://github.com/jorgebucaran/autopair.fish"; license = licenses.mit; maintainers = with maintainers; [ thehedgeh0g ]; }; } </del>

buildFishPlugin rec { pname = "autopair"; <del> version = "1.0.3"; </del> <ins> version = "1.0.4"; </ins> src = fetchFromGitHub { owner = "jorgebucaran"; repo = "autopair.fish"; rev = version; <del> sha256 = "sha256-l6WJ2kjDO/TnU9FSigjxk5xFp90xl68gDfggkE/wrlM="; </del> <ins> sha256 = "sha256-s1o188TlwpUQEN3X5MxUlD/2CFCpEkWu83U9O+wg3VU="; </ins> }; meta = with lib; { description = "Auto-complete matching pairs in the Fish command line"; homepage = "https://github.com/jorgebucaran/autopair.fish"; license = licenses.mit; <del> maintainers = with maintainers; [ kidonng ]; </del> <ins> maintainers = with maintainers; [ figsoda kidonng thehedgeh0g ]; </ins> }; }

<del> { lib, newScope }: </del> <ins> { lib, newScope, config }: </ins> lib.makeScope newScope (self: with self; { autopair = callPackage ./autopair.nix { }; <del> autopair-fish = callPackage ./autopair-fish.nix { }; </del> buildFishPlugin = callPackage ./build-fish-plugin.nix { }; colored-man-pages = callPackage ./colored-man-pages.nix { };

sponge = callPackage ./sponge.nix { }; tide = callPackage ./tide.nix { }; <ins> } // lib.optionalAttrs config.allowAliases { autopair-fish = self.autopair; # Added 2023-03-10 </ins> })
Change:
IHaskell is not GHC 8 compatible, and so it doesn't build on 16.09 onwards. Instead I get this error: System: 16.09.1512. (Flounder) Nix version: nix-env (Nix) 1.11.6 Nixpkgs version: 16.09.1512.
Thanks for filing an issue! I see you already filed the GHC 8 incompatibility upstream. You could try the following patch: but it'll require re-building substantial amounts of old code that are no longer being build by hydra. If it works we can apply the patch, otherwise I think I'd vote for removing the package. What do you think?
After applying your patch, I'm getting an error building (). Is there an easy workaround for this? I'm hopeful that IHaskell will gain GHC 8 compatibility in the near term, so I'd rather not remove the package :smile:
Reading I doubt there is. In order to save other people time maybe we should at least add an assert with an informative message and a link to this bug so other people won't lose time trying to install ihaskell?
Sure, that's a good idea.
I can't see an easy way of disabling ihaskell, so I suggest removal, followed by re-introduction when fixed. - would you be able to own this?
I've created a pull request.
I am experiencing a similar error on current nixos-unstable channel ...

Discussion:
in buildEnv { name = "ihaskell-with-packages"; <del> paths = [ ihaskellEnv ipython (abort "ihaskell is currently broken. See https://github.com/NixOS/nixpkgs/issues/22047.")]; </del> <ins> paths = [ ihaskellEnv ipython ]; </ins> postBuild = '' . "${makeWrapper}/nix-support/setup-hook" ln -s ${ihaskellSh}/bin/ihaskell-notebook $out/bin/.
Change:
Project description Enables common unix utlities like cut, awk, wc, head to work correctly with csv data containing delimiters and newlines Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin

Discussion:
<ins> --- a/csvheader +++ b/csvheader @@ -29,10 +29,6 @@ while getopts "d:tq:r:" arg; do esac done -CSVQUOTE=`which csvquote` || CSVQUOTE="./csvquote" -if [ ! -f $CSVQUOTE ]; then -    echo "csvquote program not found. exiting" -    exit 1 -fi +CSVQUOTE=@out@/bin/csvquote $CSVQUOTE $@ | head -n 1 | tr "$DEL" 'n' | nl -ba | $CSVQUOTE -u -d "$DEL" -q "$QUO" -r "$REC" </ins>

<ins> { lib , stdenv , fetchFromGitHub , patsh }: stdenv.mkDerivation rec { pname = "csvquote"; version = "0.1.5"; src = fetchFromGitHub { owner = "dbro"; repo = "csvquote"; rev = "v${version}"; hash = "sha256-847JAoDEfA9K4LB8z9cqSw+GTImqmITBylB/4odLDb0="; }; patches = [ # patch csvheader to use csvquote from the derivation ./csvquote-path.patch ]; nativeBuildInputs = [ patsh ]; makeFlags = [ "BINDIR=$(out)/bin" ]; preInstall = '' mkdir -p "$out/bin" ''; postInstall = '' substituteAllInPlace $out/bin/csvheader patsh $out/bin/csvheader -fs ${builtins.storeDir} ''; meta = with lib; { description = "Enables common unix utlities like cut, awk, wc, head to work correctly with csv data containing delimiters and newlines"; homepage = "https://github.com/dbro/csvquote"; license = licenses.mit; maintainers = with maintainers; [ figsoda ]; platforms = platforms.all; }; } </ins>

csvkit = callPackage ../tools/text/csvkit { }; <ins> csvquote = callPackage ../tools/text/csvquote { }; </ins> csvtool = callPackage ../development/ocaml-modules/csv/csvtool.nix { }; csv2latex = callPackage ../tools/misc/csv2latex { };