| 12 Mar 2025 |
|  vidariondr joined the room. | 21:10:06 |
| 17 Mar 2025 |
|  egrieco joined the room. | 06:47:52 |
 Anton (he/him) | 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 (he/him) | 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 | 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 |
