!aGqRytqbCECitOFhbt:nixos.org

Release Management

338 Members
25.11 "Xantusia" | https://nixos.github.io/release-wiki/Home.html92 Servers

Load older messages


SenderMessageTime
29 Oct 2024
@arianvp:matrix.orgArianOr at least; I'm not running into the issue when I boot that nixos generation12:28:13
30 Oct 2024
@tomodachi94:matrix.orgTomodachi94 (they/them) joined the room.04:49:41
1 Nov 2024
@vcunat:matrix.orgVladimír Čunát Schedule: I believe we can only afford a single staging-next iteration before branch-off. 07:03:13
@vcunat:matrix.orgVladimír ČunátSo I suggest that we ~~scratch~~ the first cycle from the official schedule at least.07:04:11
@lily:lily.flowersLily Foster
In reply to @vcunat:matrix.org
So I suggest that we ~~scratch~~ the first cycle from the official schedule at least.
why, uh, is the schedule tight around that again? i don't think it's been like that in prior releases, but idk if staging has just been slow or if the schedule changed?
11:43:31
@me:linj.techlinjI guess the schedule changed due to holidays https://discourse.nixos.org/t/lets-have-a-great-24-11-release-cycle/5154911:51:20
@sigmasquadron:matrix.orgSigmaSquadronsooo, ZHF today?12:56:08
@sigmasquadron:matrix.orgSigmaSquadron

I've been trying to fix gnuk recently, but i don't think there's time to add the new packages its newer versions require, so the PR I have prepped for it just overhauls the derivation to conform to recent standards and marks it as broken.

13:00:38
@sigmasquadron:matrix.orgSigmaSquadron *

I've been trying to fix gnuk recently (has been failing to build for a while now), but i don't think there's time to add the new packages its newer versions require, so the PR I have prepped for it just overhauls the derivation to conform to recent standards and marks it as broken.

13:00:55
@sigmasquadron:matrix.orgSigmaSquadron

it requires picolibc which will probably be a mess of pkgsCross that I do not want to touch.

13:01:31
@vcunat:matrix.orgVladimír ČunátNew packages can be added to stable releases any time, e.g. 24.05 could still get them even.13:03:06
@vcunat:matrix.orgVladimír Čunát * New packages can be added to stable releases any time, e.g. 24.05 could still get them even, at this moment.13:03:16
@rosscomputerguy:matrix.orgTristan Ross
In reply to @sigmasquadron:matrix.org
sooo, ZHF today?
Yes
14:13:12
@rosscomputerguy:matrix.orgTristan Rosshttps://github.com/NixOS/nixpkgs/issues/35288214:34:56
@emilazy:matrix.orgemilyyou're missing the ñ!14:47:54
@rosscomputerguy:matrix.orgTristan Ross
In reply to @emilazy:matrix.org
you're missing the ñ!
I can't type it with my JP IME lol
14:50:47
@tomodachi94:matrix.orgTomodachi94 (they/them)Is it okay to drop packages that we realistically cannot maintain and that have been EOL for a long time, with a large number of open CVEs and several mature compatible replacements?23:56:49
@tomodachi94:matrix.orgTomodachi94 (they/them) (I'm referring to OracleJDK in this specific case, but I made the question a tad more general. There is already consensus in #NixOS JVM that we can't realistically maintain that) 23:58:12
@emilazy:matrix.orgemilyit would be okay even if only one of those applied tbh23:58:23
@emilazy:matrix.orgemily
In reply to @qyliss:fairydust.space
We've never prevented removing packages at any time before a release either, fwi.w
see discussion around here
23:58:40
2 Nov 2024
@hpfr:matrix.orghpfr joined the room.04:01:46
@sigmasquadron:matrix.orgSigmaSquadronHow recent must the latest upstream commit be for a package to be considered maintained?04:58:22
@sigmasquadron:matrix.orgSigmaSquadron * How recent must the latest upstream commit be for a package to be considered maintained w.r.t not immediately dropping them as unmaintained during ZHF?04:58:46
@sigmasquadron:matrix.orgSigmaSquadronI found a couple of broken packages that have been unmaintained for 6+ months05:00:17
@sigmasquadron:matrix.orgSigmaSquadron * I found a couple of broken packages that have been unmodified for 6+ months, and another that has been last modified in October, but no longer builds in upstream's CI, nor in someone's Ubuntu install, nor in Hydra.05:03:14
@pyrox:pyrox.devdish [Fox/It/She]I'd say if they're not building in upstream's CI then it would be reasonable to drop it. If upstream can't maintain it, then we shouldn't try to either. If it was working in ours, I'd see no reason to drop, but since it doesn't, I'm in favor of dropping05:12:00
@emilazy:matrix.orgemilyI would say it's not healthy if ZHF is the only thing keeping a package going05:15:44
@emilazy:matrix.orgemilyi.e. if there's no expectation it won't just end up getting fixed again by someone else in a couple ZHFs time05:16:13
@vcunat:matrix.orgVladimír ČunátI'd say it's possible to mark it as broken instead of dropping, if there's still hope that the package will soon revive.06:04:34
@youwen:matrix.orgYouwen joined the room.07:17:05

Show newer messages


Back to Room ListRoom Version: 6