| 22 May 2025 |
 das-g | * Oh. Is that a Chaos Post thing? | 19:45:32 |
 Wheeze_NL | I can post it, but that is no fun | 19:45:36 |
| das-g | I see. | 19:45:46 |
| das-g | Maybe the secretary can pick it up on the way back. | 19:46:31 |
| Wheeze_NL | Would be welcome | 19:47:26 |
| 24 May 2025 |
 infinisil | I'll be late for the hackathon today. Need to take care of myself a bit better and get enough sleep :) | 00:01:40 |
 kirelagin | Building 4, room 4.113 | 07:57:47 |
 l0b0 | 1st floor | 08:15:59 |
 Lorenz | https://docs.google.com/presentation/d/1qwIU_qe9nTJL3csTETDhLrz3rC7EjPqxFPl_Gpsx6No/ | 08:17:18 |
| Lorenz | That is silvans presentation about how to contribute to nixpkgs | 08:17:39 |
|  chemonke joined the room. | 08:19:11 |
|  Matteo joined the room. | 08:20:40 |
|  ochsnerd joined the room. | 08:31:15 |
|  zekjur joined the room. | 08:51:34 |
| zekjur | what’s the link to this event’s nixpkgs ZHF tracking issue? the slides link to https://github.com/NixOS/nixpkgs/issues/352882, which is last year’s | 08:52:47 |
 ners | Seems to be this one:
https://github.com/NixOS/nixpkgs/issues/403336 | 09:07:10 |
| zekjur |
NixOS 25.05 is released 🎉 Therefore ZHF ends now. Thank you all so much for your contributions!
huh. are we too late? :)
| 09:10:34 |
| infinisil | Haha yeah it was released yesterday https://discourse.nixos.org/t/nixos-25-05-released/64669 | 09:15:40 |
 thomas-zahner | Redacted or Malformed Event | 09:41:42 |
 lassulus | images are sadly disabled because of spam wave | 09:44:33 |
 mfrischknecht | Is there a policy to "promote" existing PRs to ZHF? I noticed verapdf is broken (dependency hash mismatch), and there's already an open PR here: https://github.com/NixOS/nixpkgs/pull/390112 | 10:58:20 |
|  kiara joined the room. | 10:59:55 |
| mfrischknecht | And I run into the next thing I'm unclear about; I'd be glad about some guidance on how we're handling the dropping of old Qt5 packages.
I looked at quaternion-qt5, which fails to build: https://hydra.nixos.org/build/297643965
...because it uses libquotient, which has dropped Qt5 support: https://github.com/quotient-im/libQuotient/releases/tag/0.9.0
...which also seems reflected in the quaternion project's own CMakeLists.txt: https://github.com/quotient-im/Quaternion/blob/dev/CMakeLists.txt#L64
They seemingly just didn't update their readme and GitHub tags.
Should I just open an issue to drop the Qt5 version? Should I prepare a PR? Are there any policy-decisions to this (dropping an old package)?
Also: I guess with the Qt5 version gone, we could get rid of the -qt6 suffix, too. I'm not sure about how much potential there is for refactoring because of that.
| 11:40:23 |
| mfrischknecht | * And I ran into the next thing I'm unclear about; I'd be glad about some guidance on how we're handling the dropping of old Qt5 packages.
I looked at quaternion-qt5, which fails to build: https://hydra.nixos.org/build/297643965
...because it uses libquotient, which has dropped Qt5 support: https://github.com/quotient-im/libQuotient/releases/tag/0.9.0
...which also seems reflected in the quaternion project's own CMakeLists.txt: https://github.com/quotient-im/Quaternion/blob/dev/CMakeLists.txt#L64
They seemingly just didn't update their readme and GitHub tags.
Should I just open an issue to drop the Qt5 version? Should I prepare a PR? Are there any policy-decisions to this (dropping an old package)?
Also: I guess with the Qt5 version gone, we could get rid of the -qt6 suffix, too. I'm not sure about how much potential there is for refactoring because of that.
| 11:40:39 |
| thomas-zahner | I have an interesting problem when accessing https://hydra.nixos.org
With both Firefox and Chromium I get 403 responses and can't use the website. I've now debugged it with cURL and found the following.
Chromium: curl -I 'https://hydra.nixos.org/' -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36'
Firefox: curl -I 'https://hydra.nixos.org/' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:132.0) Gecko/20100101 Firefox/132.0'
Removing Firefox/132.0 from Firefox's headers fixes the problem. Removing Chrome/130.0.0.0 from the Chromium headers also fixes the problem.
To me this sounds like the firewall is too restrictive. I've now modified the headers with a browser extension to work around the problem.
Could someone fix this issue?
| 11:42:25 |
| thomas-zahner | Realised that it just rejects old browser versions 😅 guess that might make sense.. | 11:56:54 |
| zekjur | if avocadoom is around (outside?), somebody make them aware of https://github.com/NixOS/nixos-homepage/pull/1762 please :) | 12:10:47 |
| mfrischknecht | infinisil: As discussed, if you could flag https://github.com/NixOS/nixpkgs/pull/390112 for a backport, that'd be great 🙂 | 12:33:59 |
| mfrischknecht | infinisil: And this one :) https://github.com/NixOS/nixpkgs/pull/410503 | 12:57:03 |
 Fabio Lenherr | Tremor-language-server: https://github.com/NixOS/nixpkgs/pull/410506
(updating was easier than fumbling with clang versions) | 13:01:04 |
