!9IQChSjwSHXPPWTa:lix.systems

Lix

1123 Members
Lix user channel. Feel free to discuss on-topic issues here and give each other help. For matrix.to links to the rest of the Lix channels, see: https://wiki.lix.systems/books/lix-organisation/page/matrix-rooms304 Servers

Load older messages


SenderMessageTime
30 Jan 2026
@sofiedotcafe:matrix.orgSofie 🏳️‍⚧️ (she/her)nvm figured it out08:42:35
@rosssmyth:matrix.orgrosssmyth

I found something that is messed up with flakes:

  1. Write src = ./.;
  2. On another line write something like something = finalAttrs.src
  3. Run nom build

It shows that finalAttrs.src does not match the $src that is unpacked for some reason.

The log outputs will say something like

unpacking source archive /nix/store/6vpcbgxb1lv4xb36i4z0wcns26qkqb0a-ss7yf0ysfsr45a1811bcyvpkblpnhk1q-source
source root is ss7yf0ysfsr45a1811bcyvpkblpnhk1q-source

Notice that this looks like a store path made from a store path. It seems to be, as both store paths exist. But if you write something like:

echo "${finalAttrs.src}"

you will get:

ss7yf0ysfsr45a1811bcyvpkblpnhk1q-source

Since I rely on finalAttrs.src == $src I get a derivation failure. This can be fixed if I write something like src = self; from the flake outputs.

15:57:38
@rosssmyth:matrix.orgrosssmyth *

I found something that is weird:

  1. Write src = ./.;
  2. On another line write something like something = finalAttrs.src
  3. Run nom build

It shows that finalAttrs.src does not match the $src that is unpacked for some reason.

The log outputs will say something like

unpacking source archive /nix/store/6vpcbgxb1lv4xb36i4z0wcns26qkqb0a-ss7yf0ysfsr45a1811bcyvpkblpnhk1q-source
source root is ss7yf0ysfsr45a1811bcyvpkblpnhk1q-source

Notice that this looks like a store path made from a store path. It seems to be, as both store paths exist. But if you write something like:

echo "${finalAttrs.src}"

you will get:

ss7yf0ysfsr45a1811bcyvpkblpnhk1q-source

Since I rely on finalAttrs.src == $src I get a derivation failure. This can be fixed if I write something like src = self; from the flake outputs.

15:57:51
@rosssmyth:matrix.orgrosssmythNoticed this from a bug report on my library https://github.com/RossSmyth/press/issues/2015:58:05
@rosssmyth:matrix.orgrosssmyth *

I found something that is weird:

  1. Write src = ./.;
  2. On another line write something like something = finalAttrs.src
  3. Run nom build

It shows that finalAttrs.src does not match the $src that is unpacked for some reason.

The log outputs will say something like

unpacking source archive /nix/store/6vpcbgxb1lv4xb36i4z0wcns26qkqb0a-ss7yf0ysfsr45a1811bcyvpkblpnhk1q-source
source root is ss7yf0ysfsr45a1811bcyvpkblpnhk1q-source

Notice that this looks like a store path made from a store path. It seems to be, as both store paths exist. But if you write something like:

echo "${finalAttrs.src}"

you will get:

ss7yf0ysfsr45a1811bcyvpkblpnhk1q-source

Since I rely on finalAttrs.src == $src I get a derivation failure. This can be fixed if I write something like src = self; from the flake outputs, as then finalAttrs.src == $src in that case for some reason.

16:01:52
@rosssmyth:matrix.orgrosssmyth Definitely something flakey because running it without flakes it acts as expected (finalAttrs.src == $src) 16:18:08
@zimward:zimward.moezimward @fosdem changed their display name from zimward to zimward @fosdem.16:18:56
13 May 2024
@aciceri:nixos.devzrsk joined the room.13:37:30
@dariof4:matrix.orgdariof4 joined the room.14:16:05
@abbe:badti.meabbe joined the room.14:42:22
@mjm:midna.devmjmlix is now in nixos-unstable, what's the best way to use it in a NixOS config?15:47:41
@k900:0upti.meK900nix.package = pkgs.lix15:47:54
@k900:0upti.meK900Probably15:47:58
@k900:0upti.meK900Or just keep using the module15:48:02
@puck:puck.moepuck you can use nix.package = pkgs.lix; if you want; but using the overlay will guarantee more updates (tho less binary cache) 15:48:44
@mjm:midna.devmjmwell, the module/overlay doesn't easily support using the one from nixpkgs15:48:44
@mjm:midna.devmjmi do want more binary cache15:49:21
@mjm:midna.devmjm yeah i guess i'll just do nix.package then 15:50:43
@raitobezarius:matrix.orgraitobezariusto have binary cache and HEAD, we will probably need to track the channels and bolt a lix on there and rebuild with our own CI then push in our binary cache17:33:17
@charles:computer.surgeryCharlesWhat's lix using as its binary cache? Attic?17:34:36
@arianvp:matrix.orgArian left the room.17:37:44
@tc424:glasgow.social@tc424:glasgow.socialLast I heard they were using garage as the back end, and think about attic17:39:11
@tc424:glasgow.social@tc424:glasgow.socialI don't know if that means they're just pushing directly into garage's s3 interface for the moment17:39:36
@tc424:glasgow.social@tc424:glasgow.social* Last I heard they were using garage as the back end, and thinking about attic17:39:57
@raitobezarius:matrix.orgraitobezarius
In reply to @charles:computer.surgery
What's lix using as its binary cache? Attic?
garage without attic
17:41:16
@raitobezarius:matrix.orgraitobezariusit's homemade just nix push thingie17:41:24
@raitobezarius:matrix.orgraitobezariusand nix sign17:41:25
@qyriad:katesiria.orgQyriadyep17:44:26
@tc424:glasgow.social@tc424:glasgow.socialI've just given up on attic due to weird non-deterministic auth problems that nobody else seems to have experienced17:44:31
@tc424:glasgow.social@tc424:glasgow.socialStill half convinced I'm "holding it wrong" somehow17:44:49

Show newer messages


Back to Room ListRoom Version: 10