| 15 Feb 2024 |
|  a-kenji joined the room. | 19:16:00 |
| 25 Feb 2024 |
|  Simon Menke set a profile picture. | 15:25:57 |
| 27 Feb 2024 |
|  Jeremy Fleischman (jfly) joined the room. | 04:52:43 |
| Jeremy Fleischman (jfly) | As a maintainer of a package on nixpkgs, what should I be doing to ensure that nixpkgs-update can keep my package up to date? I guess I had expected it would create PRs even if the build is failing, and it would be my job to fix those PRs. evils recently explained that that's not the case, and reading the code, I believe they're right.
Should I just be periodically running a command like nix-shell maintainers/scripts/update.nix --argstr maintainer jfly to make sure my packages are staying fresh?
| 04:59:09 |
 evils | ha, was considering pinging you here :) | 05:00:07 |
| evils | * ha, was considering pinging you here :)
i'd also love to know if there's a way to be informed | 05:15:48 |
 Mindavi | Subscribe to the GitHub releases rss feeds :) | 10:29:14 |
| Mindavi | Oh whatever they use as a release platform | 10:29:26 |
| 28 Feb 2024 |
 hexa | repology provides a per maintainer rss feed | 08:55:47 |
| Jeremy Fleischman (jfly) | hmm... GitHub releases and repology don't feel actionable to me. If I get a notification from repology about a new version of some package, shouldn't I still wait (a day? two?) for nixpkgs-update to post a PR? | 09:05:07 |
| Mindavi | Depends on how lazy you want to be :), you don't need to depend on the bot. But I understand that you'd rather only get pinged on success or issues instead of for each release. | 10:33:51 |
| Jeremy Fleischman (jfly) | Is this a feature that nixpks-update would be open to? I could imagine it creating a PR (perhaps in draft mode) and pinging the maintainers. | 17:59:43 |
| 29 Feb 2024 |
| hexa | 
Download image.png | 12:40:09 |
| hexa | 
Download image.png | 12:40:16 |
| hexa | kinda two PRs for the same package | 12:40:27 |
| 8 Mar 2024 |
|  Guilhem joined the room. | 16:50:39 |
| 14 Mar 2024 |
|  Federico Damián Schonborn left the room. | 02:04:49 |
|  NixOS Moderation Botchanged room power levels. | 18:45:32 |
| 16 Mar 2024 |
|  @grahamc:nixos.org joined the room. | 00:00:13 |
| 18 Mar 2024 |
|  benjaminedwardwebb joined the room. | 22:54:19 |
| 19 Mar 2024 |
| NixOS Moderation Botchanged room power levels. | 00:30:56 |
| 21 Mar 2024 |
| NixOS Moderation Botchanged room power levels. | 18:03:47 |
| @grahamc:nixos.org left the room. | 20:07:44 |
| 24 Mar 2024 |
|  admin (Moderation Team) joined the room. | 01:57:15 |
| admin (Moderation Team) set the room name to "nixpkgs-update". | 01:57:25 |
| admin (Moderation Team) left the room. | 01:57:33 |
| 26 Mar 2024 |
|  cblacktech joined the room. | 02:03:39 |
| 29 Mar 2024 |
|  SebTM joined the room. | 05:40:06 |
| 30 Mar 2024 |
|  szlend joined the room. | 18:45:34 |
| szlend | Is there any way to check why a package is not being picked up by r-ryantm at all? It's not on the skiplist from what I can tell, and there are no logs created for it | 18:47:04 |
