!siOVEzpzgLbkHTjpmA:numtide.com

NixOS Archivists

56 Members
Taking care of NixOS historical build artifacts and GC. Meeting notes: https://pad.lassul.us/nixos-cache-gc For self-hosting, see #binary-cache-selfhosting:nixos.org 18 Servers

Load older messages


SenderMessageTime
26 Mar 2024
@leo60228:matrix.orgleo60228 joined the room.22:53:44
30 Mar 2024
@zimbatm:numtide.comJonas Chevalierjust saw this today, following the xz investigation: https://ghe.clickhouse.tech/ this could be useful to run analytics on the NixOS ecosystem10:40:29
@edef1c:matrix.orgedefyeah, we have the slight problem that we don't necessarily have a good overview of every GH repo we pull source from10:41:14
@edef1c:matrix.orgedefand 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 source10:42:00
@zimbatm:numtide.comJonas Chevalieryeah. 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:matrix.orgraitobezariusI'm afraid I need the meeting to move to another day12:15:10
@raitobezarius:matrix.orgraitobezariusI'm unable to attend on Tuesday from now on12:15:14
@edef1c:matrix.orgedefokay, what would work?12:15:40
@edef1c:matrix.orgedefi'm having a pretty rough day, so punting it forwards seems fine to me12:15:55
@edef1c:matrix.orgedefand i'm pretty indifferent to which particular day we move it to12:16:23
@mvtva:matrix.orgmvnetbiz joined the room.12:23:09
@raitobezarius:matrix.orgraitobezariusHere's my proposal: https://meet.dgnum.eu/nixos-archivists-weekly-meeting-42121712:52:47
@raitobezarius:matrix.orgraitobezarius edef: ^ 12:53:05
@raitobezarius:matrix.orgraitobezariusLet's fill this to find the optimal weekly slot12:53:20
@raitobezarius:matrix.orgraitobezarius Jonas Chevalier: flokli Eelco as usuals of the meeting ^ 12:53:40
9 Apr 2024
@symphorien:xlumurb.eusymphorien joined the room.20:40:03
@patka_123:matrix.org@patka_123:matrix.org joined the room.20:40:41
@ss:someonex.netSomeoneSerge (back on matrix) joined the room.20:43:39
@symphorien:xlumurb.eusymphorien 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@federicodschonborn:matrix.org joined the room.21:01:26
@thubrecht:matrix.orgthubrecht joined the room.21:03:58
@connorbaker:matrix.orgconnor (he/him) (UTC-7) joined the room.21:24:25
@tomasajt:matrix.orgToma joined the room.21:34:00
@ajaxbits:matrix.orgajaxbits joined the room.22:35:36
10 Apr 2024
@aloisw:kde.org@aloisw:kde.org joined the room.04:34:47
@edef1c:matrix.orgedef
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:xlumurb.eusymphorienReproducibility is already blamed today https://github.com/NixOS/nix/issues/7756 so it's not sure it would make the situation worse08:15:09
@edef1c:matrix.orgedefoof22:29:25
11 Apr 2024
@flokli:matrix.orgflokli🍿15:16:42
23 Apr 2024
@dnrix:matrix.orgdnr joined the room.03:06:54

Show newer messages


Back to Room ListRoom Version: 10