!UNVBThoJtlIiVwiDjU:nixos.org

Staging

319 Members
Staging merges | Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-25.05 | Review Reports: https://malob.github.io/nix-review-tools-reports/109 Servers

Load older messages


SenderMessageTime
15 Dec 2025
@k900:0upti.meK900Are we doing master next?07:05:12
@vcunat:matrix.orgvcunat I had been thinking - because now is a rare opportunity when stable and unstable haven't diverged much in terms of rebuilds - that maybe we could first pick the contents of this staging-next-25.11 and merge that pretty quickly into nixpkgs master. Well, perhaps after checking that all of it really was intended for staging/master as well (relatively easy from cherry-pick marks). 07:27:37
@vcunat:matrix.orgvcunatBut perhaps it's not worth the bother. The main advantage would be security fixes getting at least one week earlier than otherwise. Probably.07:28:11
@vcunat:matrix.orgvcunat * I had been thinking - because now is a rare opportunity when stable and unstable haven't diverged much in terms of rebuilds - that maybe we could first pick the contents of this staging-next-25.11 into staging-next and merge that pretty quickly into nixpkgs master. Well, perhaps after checking that all of it really was intended for staging/master as well (relatively easy from cherry-pick marks). 07:28:38
@fabianhjr:matrix.orgFabián HerediaWasn't there a staging-next cycle that wasn't part of 25.11 already performed?07:30:19
@fabianhjr:matrix.orgFabián HerediaAh no that's right the last staging-next cycle is part of 25.11 :O07:33:12
@fabianhjr:matrix.orgFabián Herediahttps://github.com/NixOS/nixpkgs/commit/3dd12c46719c52e75d9f86998de15db82d27a6df07:33:14
@fabianhjr:matrix.orgFabián Heredia
git log origin/master..origin/staging --grep CVE

Only shows:

  • gnutls (low and on 25.11)
  • libpng 1.6.51 (highs and on 25.11)
  • django_4 (moderate and on 25.11)
  • libpng: 1.6.52 (highs and on 25.11)
  • xkbcomp (moderates and on 25.11)
  • libarchive (no CVEs and not on 25.11)
  • glib (highs and not on 25.11)
07:42:00
@vcunat:matrix.orgvcunatThere was a 25.05 cycle, so perhaps that's what you mistaked for it.07:53:08
@vcunat:matrix.orgvcunat* There was a 25.05 cycle, so perhaps that's what you mistook for it.07:53:22
@fabianhjr:matrix.orgFabián Herediayeah, just double checked and there hasn't been a staging-next cycle not part of 25.1107:53:55
@yuka:yuka.devYureka (she/her)https://github.com/NixOS/nixpkgs/issues/47096108:42:31
@yuka:yuka.devYureka (she/her)https://github.com/NixOS/nixpkgs/issues/47096208:44:32
@yuka:yuka.devYureka (she/her)https://github.com/NixOS/nixpkgs/issues/47096408:46:34
@grimmauld:m.grimmauld.deGrimmauld (any/all)
In reply to @yuka:yuka.dev
https://github.com/NixOS/nixpkgs/issues/470964
This one looks like an XML parser fail, but we didn't touch libxml2 this time, wtf????
08:48:50
@k900:0upti.meK900"fuzz" in the name08:49:05
@k900:0upti.meK900I wonder if they're actually fuzzing it08:49:09
@grimmauld:m.grimmauld.deGrimmauld (any/all)Oh god08:49:18
@ghpzin:envs.netghpzinThat is some new python version thing (just linked in issue): https://bugs.launchpad.net/beautifulsoup/+bug/213439308:53:16
@k900:0upti.meK900Ah08:53:43
@k900:0upti.meK900Minor Python version updates breaking libraries08:53:51
@k900:0upti.meK900Must be a day that ends in Y08:53:54
@ghpzin:envs.netghpzin* That is some new python version thing (just linked in issue): https://bugs.launchpad.net/beautifulsoup/+bug/2134393 https://git.launchpad.net/beautifulsoup/commit/?id=55f655ffb7ef03bdd1df0f013743831fe54e3c7a08:54:23
@vcunat:matrix.orgvcunatIt's normal for patch-level python3 updates to break some stuff.08:59:37
@vcunat:matrix.orgvcunatAlways at least a few tests in python3Packages.08:59:51
@vcunat:matrix.orgvcunat* It's normal for patch-level python3 updates to break some stuff, sadly.09:00:04
@capypara:matrix.orgCapypara joined the room.09:23:27
@jlamur:matrix.orgJules Lamur joined the room.10:11:33
@matshch:matrix.orgArtem Leshchev joined the room.18:48:09
@fabianhjr:matrix.orgFabián HerediaRe: short 25.11-analog staging-next for unstable I think the only high >= severity security fix would be libpng and others would be delayed glib which probably has more usage) If that short staging-next cycle would be about a couple of days the next staging-next cycle would start around holidays (navidad + new year in my case) and I would rather do any pending gcc fixes before then to have less to think about during winter holidays xd19:58:24

Show newer messages


Back to Room ListRoom Version: 6