28 Jun 2024 |
| @raf:notashelf.dev left the room. | 07:47:46 |
| @d:bugpara.de joined the room. | 11:48:57 |
29 Jun 2024 |
| coolshaurya joined the room. | 03:42:07 |
30 Jun 2024 |
| @rayne:spooky.computer joined the room. | 01:23:10 |
| flameopathic set a profile picture. | 14:28:52 |
| flameopathic removed their profile picture. | 14:29:02 |
| flameopathic set a profile picture. | 14:32:16 |
| flameopathic changed their display name from flameopathic to Flameopathic. | 14:32:41 |
| flameopathic changed their display name from Flameopathic to flameopathic. | 14:32:59 |
1 Jul 2024 |
| @isker:matrix.org joined the room. | 05:54:11 |
| @jalr:jalr.de left the room. | 11:06:13 |
2 Jul 2024 |
| @liketechnik:matrix.im left the room. | 17:14:20 |
flyx | if my flake has nixpkgs as input with url github:NixOS/nixpkgs/nixos-24.05 , shouldn't nix flake lock --update-input nixpkgs update it to the latest commit on the nixos-24.05 branch? because it doesn't; my flake.lock shows that afterwards nixpkgs is on a commit from May 20 when the branch has been updated yesterday. | 18:32:36 |
| @isker:matrix.org left the room. | 18:41:27 |
emily | This command adds inputs to the lock file of a flake (flake.lock) so
that it contains a lock for every flake input specified in flake.nix.
Existing lock file entries are not updated.
If you want to update existing lock entries, use nix flake update
| 18:42:42 |
emily | oh, I guess it used to be able to do that? | 18:42:54 |
emily | does nix flake update nixpkgs work? | 18:43:02 |
emily | (might be a Nix version thing…) | 18:43:11 |
flyx | trying… would be funny, because a reference to another flake did update with that | 18:43:58 |
flyx | nix flake update nixpkgs works longer, but also doesn't update the rev in the lock file | 18:46:02 |
emily | does nix flake update without any parameters make a difference? if not, can you post your flake.nix maybe? | 18:47:04 |
flyx | nix flake update does update other referenced flakes, but not nixpkgs. my flake is a longer business, here's the inputs section:
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-24.05";
nixpkgs-unstable.url = "github:NixOS/nixpkgs/nixos-unstable";
utils.url = "github:numtide/flake-utils";
home-manager = {
url = "github:nix-community/home-manager/release-24.05";
};
colmena = {
url = "github:zhaofengli/colmena/v0.3.2";
inputs.utils.follows = "utils";
};
dsa41heldendokument = {
url = "github:flyx/DSA-4.1-Heldendokument";
inputs.nixpkgs.follows = "nixpkgs";
inputs.utils.follows = "utils";
};
nimyaml = {
url = "github:flyx/NimYAML";
inputs.utils.follows = "utils";
};
nyarna-web = { url = "github:nyarnalang/website"; };
};
| 18:50:06 |
emily | are you sure it's not that there are other nixpkgs inputs in your dependencies that you're not overriding and that aren't getting updated? | 18:51:09 |
emily | often you'll have e.g. nixpkgs_2 etc. in the lock | 18:51:19 |
flyx | ah, that makes sense. yeah, I looked at the wrong nixpkgs , silly. thanks! | 18:56:04 |
flyx | my original problem was that after the update, I wouldn't get a patched OpenSSH on my server, so I tried to figure out why that would be as it should be in nixos-24.05 . the lock file apparently was the wrong place to look for the problem | 18:56:30 |
emily | are you sure it's not patched? | 19:04:44 |
emily | the version wasn't bumped or anything | 19:04:47 |
emily | (yes, this means it's kind of hard to tell whether you're vulnerable, sorry; it was a big rush) | 19:05:07 |
| @mewp:nurupo.pl left the room. | 19:05:12 |