| 27 Oct 2023 |
donskifarrell |  Download 2023-10-27-10-46-22-741.jpg | 02:55:37 |
donskifarrell | I'm fairly new to nixos - is there an easy way to get more debug info at this stage of boot? | 02:56:04 |
vcunat | Nothing on Hydra so far. I asked already - it mainly remains for you/devs to choose the right moment, and I can create it.
Say, now they'd probably want to add in recent master commits, as gnome branch is missing two weeks including a staging-next merge.
| 05:35:43 |
diamond (it/its) | yea I thought it was already in master but I guess not | 05:42:25 |
| diamond (it/its) changed their profile picture. | 16:00:30 |
| romildo joined the room. | 19:36:24 |
| 28 Oct 2023 |
| ShivaAU joined the room. | 23:14:54 |
| ShivaAU changed their display name from shivaau to ShivaAU. | 23:18:13 |
| 29 Oct 2023 |
nadir | Does anybody know what's holding up the inclusion in Hydra? vcunat Do I understand you correctly in that the developers of the PR just need to ask for it to be included, but that they feel it's not the time for that yet? Anything big yet left to merge? | 13:47:28 |
Jan Tojnar | nadir: we are probably going to rebase soon so no point in building it on Hydra for now | 14:05:20 |
vcunat | Yes, I'm just waiting for the branch's devs +1 | 14:12:14 |
nadir | Jan Tojnar: That makes sense. Thank you. | 14:19:51 |
| ChaosAttractor joined the room. | 15:10:31 |
| 30 Oct 2023 |
donskifarrell | In reply to @donskifarrell:matrix.org I've suddenly ran into an issue with my local build tho. My boot sequence gets stuck on [ ok ] Started Display Manager and doesn't load gdm. This is using the most recent pull from github branch, yet I was successful in building and running it from a previous pull around 10th Oct. this was a GLIBC mismatch. A flake update and a full rebuild fixed it up | 11:38:42 |
| 1 Nov 2023 |
| @arcayr:rascals.net joined the room. | 07:33:56 |
| @djrmarques:matrix.org joined the room. | 09:38:04 |
| 2 Nov 2023 |
| diamond (it/its) changed their profile picture. | 08:54:51 |
| 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 |