Sender | Message | Time |
---|---|---|
6 Mar 2025 | ||
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 | ||
23:06:44 | ||
9 Mar 2025 | ||
15:33:07 | ||
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 | ||
19:59:25 | ||
12 Mar 2025 | ||
21:10:06 | ||
17 Mar 2025 | ||
06:47:52 | ||
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 | |
all attempts get logged | 20:21:21 | |
Thanks! I was wondering about the frequency of attempts. | 20:55:54 | |
me too 🙂 | 22:48:42 | |
18 Mar 2025 | ||
Redacted or Malformed Event | 12:07:57 | |
20 Mar 2025 | ||
03:17:41 | ||
03:19:04 | ||
03:20:17 | ||
21 Mar 2025 | ||
15:41:58 | ||
23 Mar 2025 | ||
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 | |
In reply to @glepage:matrix.orgIt 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 | |
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 | |
I'll have a look | 21:12:26 | |
Gaétan Lepage: Are you sure that this is necessary? (especially for a new contributor)
| 21:15:25 | |
In reply to @sigmasquadron:matrix.orgI 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 | |
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 | |
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 | |
* 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 | ||
In reply to @sigmasquadron:matrix.orgIt’s not necessary for the bot, but can be helpful for maintainers running the update scripts in repo | 12:23:10 | |
25 Mar 2025 | ||
17:00:10 | ||
31 Mar 2025 | ||
11:30:38 | ||
Hi,
In my understanding, the issue should was already addressed with: | 11:37:56 | |
1 Apr 2025 | ||
In reply to @xenos76:matrix.org that PR targets the 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 | 00:18:53 |