| 22 May 2025 |
|  tnias joined the room. | 11:00:51 |
|  Perchun Pak [don't ping; dm instead] changed their display name from Perchun Pak to Perchun Pak [don't ping; dm instead]. | 13:50:50 |
| 23 May 2025 |
|  divit joined the room. | 21:00:08 |
| 24 May 2025 |
|  @surnamerefill:matrix.org left the room. | 20:07:59 |
| 25 May 2025 |
 ReecerTV | What should I do if ryantm thinks it has the latest version, but it's actually not the latest. Can I just close the PR? | 10:53:14 |
 Alyssa Ross | It'll update the PR next time it runs, if it finds the newer version then. | 10:54:22 |
| Alyssa Ross | I think if you close the PR but don't update the package it will open another one next time it finds a new version. | 10:54:45 |
| Alyssa Ross | Can you just update the package to the actual latest version, and then close the PR? | 10:54:58 |
| ReecerTV | In reply to @qyliss:fairydust.space
Can you just update the package to the actual latest version, and then close the PR? It is already updated to the latest version. | 10:57:33 |
| ReecerTV | https://github.com/NixOS/nixpkgs/pull/410686 | 10:58:17 |
| Alyssa Ross | And r-ryantm is trying to downgrade it? | 11:00:05 |
| Alyssa Ross | Right | 11:00:09 |
| Alyssa Ross | Yeah, since this looks like a one-off, just close the PR. | 11:00:16 |
 FliegendeWurst (@GPN23) | r-ryantm will recreate the PR next run, better to mark it as draft | 12:45:31 |
 Grimmauld (any/all) | will it? the tag link is giving a 404, so the tag was probably pulled. And then r-ryantm will not pull it, right? Or does it go of repology version where that number still exists? | 19:19:09 |
| FliegendeWurst (@GPN23) | the tag is still there: https://github.com/Darazaki/Spedread/tree/v2.4.7 | 21:09:11 |
| FliegendeWurst (@GPN23) | the changelog link is incorrect however | 21:09:39 |
| Grimmauld (any/all) | ah | 21:09:47 |
| 26 May 2025 |
|  matrixrooms.info mod bot (does NOT read/send messages and/or invites; used for checking reported rooms) joined the room. | 18:31:16 |
| 28 May 2025 |
|  @mducoli:matrix.org joined the room. | 17:34:19 |
| @mducoli:matrix.org left the room. | 17:34:48 |
| 31 May 2025 |
|  tiferrei joined the room. | 20:53:41 |
| 2 Jun 2025 |
|  @2hexed:matrix.org joined the room. | 17:07:23 |
| Grimmauld (any/all) | what is the best way to write an update script for simple file servers such as https://lttng.org/files/lttng-ust/ ? | 20:40:39 |
 Guilhem | I'd go for https://github.com/lttng/lttng-ust/tags | 20:42:14 |
| Guilhem changed their display name from Guilhem to nim65s. | 20:42:26 |
| Guilhem | or the tags in git://git.lttng.org/lttng-ust.git | 20:43:02 |
| Grimmauld (any/all) | would one switch the source to github entirely then? Or only have the script look at github, risking desync? | 20:43:31 |
| Guilhem | I think upstream git is a better option. Something like updateScript = gitUpdater { rev-prefix = "v"; }; | 20:50:37 |
| Guilhem | but the mirror is fine too, github infra might be easier to use for us | 20:51:22 |
