| 12 Nov 2025 |
 Grimmauld (migrated to @grimmauld:m.grimmauld.de) | Uhm. We might have a problem. | 11:06:04 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | Software decoding is broken on librewolf on this staging-next cycle, it lost h264/hevc/aac | 11:06:37 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | i suspect the same applies to firefox, though hydra did not build that yet | 11:06:55 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | I'll poke a ff build on staging-next, but this is a bit of a yikes | 11:07:16 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | Oh wait hydra did actually build 145 on staging-next already, that is convenient | 11:09:50 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | Yep! Applies to firefox too! cc @hex | 11:11:15 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | 
Download image.png | 11:11:15 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | Yep! Applies to firefox too! cc @hexa | 11:11:28 |
 hexa | ffmpeg 8 update? | 11:12:04 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | Probably | 11:12:10 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | you want me to poke a build against ffmpeg 7? | 11:12:25 |
| hexa | if you can that'd be super, I'm on my way to family | 11:12:59 |
| hexa | https://bugzilla.mozilla.org/show_bug.cgi?id=1962139 | 11:19:25 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | Hmm, i don't even see where it pulls ffmpeg. its not in buildMozillaMach buildInputs, yet nix why-depends says it is there | 11:22:02 |
| hexa | wrapper | 11:22:14 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | Ah that makes sense | 11:22:51 |
| hexa | https://github.com/NixOS/nixpkgs/pull/460904 | 11:23:37 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | Yep, pinning back to ffmpeg_7 does work | 11:25:41 |
|  Inayet changed their display name from inayet to Inayet. | 12:38:31 |
 Vladimír Čunát | I think we just merge staging-next today? | 15:07:13 |
| Vladimír Čunát | The "cachix on darwin" problem hasn't been resolved yet; I haven't even seen any reaction from the relevant pinged people. But nixos-unstable is linux-only, so I think we can proceed with that one. nixpkgs-unstable would be blocked, but I'd hope that within another day or two the problem would get resolved somehow (while Hydra processes the aftermath of the merge). | 15:07:16 |
 leona | IMHO please, yes. | 15:09:31 |
 @wolfgangwalther:matrix.org | I agree on not blocking on it given there has been no reaction. We'll not be affected by it in CI, because we're not using cachix from Nixpkgs. | 15:09:54 |
| Vladimír Čunát | staging-next + staging-nixos merged a while ago. | 18:22:26 |
 Fabián Heredia | As a heads up for current nixos unstable/staging-next: https://github.com/NixOS/nixpkgs/pull/458944
Versions 2.4.126 and 2.4.127 contain an ABI breakage in libdrm_amdgpu.
Depending on which Mesa version or commit you use, you may see stack
smashing resulting in crashes of AMD Mesa drivers. It's recommended to never package versions 2.4.126 and 2.4.127.
libdrm 2.4.127 is currently on unstable+staging-next
| 20:21:08 |
| Fabián Heredia | 25.05 is currently on 2.4.124, going to backport all updates | 20:23:10 |
 K900 | Absolutely do not | 20:23:32 |
| Fabián Heredia | :O | 20:23:43 |
| K900 | We may not even have a staging-25.05 | 20:23:47 |
| K900 | And backporting 6 months of libdrm updates will definitely not go well | 20:23:57 |
