| 23 Sep 2022 |
 Winter (she/her) |
trap "exitHandler" EXIT
| 13:03:28 |
| Winter (she/her) | which should not be possible! what even | 13:03:37 |
| Winter (she/her) |
If a sigspec is 0 or EXIT, arg is executed when the shell exits.
| 15:14:55 |
| Winter (she/her) | per bash manual | 15:14:58 |
| Winter (she/her) | so... what? | 15:15:07 |
 trofi | Might be a subshell? | 17:36:08 |
| 25 Sep 2022 |
|  piegames joined the room. | 19:11:27 |
| piegames | Hi, can somebody help me figure out what exactly this failure means? https://gist.github.com/GrahamcOfBorg/40de36fd7e6b24925f81c75e8623dc0a | 19:12:04 |
| piegames | This happens when I call lib.getName on a derivation during checkMeta, see https://github.com/NixOS/nixpkgs/pull/177272 | 19:12:29 |
 Artturin | removing ${name} from here https://github.com/NixOS/nixpkgs/blob/5fa1488e2b0effad849125784310f17b16f59004/pkgs/build-support/trivial-builders/test-overriding.nix#L95 makes it not fail | 19:28:20 |
| piegames | But—why? | 19:30:15 |
| Artturin | nix-repl> builtins.baseNameOf bash
"p7bpdnxqd3i5hwm92mrscf7mvxk66404-bash-5.1-p16"
so it'll be embeded in the name
| 19:32:52 |
| Artturin | builtins.unsafeDiscardStringContext has to be used | 19:32:55 |
| Artturin | diff --git a/pkgs/build-support/trivial-builders/test-overriding.nix b/pkgs/build-support/trivial-builders/test-overriding.nix
index a16bbbee1b1..1ea8d7c0b90 100644
--- a/pkgs/build-support/trivial-builders/test-overriding.nix
+++ b/pkgs/build-support/trivial-builders/test-overriding.nix
@@ -91,7 +91,7 @@ let
# works at run time.
runTest = script:
let
- name = script.name or (builtins.baseNameOf script);
+ name = script.name or (builtins.unsafeDiscardStringContext (builtins.baseNameOf script));
in writeShellScript "run-${name}" ''
if [ "$(${script})" != "success" ]; then
echo "Failed in ${name}"
makes it pass too
| 19:33:37 |
| piegames | Artturin Thank you | 20:14:21 |
| 28 Sep 2022 |
|  coolshaurya changed their profile picture. | 17:32:55 |
| 3 Oct 2022 |
|  spacesbot - keeps a log of public NixOS channels joined the room. | 14:25:48 |
| Artturin | https://github.com/NixOS/nixpkgs/pull/194259 | 17:20:43 |
| 15 Oct 2022 |
|  underpantsgnome changed their display name from underpantsgnome to underpantsgnome!. | 00:34:19 |
| 17 Oct 2022 |
 hexa |
On x86_64 systems, x86_64 microarchitecture levels are mapped to additional system types (e.g. x86_64-v1-linux).
| 13:39:44 |
| hexa | John Ericson: nix since 2.4 supports building for given x86_64 abi levels, but nixpkgs doesn't allow that | 13:40:05 |
| hexa | ❯ nom-build -A hello --option system x86_64-v3-linux
error: Target specification with 3 components is ambiguous
⚠︎ Exited with 1 errors reported by nix at 15:38:23 after 0s
| 13:40:12 |
| hexa | ❯ nix -vv --version
nix (Nix) 2.11.0
System type: x86_64-linux
Additional system types: i686-linux, x86_64-v1-linux, x86_64-v2-linux, x86_64-v3-linux
| 13:40:29 |
| hexa | * ❯ nix -vv --version
nix (Nix) 2.11.0
System type: x86_64-linux
Additional system types: i686-linux, x86_64-v1-linux, x86_64-v2-linux, x86_64-v3-linux
[...]
| 13:40:35 |
| hexa | The error comes from here:
8c99aab lib/systems/parse.nix John Ericson 2017-02-09 16:09 -0500 442│ else throw "Target specification with 3 components is ambiguous";
| 13:41:02 |
| hexa | can you look into supporting that? | 13:41:29 |
| hexa | the rationale would be to flag certain packages with an abi level requirement, so build time does not get wasted | 13:43:19 |
| hexa | that applies mostly to the ML sector, where builds and tests are often quite costly | 13:43:36 |
| hexa | * ❯ nom-build -A hello --option system x86_64-v3-linux
error: Target specification with 3 components is ambiguous
⚠︎ Exited with 1 errors reported by nix at 15:38:23 after 0s
via https://github.com/NixOS/nix/pull/4551
| 13:44:04 |
| 22 Oct 2022 |
 sterni | hexa: FWIW x86_64-v1-linux etc. tuples are bogus, neither LLVM nor autotools accept those and it's quite understandable since they cause a huge nightmare when parsing | 19:55:29 |
