| 2 Jul 2025 |
 sorrel | question: is r-ryantm meant to be able to update existing PRs if a new upstream version is released? (i.e. if r-ryantm opens "A -> B", then upstream releases C, should r-ryantm change that PR to "A -> C"?) | 11:16:28 |
| sorrel | I ask because I thought I'd observed it doing that previously, but it failed to do so in https://github.com/NixOS/nixpkgs/pull/412461#issuecomment-3013733328 | 11:16:50 |
 kuflierl | As far as I remember, a PR is only ignored if the string "x.x -> y.y" matches. That means it should create the new pr | 11:18:07 |
| 6 Jul 2025 |
|  JamieMagee joined the room. | 02:29:58 |
|  Cathal changed their display name from CJ to Cathal. | 17:17:29 |
| 9 Jul 2025 |
|  jonhermansen joined the room. | 01:17:22 |
| 19 Jul 2025 |
|  sorimaxuki joined the room. | 00:10:09 |
| 21 Jul 2025 |
 hexa | asymmetric: I tried following my github handle on your bot and it stopped responding 🫣 | 20:05:34 |
| hexa | after 6 minutes it returned with
There was a problem processing your request, sorry.
| 20:06:52 |
| kuflierl | In reply to @hexa:lossy.network
asymmetric: I tried following my github handle on your bot and it stopped responding 🫣 Same issue here as well but without the timeout message | 20:10:11 |
| hexa | fwiw the bot is https://github.com/asymmetric/nixpkgs-update-notifier | 20:10:33 |
| kuflierl | Correction: it seems to answer my requests to list my subscriptions but doesn't allow me to subscribe to any other packages | 20:13:21 |
| kuflierl | * Correction: it seems to answer my requests to list my subscriptions but doesn't allow me to subscribe to any other packages and also doesn't answer | 20:13:39 |
| kuflierl | * Correction: it seems to answer my requests to list my subscriptions now but doesn't allow me to subscribe to any other packages and also doesn't answer | 20:13:54 |
 asymmetric | kuflierlhexathanks for the report, I’ll take a look | 20:15:57 |
| 22 Jul 2025 |
|  JacoMalan1 joined the room. | 08:32:34 |
| asymmetric | kuflierl: hexa the follow/unfollow issue should be fixed 🙂 | 20:00:56 |
| hexa | yup, I already subbed to all my packages, thx | 20:01:11 |
| asymmetric | hexa: due to the amount of packages you maintain, the bot is hitting this issue 😉 | 20:01:14 |
| hexa | 🙂 | 20:01:19 |
| hexa | that one issue that will never be fixed | 20:01:34 |
| hexa | loving it | 20:01:35 |
| hexa | might want to escape package names with backticks, if possible | 20:01:56 |
| hexa | 
Download image.png | 20:02:34 |
| hexa | also, does it update the list over time? | 20:02:55 |
| asymmetric | no, not atm. a new follow will sub to any newly maintained packages, but won't remove any. need to work on proper sync/reconciliation at some point 😅 | 20:27:05 |
| asymmetric | ok now it handles cases with lots of subs/unsubs more gracefully:
- prints something if
M_TOO_LARGE happens
- notifies user if a follow is taking > 10s
| 21:00:54 |
 Sandro 🐧 | same yesterday. Now it seems to work somewhat. | 21:27:01 |
| 23 Jul 2025 |
| kuflierl | Alright, it also works for me now | 09:08:39 |
| JacoMalan1 | Is there a way to manually have r-ryantm create a PR for a package update, or do you need to wait for the package to bubble up to the top of the queue? Also, how long does it usually take for a package update ? | 11:52:43 |
