| 15 Nov 2024 |
| hausken joined the room. | 05:19:46 |
| 19 Nov 2024 |
| oliver.falvai joined the room. | 08:13:31 |
| 20 Nov 2024 |
| Inayet removed their profile picture. | 00:59:06 |
asymmetric | In reply to @zowoq:matrix.org r-ryantm is fine but it is throttled because of the load on ofborg. what's the relationship between r-ryantm and ofborg? like, why does high load on ofborg result in r-ryantm being throttled? | 22:06:20 |
asymmetric | are they running on the same infra? | 22:06:57 |
| 21 Nov 2024 |
zowoq | No, they don't run on the same infra. It gets throttled to keep the PR eval queue wait time reasonable, unfortunately ofborg seems to be kinda broken at the moment and the eval queue just keeps getting worse. Ofborg is being replaced with github actions so hopefully won't need to throttle it. https://github.com/NixOS/nixpkgs/issues/355847 | 02:18:11 |
| karlericsson joined the room. | 10:27:01 |
| 22 Nov 2024 |
| Morgan (@numinit) joined the room. | 17:49:25 |
| 25 Nov 2024 |
asymmetric | looking at this, it seems like the package that's printed in the logs is [generic.nix]( https://github.com/NixOS/nixpkgs /tree/master/pkgs/data/sgml+xml/schemas/xml-dtd/docbook/generic.nix) rather than [4.5.nix]( https://github.com/NixOS/nixpkgs /tree/master/pkgs/data/sgml+xml/schemas/xml-dtd/docbook/4.5.nix), which imports it. is that a bug? | 12:19:45 |
asymmetric | * looking at this, it seems like the package that's printed in the logs is generic.nix rather than [4.5.nix]( https://github.com/NixOS/nixpkgs/tree/master/pkgs/data/sgml+xml/schemas/xml-dtd/docbook/4.5.nix), which imports it. is that a bug? | 12:20:08 |
asymmetric | * looking at this, it seems like the package that's printed in the logs is generic.nix rather than 4.5.nix, which imports it. is that a bug? | 12:20:19 |
asymmetric | * looking at this, it seems like the package that's printed in the logs is generic.nix rather than 4.5.nix, which imports it.
then nixpkgs-update can't find 4.5 in the package, and doesn't file an update PR to 5.1.
is that a bug?
| 12:20:58 |
| 26 Nov 2024 |
zowoq | It looks in generic.nix because of meta.position:
❯ EDITOR=echo nix edit -f. docbook_xml_dtd_45
/home/zowoq/src/nixpkgs/pkgs/data/sgml+xml/schemas/xml-dtd/docbook/generic.nix
doesn't file an update PR to 5.1.
Sorry, I don't understand this. If the bot did file that PR, wouldn't it be incorrect?
| 04:16:53 |
| 27 Nov 2024 |
| jopejoe1 (4094@39c3) changed their display name from jopejoe1 to jopejoe1 [4094]. | 18:17:37 |
| 1 Dec 2024 |
| shawn8901 left the room. | 00:10:18 |
| shawn8901 joined the room. | 00:10:55 |
| codgician joined the room. | 08:33:26 |
| 2 Dec 2024 |
| dish [Fox/It/She] changed their profile picture. | 19:59:30 |
| 8 Dec 2024 |
asymmetric | yes i guess you're right it shouldn't file that pr, my bad
who/what sets meta.position? i couldn't find mention of it in meta.chapter.md or lib/meta.nix
| 16:33:32 |
asymmetric | 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 |
| shawn8901 set a profile picture. | 19:21:35 |
| 9 Dec 2024 |
zowoq | 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 |
asymmetric | 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 |
| Perchun Pak [don't ping; dm instead] joined the room. | 18:11:23 |
Perchun Pak [don't ping; dm instead] | hey, we would want to automate updates of vimPlugins.*. we already have a script that does that and after https://github.com/NixOS/nixpkgs/pull/364001 it can be run by a bot
what would it take to run nix-build -A vimPluginsUpdater && ./result/bin/vim-plugins-updater update using r-ryantm every month?
| 18:15:39 |
Perchun Pak [don't ping; dm instead] | (i am just asking for now) | 18:15:57 |
Perchun Pak [don't ping; dm instead] | * hey, we would want to automate updates of vimPlugins.*. we already have a script that does that and it can be run by a bot
what would it take to run nix-build -A vimPluginsUpdater && ./result/bin/vim-plugins-updater update using r-ryantm every month?
| 19:09:56 |
zowoq | https://nixpkgs-update-logs.nix-community.org/vimPluginsUpdater/
The bot has already picked up vimPluginsUpdater because it is python which has a default updateScript, need to change it so it uses itself as the updateScript and pass the update command. The bot is running other package updates in parallel so would be good to not saturate the connection to github. Because of ofborg problems updates have been slow for the last couple of months, once the backlog clears it'll be running every week, approximately.
| 23:53:56 |
zowoq | diff --git a/pkgs/applications/editors/vim/plugins/updater.nix b/pkgs/applications/editors/vim/plugins/updater.nix
index 41413a5b4c66..8f04ecc8f0dd 100644
--- a/pkgs/applications/editors/vim/plugins/updater.nix
+++ b/pkgs/applications/editors/vim/plugins/updater.nix
@@ -9,6 +9,9 @@
# optional
neovim-unwrapped,
+
+ writeShellScript,
+ vimPluginsUpdater,
}:
buildPythonApplication {
pname = "vim-plugins-updater";
@@ -49,4 +52,9 @@ buildPythonApplication {
'';
meta.mainProgram = "vim-plugins-updater";
+
+ passthru.updateScript = writeShellScript "updateScript" ''
+ # don't saturate the update bot connection
+ ${lib.getExe vimPluginsUpdater} --proc 2 update
+ '';
}
| 23:54:12 |
| 15 Dec 2024 |
sorrel | 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 |