17 Aug 2023 |
| @bangzek:matrix.org left the room. | 02:00:47 |
K900 | Heads up, nixpkgs-update from master doesn't build with the latest nixpkgs | 14:47:48 |
K900 | nixpkgs-update> src/Version.hs:16:36: error:
nixpkgs-update> Module ‘Data.Versions’ does not export ‘VUnit(..)’
nixpkgs-update> |
nixpkgs-update> 16 | import Data.Versions (SemVer (..), VUnit (..), semver) | 14:48:04 |
19 Aug 2023 |
| theoretical-types joined the room. | 12:47:08 |
20 Aug 2023 |
| abstract-logic-tree joined the room. | 20:41:31 |
8 Sep 2023 |
| @ulli:hrnz.li left the room. | 20:43:27 |
19 Sep 2023 |
raitobezarius | Hi there | 16:12:17 |
raitobezarius | I would like to enable automatic kernel upgrades PRs with nixpkgs-update | 16:12:27 |
raitobezarius | The problem is that we have a lot of kernels and I think it may be good to keep them upgraded at the same time in the same PR | 16:12:38 |
raitobezarius | I know there is updateScript but I am not sure if there is a more global option to say "do upgrade on all of them and open the PR only if all of them succeeded the upgrade" ? | 16:12:56 |
vcunat | In one PR just because of the number of PRs? Or because the updates will de-facto share lots of diffs within the upstream changes. | 16:14:34 |
| evils joined the room. | 16:15:20 |
ryantm | raitobezarius: No, not really. It's been an idea for a long time to have grouped package updates like that, but it hasn't been implemented. | 16:52:21 |
evils | hi, second link in the channel topic is dead | 19:21:58 |
evils | is there a way to see what packages the bot tried to update but failed on? | 19:22:23 |
Artturin | In reply to @evils:nixos.dev is there a way to see what packages the bot tried to update but failed on? https://r.ryantm.com/log/ | 19:23:49 |
Artturin | https://ryantm.github.io/nixpkgs-update/nixpkgs-maintainer-faq/#nixpkgs-maintainer-faq | 19:23:56 |
Artturin | * from https://ryantm.github.io/nixpkgs-update/nixpkgs-maintainer-faq/#nixpkgs-maintainer-faq | 19:23:58 |
evils | Download image.png | 19:24:43 |
evils | oof that's a subtle link underline | 19:24:50 |
evils | (i was looking at the page :) | 19:25:02 |
Artturin | yeah | 19:26:15 |
evils | ok, why do all KiCad update attempts end in "Do not update GNOME during a release cycle"? | 19:30:21 |
ryantm |
| 19:44:27 |
ryantm | * [ryantm@replit1:~/p/nixpkgs]$ EDITOR=echo nix edit -f . kicad
/home/ryantm/p/nixpkgs/pkgs/applications/science/electronics/kicad/default.nix
[ryantm@replit1:~/p/nixpkgs]$ cat /home/ryantm/p/nixpkgs/pkgs/applications/science/electronics/kicad/default.nix | grep gnome
, gnome
"--prefix XDG_DATA_DIRS : ${gnome.adwaita-icon-theme}/share" | 19:44:32 |
Artturin | the check here is wrong https://github.com/ryantm/nixpkgs-update/blob/8fedf8f6f29280578e335bf4483c9f88d4bcdbaa/src/Skiplist.hs#L151 | 19:45:39 |
Artturin | just a naive grep | 19:45:49 |
Artturin | maybe a better way would be to check for teams.gnome.members | 19:47:29 |
Artturin | still has false positives but way less | 19:47:37 |
ryantm | https://github.com/ryantm/nixpkgs-update/commit/2fda8bcb73776c3e11c0155fa15e138a71e1f189 | 19:49:37 |