| 6 Mar 2025 |
 🐰 xiaoxiangmoe | * https://nixpkgs-update-logs.nix-community.org/~supervisor/queue.html
https://nixpkgs-update-logs.nix-community.org/notion-app/
notion-app is created on Jan 30, but never trigged by update-bot. Is there anyway to trigger it manually? | 12:50:44 |
| 🐰 xiaoxiangmoe | https://github.com/NixOS/nixpkgs/pull/376125 | 12:50:52 |
 linj | maybe the bot ignores unfree pkgs? | 12:54:49 |
| 🐰 xiaoxiangmoe | No | 12:55:38 |
| 🐰 xiaoxiangmoe | https://r.ryantm.com/log/the-unarchiver/ | 12:55:39 |
| 🐰 xiaoxiangmoe | this is another unfree software, but not ignored by bot | 12:56:09 |
| 🐰 xiaoxiangmoe | Every commit created by maintainer can't merged by merge-bot, so I think I need some mechanics to trigger update-bot manually. | 12:58:40 |
| 8 Mar 2025 |
|  Sigmanificient joined the room. | 23:06:44 |
| 9 Mar 2025 |
|  Anton joined the room. | 15:33:07 |
 sorrel | the answer to this, I think: the fflogs derivation no longer works for the latest fflogs version, and nixpkgs-update is unhelpfully printing a message about unfreeness rather than The Actual Error Message. fixing the derivation then running nixpkgs-update locally works juuuust fine. | 17:14:19 |
| 11 Mar 2025 |
|  emily joined the room. | 19:59:25 |
| 12 Mar 2025 |
|  vidariondr joined the room. | 21:10:06 |
| 17 Mar 2025 |
|  egrieco joined the room. | 06:47:52 |
| Anton | Am I interpreting the logs correctly, that aerc's updateScript has been executed by r-ryantm 5 times in 2025 with those ~14 days between each execution? Or are there additional attempts not being logged? | 16:31:12 |
 hexa | all attempts get logged | 20:21:21 |
| Anton | Thanks! I was wondering about the frequency of attempts. | 20:55:54 |
| hexa | me too 🙂 | 22:48:42 |
| 18 Mar 2025 |
| 🐰 xiaoxiangmoe | Redacted or Malformed Event | 12:07:57 |
| 20 Mar 2025 |
|  @xsrp:matrix.org joined the room. | 03:17:41 |
| @xsrp:matrix.org changed their display name from Seraphim Pardee to srp. | 03:19:04 |
| @xsrp:matrix.org left the room. | 03:20:17 |
| 21 Mar 2025 |
|  nat joined the room. | 15:41:58 |
| 23 Mar 2025 |
 Gaétan Lepage | It is a bit annoying that the bot automatically substitutes ${version} with ${src.tag} in meta.changelog.
Is this made on purpose? If not, where should I send a PR to disable this? | 10:20:09 |
 FliegendeWurst (@GPN23) | In reply to @glepage:matrix.org
It is a bit annoying that the bot automatically substitutes ${version} with ${src.tag} in meta.changelog.
Is this made on purpose? If not, where should I send a PR to disable this? It is more accurate in some cases, and wrong in others. Would be good to disable, in my opinion. PR probably to the nixpkgs-update repo? | 20:45:00 |
| Gaétan Lepage | Yes, as there is no clear consensus on which one is best, I don't think that the update script should enforce one of them. | 21:11:56 |
| Gaétan Lepage | I'll have a look | 21:12:26 |
 SigmaSquadron | Gaétan Lepage: Are you sure that this is necessary? (especially for a new contributor)
nixpkgs-update automatically fetches new releases from packages published on GitHub without an explicit passthru.updateScript set.
| 21:15:25 |
| Gaétan Lepage | In reply to @sigmasquadron:matrix.org
Gaétan Lepage: Are you sure that this is necessary? (especially for a new contributor)
nixpkgs-update automatically fetches new releases from packages published on GitHub without an explicit passthru.updateScript set.
I didn't know that! I thought that specifying updateScript was necessary for the bot to work. (except for python packages where this is set by default). | 21:16:58 |
| SigmaSquadron | As far as I understand, that's what the documentation means by "It uses package repository information from Repology.org, the GitHub releases API, and the package passthru.updateScript to generate a lists of outdated packages." (emphasis mine)
I'm not exactly sure if that's for some internal "list of outdated packages" or the actual update itself, so take this with a grain of salt. | 21:20:14 |
| SigmaSquadron | I'm just more concerned about making such reviews for first-time contributors; we can merge a package as-is, and add non-essential improvements later on. | 21:21:28 |
