| 10 Dec 2025 |
|  @wolfgangwalther:matrix.org left the room. | 20:00:45 |
|  JManch joined the room. | 23:23:49 |
| 11 Dec 2025 |
|  zgypa (Toni Magni) joined the room. | 12:02:51 |
|  Toe Knee Magni joined the room. | 12:03:19 |
| Toe Knee Magni | Hi, i'm totally baffled as to the missing vscode-extensions.ms-python.autopep8package in the nixstore. I'm sure there has been a discussion on this, but i can't find out where.
Basically: why is it not there?
I apologize if this were to be out of topic, not exactly sure which the best room would be for this. You can just point me to whatever resource you know. | 12:07:50 |
| Toe Knee Magni | Hi, i'm totally baffled as to the missing `vscode-extensions.ms-python.autopep8`package in the nixstore. I'm sure there has been a discussion on this, but i can't find out where. https://search.nixos.org/packages?channel=25.11&query=ms-python.autopep8
Basically: why is it not there?
I apologize if this were to be out of topic, not exactly sure which the best room would be for this. You can just point me to whatever resource you know. | 12:08:26 |
 K900 | Why is what not where? | 13:04:45 |
| Toe Knee Magni | Why do we have the black-formatter vscode extension but not the autopep8 extension in the nixos packages? If you follow the link I sent it returns no results.
Has the community decided that that extension was not worth adding? And if so, is there a reason for that?
I’m trying to understand if I should spend time adding it myself: if it has been already decided by the community that it is not worth doing for some reason, then no point for me to waste time on it. And if that is the case, I would like to know what the reason is. | 13:19:44 |
| K900 | I don't think anyone decided on anything | 13:20:06 |
| K900 | You can just submit a PR adding it if you want to use it | 13:20:12 |
| K900 | There's also a repo with an automated index of vscode extensions at https://github.com/nix-community/nix-vscode-extensions | 13:20:40 |
| K900 | You can just pull it from there | 13:20:58 |
| Toe Knee Magni | Ah! That explains it. Thanks. | 13:23:35 |
| 19 Sep 2023 |
|  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 |
