26 Mar 2024 |
| leo60228 joined the room. | 22:53:44 |
30 Mar 2024 |
Jonas Chevalier | just saw this today, following the xz investigation: https://ghe.clickhouse.tech/
this could be useful to run analytics on the NixOS ecosystem | 10:40:29 |
edef | yeah, we have the slight problem that we don't necessarily have a good overview of every GH repo we pull source from | 10:41:14 |
edef | and the obvious problem (and i hope, now obvious to all) that we do not in fact always use the git/GitHub source, but source tarballs, which need not correspond to actual source | 10:42:00 |
Jonas Chevalier | yeah. I was thinking also in terms of better understanding usage patterns from the community, it's a nice data source to have. | 13:12:36 |
2 Apr 2024 |
raitobezarius | I'm afraid I need the meeting to move to another day | 12:15:10 |
raitobezarius | I'm unable to attend on Tuesday from now on | 12:15:14 |
edef | okay, what would work? | 12:15:40 |
edef | i'm having a pretty rough day, so punting it forwards seems fine to me | 12:15:55 |
edef | and i'm pretty indifferent to which particular day we move it to | 12:16:23 |
| mvnetbiz joined the room. | 12:23:09 |
raitobezarius | Here's my proposal: https://meet.dgnum.eu/nixos-archivists-weekly-meeting-421217 | 12:52:47 |
raitobezarius | edef: ^ | 12:53:05 |
raitobezarius | Let's fill this to find the optimal weekly slot | 12:53:20 |
raitobezarius | Jonas Chevalier: flokli Eelco as usuals of the meeting ^ | 12:53:40 |
9 Apr 2024 |
| symphorien joined the room. | 20:40:03 |
| @patka_123:matrix.org joined the room. | 20:40:41 |
| SomeoneSerge (back on matrix) joined the room. | 20:43:39 |
symphorien | hey, I'm interested in having more debug info in nixpkgs, which has storage size implication (debuginfo is frequently as large as the executable, sometimes more). I have proposed a way https://github.com/NixOS/nix/pull/8080 to mark debuginfo NARs as debuginfo so that a different AWS retention policy can be set for those, but this approach has been deemed not generic enough. Do you have other approaches in mind that could allow having debuginfo in the cache for, say, 6 months? | 20:46:29 |
| @federicodschonborn:matrix.org joined the room. | 21:01:26 |
| thubrecht joined the room. | 21:03:58 |
| connor (he/him) (UTC-7) joined the room. | 21:24:25 |
| Toma joined the room. | 21:34:00 |
| ajaxbits joined the room. | 22:35:36 |
10 Apr 2024 |
| @aloisw:kde.org joined the room. | 04:34:47 |
edef | In reply to @symphorien:xlumurb.eu hey, I'm interested in having more debug info in nixpkgs, which has storage size implication (debuginfo is frequently as large as the executable, sometimes more). I have proposed a way https://github.com/NixOS/nix/pull/8080 to mark debuginfo NARs as debuginfo so that a different AWS retention policy can be set for those, but this approach has been deemed not generic enough. Do you have other approaches in mind that could allow having debuginfo in the cache for, say, 6 months? the biggest problem there is that it places much stronger requirements on reproducibility | 07:33:30 |
symphorien | Reproducibility is already blamed today https://github.com/NixOS/nix/issues/7756 so it's not sure it would make the situation worse | 08:15:09 |
edef | oof | 22:29:25 |
11 Apr 2024 |
flokli | 🍿 | 15:16:42 |
23 Apr 2024 |
| dnr joined the room. | 03:06:54 |