Sender | Message | Time |
---|---|---|
2 Dec 2024 | ||
19:59:30 | ||
8 Dec 2024 | ||
yes i guess you're right it shouldn't file that pr, my bad who/what sets | 16:33:32 | |
one more thing: i get pinged for jitsi updates, even though i'm not a maintainer since this got merged. any idea why? | 16:34:32 | |
19:21:35 | ||
9 Dec 2024 | ||
IIRC it is set by mkDerivation. You were pinged by the bot when it opened the PR but not in the next comment when it updated the PR? | 00:17:49 | |
ah sorry, i overlooked that the pr was created a long time ago, and only merged now. all good | 09:49:49 | |
10 Dec 2024 | ||
18:11:23 | ||
hey, we would want to automate updates of what would it take to run | 18:15:39 | |
(i am just asking for now) | 18:15:57 | |
* hey, we would want to automate updates of what would it take to run | 19:09:56 | |
https://nixpkgs-update-logs.nix-community.org/vimPluginsUpdater/ The bot has already picked up | 23:53:56 | |
| 23:54:12 | |
15 Dec 2024 | ||
is there any way to examine how quickly nixpkgs-update is making its way through the queue? (e.g. "~N items are processed per day, so (say) fflogs at position 5269 will be processed in ~M days") | 21:25:52 | |
16 Dec 2024 | ||
No, not at the moment. An approximate version of the queue is public, I'll probably get around to making it more accurate in the next few weeks, should be able to add "~N items are processed per day" at the same time. I don't think "will be processed in ~M days" is feasible, some days the bot may only process a few hundred updates, other days it will process thousands. | 00:22:55 | |
* No, not at the moment. An approximate version of the queue is public, I'll probably get around to making it more accurate in the next few weeks, should be able to add "~N items are processed per day" at the same time (and show 48 hours and a week as well). I don't think "will be processed in ~M days" is feasible, some days the bot may only process a few hundred updates, other days it will process thousands. | 00:25:01 | |
19 Dec 2024 | ||
07:48:00 | ||
Hello, I tried to use Thank you for your time! | 08:00:02 | |
* Hello, I tried to use Thank you for your time! | 08:05:31 | |
16:30:11 | ||
why this update didn't work (there is a new version since april)? running locally nix-update python312Packages.eval-type-backport workshttps://nixpkgs-update-logs.nix-community.org/python312Packages.eval-type-backport/2024-12-15.log | 17:49:34 | |
* why this update didn't work (there is a new version since april)? running locally EDIT: looks like this update causes some build failures, weird that it is not displayed in the log | 18:08:21 | |
20 Dec 2024 | ||
Sorry, I don't know what the problem is. nixpkgs-update isn't particularly easy to set up or use, I'd suggest nix-shell maintainers/scripts/update.nix or nix-update instead. | 04:47:20 | |
Not sure why but the package updateScript thinks the current version is the newest version. | 04:56:30 | |
Thanks a ton!, other methods do seem easy compared to nixpkgs-update. | 05:03:33 | |
* Thanks a ton! other methods do seem easy compared to nixpkgs-update. | 05:03:43 | |
In reply to @zowoq:matrix.orgIsn't it a bug? | 07:24:50 | |
It isn't a nixpkgs-update bug. | 09:27:36 | |
22 Dec 2024 | ||
04:58:13 | ||
23 Dec 2024 | ||
17:00:54 | ||
Is there any way to trigger r-ryantm bot manually if I know some package has a update recently? | 17:02:17 |