Discussion
Loading...

Post

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Klaus Frank
@agowa338@chaos.social  ·  activity timestamp yesterday

#NixOS is deterministic they said.

Praxis:

Changing "programs.kdeconnect.enable = true;" to "programs.kdeconnect.enable = false;"

and being pleased with a gtk3 compile error on "nixos-rebuild switch".

Can anyone explain what happened?!?

https://privatebin.net/?47e05363f0bc074b#D11Nu8EZ6xYRBXjeT8rpXafNT3jHTTBbh8tvGn86EXmH

2
  • Copy link
  • Flag this post
  • Block
A.B. Murrow
@abmurrow@hachyderm.io replied  ·  activity timestamp 24 hours ago

@agowa338 I've seen this happen a time or two when upgrading the system, but for stuff like Firefox. I run the unstable channel, so this does happen sometimes.

Do you use configuration.nix or a flake?

If it's the former, I'd expect that the upstream channel had an update for a package, and that package wasn't cached, so you had to build it locally, but the update was bad, so the build failed.

If you use a flake, you can have the same thing happen after a 'nix flake upgrade' and make all of your packages repin to the newest version.

Sometimes you rebuild at juuust the wrong time and catch a package from nixpks in a broken state that is in the process of being patched.

There is a zero build failures campaign on right now to clean up the nixpkgs code base in preparation for the 25.11 release, so people are actively making lots of changes to the code.

  • Copy link
  • Flag this comment
  • Block
Klaus Frank
@agowa338@chaos.social replied  ·  activity timestamp yesterday

Wait, I didn't even save the change.

So this was ran without any changes to the configuration.nix.

Double WTF?!?

  • Copy link
  • Flag this comment
  • Block
Log in

Kakapo Social

Kakapo Social: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.0 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login