| 8 Nov 2023 |
 hexa | 
Download image.png | 00:00:42 |
| hexa | 😱 | 00:00:45 |
 raitobezarius | Should I click the button sir | 00:00:54 |
| hexa | nooouuuu | 00:00:58 |
| raitobezarius | You already have enouf on the plate | 00:01:01 |
| hexa | there was someone fixing some big python library for i686-linux, that was marked broken since 2017 | 00:01:27 |
| raitobezarius | I don't think someone is enough to be frank | 00:01:42 |
| raitobezarius | I would be willing to put efforts setting nixpkgs-i686 out of tree | 00:01:54 |
| hexa | I think it was pandas | 00:01:58 |
| raitobezarius | Wow | 00:02:07 |
| raitobezarius | If we have 5-6 serious folks around for i686, of course, that's another story | 00:02:14 |
| hexa | was misuzu | 00:02:22 |
| hexa | oh, no | 00:02:29 |
| hexa | this was about armv7, so just 32bit | 00:02:34 |
| raitobezarius | misuzu is usually armv7l person | 00:02:40 |
| raitobezarius | I think the 32 bits interest is dying to be fair | 00:02:51 |
| raitobezarius | on x86 | 00:02:53 |
| hexa | yeah, just wine | 00:02:57 |
| raitobezarius | Kernel security updates are not performed anymore | 00:02:59 |
| hexa | * yeah, just wine/steam | 00:03:07 |
| raitobezarius | I don't think it's responsible to let people believe it can be used for more than wine/steam or retrocomputing | 00:03:14 |
| hexa | hydra is currently incapacitated | 16:55:20 |
| hexa | which will certainly cause some delay | 16:55:40 |
| 9 Nov 2023 |
| hexa |
FoundationDB now defaults to major version 7.
| 00:25:17 |
| hexa | who here has used or knows what that is? It's listed as a highlight 🙂 | 00:25:37 |
| hexa | * who here has used this or knows what that is? It's listed as a highlight 🙂 | 01:30:59 |
|  Randy Eckenrode joined the room. | 15:03:42 |
| Randy Eckenrode | I was directed here from the Staging channel. I’ve got question about how LLVM update for Darwin fits into the release process. I know Darwin isn’t a tier 1 platform, but I don’t know what amount of breakage is expected or tolerated.
- Is there a point at which it should be reverted to reduce the breakage on staging-next; or
- Is there a threshold (such as less than X dependents) where stuff can be allowed through broken on Darwin (perhaps marked en masse on the release branch) and fixed with backports?
| 15:14:15 |
| raitobezarius | (a shame we didn't get a Darwin release manager :>) | 15:32:23 |
| raitobezarius | Personally, I have no idea and no real opinion, I don't know what is the type of software people tend to use on Darwin with Nix, if I had to say anything:
- someone who cares about Darwin has to make the call for the reverts on staging-next based on their time, expected folks who will help on Darwin fixes, etc.
- the threshold thing seems weird to me, I would pursue a set of leaf packages that you always want to work in general (or is required for channel bump for example).
- I'd generally move any large scale changes to after the release otherwise chances are that you will slip and it will be hard to fix things with all the backports you need
| 15:36:13 |
