| 27 Jun 2024 |
|  @sersorrel:matrix.org joined the room. | 16:42:59 |
| @sersorrel:matrix.org | o/ r-ryantm seems unhappy to update xivlauncher to 1.0.9, due to steam-run unfreeness: https://nixpkgs-update-logs.nix-community.org/xivlauncher/2024-06-27.log
but it quite happily did the update to 1.0.8: https://nixpkgs-update-logs.nix-community.org/xivlauncher/2024-03-19.log, https://github.com/NixOS/nixpkgs/pull/297179
what's caused the change? | 16:45:03 |
| @sersorrel:matrix.org | ^ can be ignored, this release needs manual intervention so I'm less interested in the lack of automatic update for the time being | 19:55:44 |
| 29 Jun 2024 |
|  mib 🥐 changed their profile picture. | 22:25:28 |
| 30 Jun 2024 |
|  asymmetric joined the room. | 12:11:35 |
| asymmetric | is there an api for the bot results? i'd like to know when a package i'm a maintainer of is not auto-updating properly | 12:29:00 |
| asymmetric | * is there an api for the bot's builds? i'd like to know when a package i'm a maintainer of is not auto-updating properly | 12:29:15 |
| asymmetric | also, is the bot still being paid out-of-pocket by ryantm? that seems crazy, if so | 12:32:06 |
 ryantm | There's no API. The bot is hosted by a nix-community server. I donate to them to help pay for it. | 12:58:31 |
|  jshcmpbll joined the room. | 21:48:06 |
| jshcmpbll | Hi all, I just noticed a PR for a package I maintain has merge conflicts. Does anyone know the proper way to handle that? Should I just dismiss the PR or is there a mechanism to fix conflicts? Thanks!
https://github.com/NixOS/nixpkgs/pull/323194 | 21:50:00 |
| 1 Jul 2024 |
| ryantm | I close it. It will regenerate. | 12:07:39 |
