!aGqRytqbCECitOFhbt:nixos.org

Release Management

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

You have reached the beginning of time (for this room).


SenderMessageTime
7 Nov 2024
@vcunat:matrix.orgvcunatI'd say we just merge it. (first the channel-scripts part)07:27:01
@vcunat:matrix.orgvcunatIt's been hanging there for over a week, not trying to hide, and I haven't noticed any argument against really.07:27:36
@emilazy:matrix.orgemilySGTM07:28:15
@emilazy:matrix.orgemilyif you want to hit the button and deploy the scripts stuff07:28:29
@vcunat:matrix.orgvcunatToday I feel overwhelmed, but I should do it this week if noone else steps in.07:31:09
@emilazy:matrix.orgemilyno worries :)07:32:49
@emilazy:matrix.orgemily(I guess it's the infra team that has access to merging/deploying channel scripts PRs?)07:33:09
@vcunat:matrix.orgvcunat Yes. This runs on pluto.nixos.org. 07:33:46
@katexochen:matrix.orgPaul Meyer (katexochen)2nd staging-next is open, are breaking changes already unrestricted on staging?13:43:43
@joerg:thalheim.ioMic92
In reply to @vcunat:matrix.org
Today I feel overwhelmed, but I should do it this week if noone else steps in.
what needs to be done?
14:15:17
@rosscomputerguy:matrix.orgTristan Ross
In reply to @katexochen:matrix.org
2nd staging-next is open, are breaking changes already unrestricted on staging?
For staging, that will be the 8th
16:07:42
@hexa:lossy.networkhexa
In reply to @emilazy:matrix.org
if you want to hit the button and deploy the scripts stuff
deployed
16:19:15
@rosscomputerguy:matrix.orgTristan Ross
In reply to @emilazy:matrix.org
https://github.com/NixOS/nixpkgs/pull/352603 is pending a decision for 24.11
Oh, I didn't see this one on my feed lol. I'll take a look.
16:35:14
8 Nov 2024
@hexa:lossy.networkhexapkgs.formats.yaml was migrated to yaml 1.2 output in the last remarshal update18:01:28
@hexa:lossy.networkhexathe output now unquotes certain outputs, that previously needed to be quoted in yaml 1.118:02:08
@hexa:lossy.networkhexawhich otoh means that when parsed by a yaml 1.1 parser will lead to unexpected results18:02:23
@hexa:lossy.networkhexa
$ cat test.json 
{
  "time": "22:30:00"
}
$ json2yaml test.json test.yaml
$ cat test.yaml
time: 22:30:00
$ python3
Python 3.12.7 (main, Oct  1 2024, 02:05:46) [GCC 13.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import yaml
>>> yaml.safe_load(open("test.yaml"))
{'time': 81000}
>>> 
18:02:34
@hexa:lossy.networkhexa
$ cat test.json
{
  "enable": "on",
  "disable": "off"
}
$ json2yaml test.json test.yaml
$ cat test.yaml
enable: on
disable: off
$ python3
Python 3.12.7 (main, Oct  1 2024, 02:05:46) [GCC 13.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import yaml
>>> yaml.safe_load(open("test.yaml"))
{'enable': True, 'disable': False}
18:02:50
@emilazy:matrix.orgemilyIIRC YAML 1.2 isn't that widely-adopted (though maybe that's changed?). is there a remarshal flag to use 1.1?18:03:31
@hexa:lossy.networkhexaI'm contemplating whether to provide the remarshal package in an old version for yaml 1.1 support18:03:44

Show newer messages


Back to Room ListRoom Version: 6