Conversation
|
jq 1.7rc2 introduces a cycle between outputs and I'm not sure how to resolve it.
|
Would break many builds because dev is the default output chosen.
This would be good.
By removing |
Done that. |
|
Nice that you are already onto this! 🎉 Unfortunately when I apply this patch I am running into a test failure. For anyone else also running into this, this seems to be tracked here: jqlang/jq#2885 |
|
Tests are passing for me (and for ofborg) on x86_64-linux, aarch64-linux and aarch64-darwin. Are you on x86_64-darwin? What revision did you apply this patch to? |
Interesting... No x86_64-linux (i.e. NixOS)
Current nixos-unstable (0bffda1). Only other two commits in my fork are unrelated (they add two options to
Nope, just a normal |
Well then the sandbox should be enabled by default. Please ensure that your |
|
Can you paste the |
It does
Oh... Damn... I only saw the error with jq, but in fact it is from python3.10-yq: /nix/store/y0nkkmhxhc3fkhc3q0wwqjm0ks8lqh08-python3.10-yq-3.2.2.drvDerive([("dist","/nix/store/4g45xi9866myvha3vxq8yahm29gxpsga-python3.10-yq-3.2.2-dist","",""),("out","/nix/store/64lyjyh5q39akgwcd71yj53yaw4i15k4-python3.10-yq-3.2.2","","")],[("/nix/store/02kq0w1zn1v9qzvanz1gvsds6vf1kkh6-python3.10-argcomplete-3.1.1.drv",["out"]),("/nix/store/0sawbbskl41aq4ii9kl5w77r4m92das8-bash-5.2-p15.drv",["out"]),("/nix/store/1ybxfm6v8ijnr72wm1fx4d3ry59256sr-pypa-install-hook.drv",["out"]),("/nix/store/4lky73gnpd3k90hlhlybik83hv5b12a4-python-remove-tests-dir-hook.drv",["out"]),("/nix/store/599xrhrkyx743jz8lsqjmhhjynswr87f-python3.10-xmltodict-0.13.0.drv",["out"]),("/nix/store/7miy4j2xy6p97f34savhl0jsgy5syf0b-python-catch-conflicts-hook.drv",["out"]),("/nix/store/9663sml6h17kv61wg8am9dmpvfccwrq3-setuptools-check-hook.drv",["out"]),("/nix/store/9fwlz0myh3lwwmj3rcic4ssv7ygrig6x-stdenv-linux.drv",["out"]),("/nix/store/9r57db02g9pvj2fl914m5y9xjma26zr5-pytest-check-hook.drv",["out"]),("/nix/store/9zjcxviqkl4mr6wsvs9554w5ywnr3fas-python3.10-setuptools-scm-7.1.0.drv",["out"]),("/nix/store/bcchpqhqph735wvgkvnf3bc6mzfwjj8g-python3.10-tomlkit-0.12.1.drv",["out"]),("/nix/store/hw5ygglyq53qzx75gdv01wh8qnmd66hq-wrap-python-hook.drv",["out"]),("/nix/store/l0kin7jf2qm401vzqrlrd2cb7zz1x8ah-jq-path.patch.drv",["out"]),("/nix/store/mpaa4mcp8zvhxc5mg10cwmnmhqkzvlak-python-imports-check-hook.sh.drv",["out"]),("/nix/store/mv79m4vxlqrjsasnwf2j9gaa256vyi6h-python3-3.10.12.drv",["out"]),("/nix/store/mx50p8hbrwg9xiimaanmyg7yyq6szdpf-python3.10-pyyaml-6.0.1.drv",["out"]),("/nix/store/n66c5lb52caw80dcyacp2c61bz88vk46-python-remove-bin-bytecode-hook.drv",["out"]),("/nix/store/pqmn7mhg2fz0dz58a7h1sxbd4vvgznv1-ensure-newer-sources-hook.drv",["out"]),("/nix/store/s894x9568fhi765589235am0yjnw2m00-yq-3.2.2.tar.gz.drv",["out"]),("/nix/store/vbhxxiq5ylm82qdpds92ybjpv7hbmc9c-python-namespaces-hook.sh.drv",["out"]),("/nix/store/yav55g1lzz5smcm6lfvjkiczaacx80gz-setuptools-setup-hook.drv",["out"]),("/nix/store/ysl7znxpxa7ibnxpiflgn8mbvls8zx0d-python-output-dist-hook.drv",["out"])],["/nix/store/6xg259477c90a229xwmb53pdfkn6ig3g-default-builder.sh"],"x86_64-linux","/nix/store/m36d29gn5gm9bk0g7fcln1v8171hvn95-bash-5.2-p15/bin/bash",["-e","/nix/store/6xg259477c90a229xwmb53pdfkn6ig3g-default-builder.sh"],[("LANG","C.UTF-8"),("__structuredAttrs",""),("buildInputs",""),("builder","/nix/store/m36d29gn5gm9bk0g7fcln1v8171hvn95-bash-5.2-p15/bin/bash"),("cmakeFlags",""),("configureFlags",""),("depsBuildBuild",""),("depsBuildBuildPropagated",""),("depsBuildTarget",""),("depsBuildTargetPropagated",""),("depsHostHost",""),("depsHostHostPropagated",""),("depsTargetTarget",""),("depsTargetTargetPropagated",""),("disallowedReferences",""),("dist","/nix/store/4g45xi9866myvha3vxq8yahm29gxpsga-python3.10-yq-3.2.2-dist"),("doCheck",""),("doInstallCheck","1"),("mesonFlags",""),("name","python3.10-yq-3.2.2"),("nativeBuildInputs","/nix/store/vagb0sjv83ybi435i6iiv10hjrdghph9-python3-3.10.12 /nix/store/cwcdrvv94c4rys2cgxhs2byn6a4rczgr-wrap-python-hook /nix/store/2ay7q7ligvy0zkhb22z9hb6ksk68rgcf-ensure-newer-sources-hook /nix/store/4bm7si6b8hjfr3vncl1b3phckawdbhah-python-remove-tests-dir-hook /nix/store/3l5vkplnmwxdmccajy7knsx6hrzj9jf7-python-catch-conflicts-hook /nix/store/ihc2jyzhx3crnlws34qhhv4d73zp6zy6-python-remove-bin-bytecode-hook /nix/store/b9284xij30zf4zfmqvvamqag3gzfqrmh-setuptools-setup-hook /nix/store/414d6mi9bw0d3p48sy5z3468n445kzz8-pypa-install-hook /nix/store/l2lrx1kx0phn947rmylddrday6l6z1ig-python-imports-check-hook.sh /nix/store/4x04hyzyz8pfh2dqdvx7j5svp315j66k-python-namespaces-hook.sh /nix/store/9gcs29995dq04c8r8sx46nxczz083vw1-python-output-dist-hook /nix/store/6bx9kdapg02a19mkrhdyhdl4s0rnajyv-python3.10-setuptools-scm-7.1.0 /nix/store/47y9smr6b6g7542p1iahj1qzv4ncdr7a-setuptools-check-hook /nix/store/rkapa2ajfn7bphiy98bjyrgnfgvb2isa-pytest-check-hook"),("out","/nix/store/64lyjyh5q39akgwcd71yj53yaw4i15k4-python3.10-yq-3.2.2"),("outputs","out dist"),("patches","/nix/store/cvwrvbb09jqqz5mv2f4jl5rzzj58ycfv-jq-path.patch"),("pname","yq"),("postFixup","wrapPythonPrograms\n"),("propagatedBuildInputs","/nix/store/pngxdvmmc32m3hsy8psnxbk2rfrkdqyx-python3.10-argcomplete-3.1.1 /nix/store/31zpzgn2hr04mmg7dqp8gkf5n99i29ab-python3.10-pyyaml-6.0.1 /nix/store/r6ii1v9v4wrr6m29dksl5raqjn29q95n-python3.10-tomlkit-0.12.1 /nix/store/mdbiflqwg46s7yn46cww05zcqp52709z-python3.10-xmltodict-0.13.0 /nix/store/vagb0sjv83ybi435i6iiv10hjrdghph9-python3-3.10.12"),("propagatedNativeBuildInputs",""),("pytestFlagsArray","test/test.py"),("pythonImportsCheck","yq"),("src","/nix/store/7a84byjhj33rrc5yjd4mkz1yqiwkc6pn-yq-3.2.2.tar.gz"),("stdenv","/nix/store/7cni7ndy2pm18ysl5znq6znb30sxp156-stdenv-linux"),("strictDeps","1"),("system","x86_64-linux"),("version","3.2.2")]) |
|
Is jq failing to build or not? If so, please paste that |
|
Sorry for the confusion - the jq–build is indeed working, but AFAICT the issue is indeed because of a change of behaviour of jq of something in the |
|
The reason why I directly jumped to the conclusion that it had to do with the mentioned jq issue is that that log contained the lines: which was pretty much what I saw in the error message so I felt confirmed. I did not question my beliefs. Sorry for that! What is the procedure for such a dependency failure? This PR in itself is great, but I don't know how to deal with it breaking other packages... |
|
We can wait for known problems to be resolved upstream and bump the reverse dependencies simultaneously.
|
Good catch! I created an issue over there as well: mwilliamson/jq.py#93 |
|
Successfully built nix. |
|
Added a release note |
|
Aside from the pending comment about the release notes, are there any remaining objections to merging this change? |
After five years, jq is getting a new release! https://github.com/jqlang/jq/releases/tag/jq-1.7
Not sure if this deserves a release note? The breaking changes seem relatively limited, but
jqis kind of a core package.Things done
sandbox = trueset innix.conf? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)