| 21 Feb 2025 |
 Lunaphied | In reply to@charles:computer.surgery
writing a blog post explaining the non-flakes way in depth is a good idea, i may attempt this when i have time. i'm kinda swamped for the next week and a half or so though so it may be a while I mean there's always https://jade.fyi/blog/flakes-arent-real/ and https://jade.fyi/blog/pinning-nixos-with-npins/ | 00:15:57 |
 Charles | there's a lot of good info in there but it's not quite how i would do it | 00:26:43 |
| Lunaphied | 🟣A> Just important to point out there's some information already out there | 00:27:17 |
| Lunaphied | * Just important to point out there's some information already out there | 00:27:21 |
|  clay53 joined the room. | 01:12:51 |
 Whovian9369 | Any idea on why I am getting the following whenever I do a nix flake update or attempt to build a system config after a gc? The warning seems to be printed a total of 4 times.
warning: refname '621aae0f3cceaffa6d73a4fb0f89c08d338d729e' is ambiguous.
Git normally never creates a ref that ends with 40 hex characters
because it will be ignored when you just specify 40-hex. These refs
may be created by mistake. For example,
git switch -c $br $(git rev-parse ...)
where "$br" is somehow empty and a 40-hex ref is created. Please
examine these refs and maybe delete them. Turn this message off by
running "git config advice.objectNameWarning false"
| 05:27:23 |
| Whovian9369 | I'm using nix (Lix, like Nix) 2.93.0-dev-pre20250214-1077bc6 so I just realized that may be a little out of date -- Lemme see if I can correct that. | 05:27:55 |
| Whovian9369 | Seems to be reproducible by me on nix (Lix, like Nix) 2.93.0-dev-pre20250221-e7aa55c as well | 05:33:14 |
 aloisw | That may be a bug unless you actually have a branch or tag of that name somewhere. | 06:57:54 |
|  oli 🏳️⚧️ joined the room. | 08:51:18 |
 raitobezarius | In reply to @charles:computer.surgery
will anything explode if i try to change my username on identity.lix.systems to have capital letters in it Normally no | 10:55:26 |
 validitymaiden | Not sure if this is the right place to ask this; just let me know if so. I've noticed that when I use nix --help I get some unexpected coding inline with the command names, such as · 8;;./nix3-help.mdnix help8;; | 15:16:27 |
| validitymaiden | man nix doesn't produce this. I've tried it in zsh and tcsh with the same result | 15:16:51 |
| Lunaphied | I've encountered the same issue for quite awhile. I am not sure the cause. | 15:19:50 |
| validitymaiden | Ok, thanks for confirming it's not just my environment. I'll take a look at it at | 15:20:38 |
| validitymaiden | Just wanted to share that there is a bug for this and jade is aware of the source of the issue. I'll still see if I can help with it but here's the bug https://git.lix.systems/lix-project/lix/issues/622 | 15:30:02 |
| validitymaiden | is this thread visible to everyone or just Lunaphied and I? This is my first usage of Element, so apologies | 15:30:47 |
| validitymaiden | Is this the right place to request a Lix account? Also, is there a preferred process for contributions? | 15:38:12 |
 K900 | Threads are visible to everyone, but you probably don't want to use them | 15:38:25 |
| K900 | Since not all clients support them | 15:38:35 |
| K900 | (that's a Matrix Moment) | 15:38:42 |
| K900 | You can just sign in with github on keycloak | 15:38:58 |
| K900 | If you don't want to, I can make you a keycloak account in a bit | 15:39:07 |
| validitymaiden | I am probably going to shift to using something else besides github so I'd prefer the keycloak if it isn't too much trouble. Please take your time, I'm in no rush | 15:40:20 |
| K900 | You can sign in with github once, then update your account to use other login flows I think | 15:41:54 |
| Whovian9369 | If that was for me, the only reference that I could find for the rev string was in my flake.lock for /lix-project/nixos-module
$ rg -N --context=4 621aae0f3cceaffa6d73a4fb0f89c08d338d729e
flake.lock
"locked": {
"lastModified": 1738176840,
"narHash": "sha256-NG3IRvRs3u3btVCN861FqHvgOwqcNT/Oy6PBG86F5/E=",
"ref": "refs/heads/main",
"rev": "621aae0f3cceaffa6d73a4fb0f89c08d338d729e",
"revCount": 133,
"type": "git",
"url": "https://git.lix.systems/lix-project/nixos-module"
},
| 16:39:19 |
| Whovian9369 | and all of the other .nodes.[].locked.rev entries appear to be the same length, which also makes me wonder why it was only erroring on a Lix-related rev string | 16:40:33 |
 just1602 | Oh thanks, I was aware and read flakes arent' real, but didn't know about the pinning nixos with npins article. | 17:20:16 |
| Lunaphied | np | 17:44:34 |
| aloisw | In reply to @lunaphied:lunaphied.me
I've encountered the same issue for quite awhile. I am not sure the cause. lowdown update in conjunction with our broken filtering code. | 18:20:47 |
