| 6 Mar 2025 |
 🐰 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 |
|  srp joined the room. | 03:17:41 |
| srp changed their display name from Seraphim Pardee to srp. | 03:19:04 |
| srp 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 | 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 |
| 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. (ditto for using lib.cmakeBool, since that library is really only used in situations where the boolean isn't always true or false. The string flag is fine.) | 21:23:14 |
| 24 Mar 2025 |
 Austin Horstman | 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.
It’s not necessary for the bot, but can be helpful for maintainers running the update scripts in repo | 12:23:10 |
| 25 Mar 2025 |
|  aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) changed their display name from aleksana (force me to bed after 18:00 UTC) to aleksana 🏳️⚧️ (force me to bed after 18:00 UTC). | 17:00:10 |
| 31 Mar 2025 |
|  xenos76 joined the room. | 11:30:38 |
| xenos76 | Hi,
I'm facing the following problem while updating hplip:
error: builder for '/nix/store/3szdhxqbxk0npbf1ihqkdhqb7qidv6gj-hplip-3.24.4-plugin.run.drv' failed with exit code 1;
last 7 log lines:
>
> trying https://developers.hp.com/sites/default/files/hplip-3.24.4-plugin.run
> % Total % Received % Xferd Average Speed Time Time Time Current
> Dload Upload Total Spent Left Speed
> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
> curl: (22) The requested URL returned error: 403
> error: cannot download hplip-3.24.4-plugin.run from any mirror
In my understanding, the issue should was already addressed with:
https://github.com/NixOS/nixpkgs/issues/391727
https://github.com/NixOS/nixpkgs/pull/391529
but today's update from 24.11 failed: how can I check if the patch made it to the stable branch? Am I missing something else?
| 11:37:56 |
| 1 Apr 2025 |
| sorrel | In reply to @xenos76:matrix.org
Hi,
I'm facing the following problem while updating hplip:
error: builder for '/nix/store/3szdhxqbxk0npbf1ihqkdhqb7qidv6gj-hplip-3.24.4-plugin.run.drv' failed with exit code 1;
last 7 log lines:
>
> trying https://developers.hp.com/sites/default/files/hplip-3.24.4-plugin.run
> % Total % Received % Xferd Average Speed Time Time Time Current
> Dload Upload Total Spent Left Speed
> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
> curl: (22) The requested URL returned error: 403
> error: cannot download hplip-3.24.4-plugin.run from any mirror
In my understanding, the issue should was already addressed with:
https://github.com/NixOS/nixpkgs/issues/391727
https://github.com/NixOS/nixpkgs/pull/391529
but today's update from 24.11 failed: how can I check if the patch made it to the stable branch? Am I missing something else?
that PR targets the master branch, so it will not hit the stable channels ever. (you can see its progress towards e.g. nixos-unstable at https://nixpk.gs/pr-tracker.html?pr=391529)
I've now tagged it for backport to 24.11, so a backport PR has been automatically created: https://github.com/NixOS/nixpkgs/pull/395044
however, this will still need to be manually merged and make its way through hydra before it's available in e.g. the nixos-24.11 branch | 00:18:53 |
