| 2 Nov 2023 |
|  diamond (it/its) changed their profile picture. | 08:56:17 |
| 3 Nov 2023 |
|  mib 🥐 changed their profile picture. | 13:53:41 |
|  shortcutz joined the room. | 20:14:46 |
| shortcutz | latest commit on the gnome branch failed to build for me | 20:50:29 |
| shortcutz | does anyone have a stable-ish commit they use for their own builds? | 20:50:56 |
| shortcutz | * does anyone have a stable-ish commit they use for their own environments? | 21:07:04 |
 donskifarrell | I've built from the latest commit on the gnome branch and it's working fine.
What's the failure you're getting? | 23:23:35 |
| shortcutz | i'm getting > 29/39 tracker:core / ontology-change TIMEOUT 60.01s killed by signal 15 SIGTERM when building tracker-3.6.0 | 23:36:26 |
| shortcutz | Download tracker-3.6.0.log | 23:39:26 |
| shortcutz | actually if it builds fine for you it is probably how i am using it in my configuration- i have a member of inputs in my system flake.nix pointing to github:NixOS/nixpkgs/gnome, and then in my modules i've added:
{
nixpkgs.overlays = [
(self: super: {
gnome = inp.gnomeNixpkgs.legacyPackages.x86_64-linux.gnome;
})
];
}
| 23:41:02 |
| shortcutz | anything seem wrong with that? | 23:41:15 |
| shortcutz | * actually if it builds fine for you it is probably how i am using it in my configuration- i have a member of inputscalled gnomeNixpkgs in my system flake.nix pointing to github:NixOS/nixpkgs/gnome, and then in my modules i've added:
{
nixpkgs.overlays = [
(self: super: {
gnome = gnomeNixpkgs.legacyPackages.x86_64-linux.gnome;
})
];
}
| 23:41:36 |
| 4 Nov 2023 |
| donskifarrell | That looks fine. I was using that way initially then I had an issue with mismatched GLIBC versions, so I made the gnome branch the primary nixpkgs url (which triggered a massive rebuild) in order to resolve it.
I haven't experienced the tracker issue yet but there were some related convos earlier in the chat if you scroll back.
The only similar issue was with libsecret, which was caused by 100% CPU usage. I kept restarting the builds and it eventually got there | 00:39:34 |
| donskifarrell | * That looks fine. I was using that way initially then I had an issue with mismatched GLIBC versions, so I made the gnome branch the primary nixpkgs url (which triggered a massive rebuild) in order to resolve it.
I haven't experienced the tracker issue yet but there were some related convos earlier in the chat if you scroll back.
The only similar issue to yours was with libsecret, which was caused by 100% CPU usage. I kept restarting the builds and it eventually got there | 00:39:43 |
| shortcutz | alright | 00:48:59 |
| shortcutz | In reply to @donskifarrell:matrix.org
That looks fine. I was using that way initially then I had an issue with mismatched GLIBC versions, so I made the gnome branch the primary nixpkgs url (which triggered a massive rebuild) in order to resolve it.
I haven't experienced the tracker issue yet but there were some related convos earlier in the chat if you scroll back.
The only similar issue to yours was with libsecret, which was caused by 100% CPU usage. I kept restarting the builds and it eventually got there by any chances was the CPU usage error related to a TIMEOUT [...] signal 15 sigterm message? hadn't seen that before this build | 00:52:46 |
| donskifarrell | In reply to @shortcutz:matrix.org
by any chances was the CPU usage error related to a TIMEOUT [...] signal 15 sigterm message? hadn't seen that before this build Ah, just checked and its not quite the same.
I was having this issue : https://gitlab.gnome.org/GNOME/libsecret/-/issues/80 | 01:18:45 |
| shortcutz | thanks anyway | 01:19:48 |
| shortcutz | not even sure what the issue is, i'm getting different errors every rebuild | 01:20:04 |
| shortcutz | the latest one had to do with a curl failure 🤷 | 01:20:16 |
 Jan Tojnar | shortcutz: the non-deterministic failures sometimes happen more frequently during CPU pressure, you can try building just the affected package if it persists (nix-build https://github.com/NixOS/nixpkgs/archive/gnome.tar.gz -A tracker) | 14:46:00 |
| Jan Tojnar | In reply to @shortcutz:matrix.org
actually if it builds fine for you it is probably how i am using it in my configuration- i have a member of inputscalled gnomeNixpkgs in my system flake.nix pointing to github:NixOS/nixpkgs/gnome, and then in my modules i've added:
{
nixpkgs.overlays = [
(self: super: {
gnome = gnomeNixpkgs.legacyPackages.x86_64-linux.gnome;
})
];
}
note that there are also some module changes so you might get issues from that | 14:46:53 |
| shortcutz | thanks for the tips! | 14:55:37 |
| shortcutz | i think i can corroborate the cpu pressure thing- i could get much farther (last <100 derivations) built when forcing `max-jobs=1`. maybe that doesnt technically correlate with cpu pressure but it is a fact | 14:56:57 |
| shortcutz | now my only issue is it running OOM, but i guess i fan fix that by building manually. | 14:57:56 |
| shortcutz | * now my only issue is it running OOM, but i guess i can fix that by building incrementally. | 15:00:24 |
|  thegreenguy changed their display name from thegreenguy to iGreenGuy Pro Max. | 21:24:41 |
| 6 Nov 2023 |
| diamond (it/its) | In reply to@shortcutz:matrix.org
actually if it builds fine for you it is probably how i am using it in my configuration- i have a member of inputscalled gnomeNixpkgs in my system flake.nix pointing to github:NixOS/nixpkgs/gnome, and then in my modules i've added:
{
nixpkgs.overlays = [
(self: super: {
gnome = gnomeNixpkgs.legacyPackages.x86_64-linux.gnome;
})
];
}
is this actually the recommended way to do this? wouldn't it make more sense if the gnome branch Nix files are imported using the system pkgs instead of pulling its own pkgs set (which includes a mismatch glibc)? | 05:34:10 |
| thegreenguy changed their display name from iGreenGuy Pro Max to thegreenguy. | 15:49:19 |
| 7 Nov 2023 |
|  Ramses 🇵🇸 joined the room. | 07:46:25 |
