| 10 Dec 2025 |
|  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 |
| 14 Dec 2025 |
|  bandithedoge joined the room. | 00:16:15 |
| 15 Dec 2025 |
 JacoMalan1 | Hey guys. Looks like nixpkgs-update got the wrong hash for a file somehow. Could this be a bug, or did the author of the software just screw with the files?
https://github.com/NixOS/nixpkgs/pull/470685 | 06:43:49 |
| 16 Dec 2025 |
|  @liljaylj:matrix.org joined the room. | 22:14:27 |
| @liljaylj:matrix.org left the room. | 22:18:08 |
| 17 Dec 2025 |
|  korken89 joined the room. | 09:27:44 |
|  datdenkikniet joined the room. | 09:28:17 |
| korken89 | Hi, I have moved a package to by-name but am unable to get r-ryantm to rebase it such that I can then merge it. Does anyone know what the process to follow here is? I've pinata-d the bot(s) with different commands but nothing initiates a rebase. https://github.com/NixOS/nixpkgs/pull/458106 | 09:29:45 |
 jopejoe1 | The bot currently does not support rebasing, the solutions would be to ask a commiter to rebase it, open a new pr your self or close the pr and hope that the bot creates a new pr in a reasonable time frame. | 11:11:03 |
| 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 |
