| 7 Feb 2024 |
 raitobezarius | Redacted or Malformed Event | 20:01:35 |
 TWIN | ✅ Thanks for the report raitobezarius, I'll store your update! | 20:01:36 |
| TWIN | Whoops there has been an error. | 20:01:39 |
| TWIN | Check the log for details. | 20:01:39 |
| raitobezarius | 🫠 | 20:02:16 |
| raitobezarius | Redacted or Malformed Event | 20:04:04 |
| TWIN | ❌ raitobezarius: Your update is too short and was not stored. This limitation was set-up to limit spam. | 20:04:05 |
| TWIN | ❌ raitobezarius: Your update is too short and was not stored. This limitation was set-up to limit spam. | 20:04:08 |
| TWIN | Whoops there has been an error. | 20:04:09 |
| TWIN | Check the log for details. | 20:04:09 |
| raitobezarius | It's convinced that it's PL50… | 20:04:21 |
| raitobezarius | * It's convinced that it's PL0… | 20:04:24 |
| raitobezarius | so sorry I may have gotten the room wrong | 20:04:29 |
| raitobezarius | target room is !EkIttzQthkJjeZNAnb:matrix.org | 20:04:43 |
| raitobezarius | hexa: you can demote actually the bot here | 20:05:01 |
| raitobezarius | Redacted or Malformed Event | 20:05:26 |
| TWIN | ❌ raitobezarius: Your update is too short and was not stored. This limitation was set-up to limit spam. | 20:05:27 |
| TWIN | ❌ raitobezarius: Your update is too short and was not stored. This limitation was set-up to limit spam. | 20:05:33 |
| TWIN | 20:06:27 |
| raitobezarius | ok now this is fixed, all that remains is to fix the sync event spec violation in conduit or matrix-nio | 20:06:33 |
| raitobezarius | hexa: we are ready for an experimentation phase now | 20:09:11 |
| raitobezarius | the sync event fix does not appear to me important | 20:09:26 |
| raitobezarius | In reply to @hexa:lossy.network
TWIN: Dependency validation for Python Package will be restored after the next staging cycle on master. We expect a few breakages here and there, but clear error messages will be provided!
For missing propagatedBuildInputs you'll see
Checking runtime dependencies for pysml-0.1.1-py3-none-any.whl
- aiohttp not installed
and for violated version constraints
Checking runtime dependencies for sphinx_prompt-1.6.0-py3-none-any.whl
- sphinx==7.0.0 not satisfied by version 7.2.6
Use pythonRelaxDepsHook to relax version constraints on dependencies, or bump dependencies as needed!
do you want to try to resend this ^ or something else? | 20:16:31 |
|  @twin:the-apothecary.club left the room. | 20:17:00 |
 @hexa:lossy.network | I think that has landed like a month ago 😄 | 20:17:22 |
| @hexa:lossy.network | I have to think of new things | 20:17:29 |
| raitobezarius | :D | 20:17:35 |
| raitobezarius | I will draft a Discourse post to get attention | 20:17:49 |
| raitobezarius | https://discourse.nixos.org/t/call-for-testing-this-week-in-nixos/39465 | 22:04:02 |
| raitobezarius | TWIN: This week, sparked from a discussion to prompt the removal of scripted initrd networking where a call for feedback has been made in https://discourse.nixos.org/t/seeking-feedback-on-the-removal-of-scripted-initrd-networking-in-nixos/39457, we discussed with contributors in #dev:nixos.org at message https://matrix.to/#/!kjdutkOsheZdjqYmqp:nixos.org/$6e30z5pwbKIKXLTHs1eZwWkddMNrXgyoYc5NEIsW5zA?via=nixos.org&via=matrix.org&via=nixos.dev
A summary is that we notice that we don't have formal policies for deprecations in nixpkgs, we do not want to discuss tools or implementations of such things as we know plenty of them: RFC127 (unimplemented), NixOS module systems, lib.warn and more. We would like to focus and steer things towards a policy, we described our state of knowledge in https://pad.lassul.us/nixos-deprecation-cycle-theory.
Once we collect enough, we will move to a proposal in a PR and enact such a policy with the approval of contributors.
| 22:17:56 |
