| 28 Oct 2025 |
 kuflierl | https://nixpkgs-update-logs.nix-community.org/~supervisor/queue.html | 12:16:19 |
 hexa | oh, that exists? TIL | 12:16:39 |
 tnias | Last time I waited for something it was around 2000/day | 12:20:11 |
 ivy | so about a week 💀 | 12:43:47 |
| ivy | why on earth are packages which don't have updates like further up in the queue than ones that do have clear updates? | 12:45:57 |
 Sandro 🐧 | If you want an update faster, you can always open a PR. There is no requirement to use the bot. | 12:46:02 |
| Sandro 🐧 | probably because it is not a smart queue considering things but just going through it | 12:46:31 |
| ivy | i know but i wanna test if it even works on my script (i do use it to update on my own) and for some reason my own prs don't get marked as by maintainer | 12:46:42 |
| kuflierl | But it also generally takes ages for the PR to geht merged to the point that its probably faster to merge it yourself After the bot is done with it | 12:47:12 |
| ivy | yeah that's my intention | 12:47:26 |
| ivy | just want the pr to like "exist" so i can run merge command | 12:48:05 |
| ivy | without having to deal with having a committer go yeah ur the maintainer no shit, but it doesn't even mark me as the maintainer on my prs | 12:48:45 |
 loudgolem | if you are a maintainer you can edit labels | 12:49:13 |
| ivy | i did | 12:49:19 |
| kuflierl | In reply to @ivy:faggot.sh
without having to deal with having a committer go yeah ur the maintainer no shit, but it doesn't even mark me as the maintainer on my prs Thats... Strange | 12:49:19 |
| ivy | then the bot removed it | 12:49:22 |
 K900 | Do you have a link to the PR? | 12:49:30 |
| ivy | https://github.com/NixOS/nixpkgs/pull/456375 i did delete it tho cause i was getting fed up | 12:49:51 |
| ivy | it just kept going no you arent the maintainer, like yes i am | 12:51:41 |
| ivy | if i re open it will it make the bot not attempt to make a pr? | 12:52:41 |
| K900 | @wolfgangwalther:matrix.org any idea why it would do that? | 12:55:07 |
| kuflierl | On a completely different note, i noticed that in my latest PR nix-update seems to update the Go Derivation hash but seems to use the generated hash for the peotobuf Derivation.
https://github.com/NixOS/nixpkgs/pull/456029
How to reproduce:
- check out PR and go back a commit before the update but after the fix.
- run: nix-update -u memos
| 12:55:27 |
| kuflierl | * On a completely different note, i noticed that in my latest PR nix-update seems to update the Go Derivation hash but seems to use the generated hash for the Protobuf Derivation.
https://github.com/NixOS/nixpkgs/pull/456029
How to reproduce:
- check out PR and go back a commit before the update but after the fix.
- run: nix-update -u memos
| 12:55:43 |
| kuflierl | * On a completely different note, i noticed that in my latest PR nix-update seems to update the Go Derivation hash but seems to use the generated hash for the Protobuf Derivation.
https://github.com/NixOS/nixpkgs/pull/456029
How to reproduce:
- check out PR and go back a commit before the update but after the fix.
- run: nix-update -u memos
- observe the diff to my last commit
| 12:57:07 |
| ivy | okay now its saying maintainer!?!?! | 12:58:49 |
| ivy | whattt | 12:58:51 |
| ivy | why didn't it before!?!?!? | 12:59:27 |
| ivy | Wolfgang Walther: thoughts? | 12:59:50 |
 Wolfgang Walther | I looked into this earlier and I expected the label to show up the next time CI would run there. This must have been GitHub returning a wrong (or no) user ID for the PR from their API - all other code looks fine. | 13:01:34 |
| Wolfgang Walther | Also note that the label currently does not matter at all for whether you can merge with the merge bot or not. | 13:01:49 |
