| 6 Jan 2025 |
 K900 ⚡️ | Oh, no, it can't update that | 15:26:12 |
| K900 ⚡️ | Also that looks like a fairly normal pnpm/electron app? | 15:26:54 |
| K900 ⚡️ | So it could be switched to a source build | 15:27:00 |
 🐰 xiaoxiangmoe | Yes | 15:27:05 |
| 🐰 xiaoxiangmoe | I want to switched to a source build when I have free | 15:27:17 |
| 🐰 xiaoxiangmoe | * I want to switched to a source build when I have free time | 15:27:21 |
 bumperboat | why does it fail to update if repology hasnt updated to the version in master yet? https://nixpkgs-update-logs.nix-community.org/rbw/2025-01-06.log | 15:29:04 |
| bumperboat | seems like a lot of wasted cycles if there is a small bump released, waiting for a build to make it into unstable, then for repology to pick it up so nixpkgs-update will then bump again | 15:31:54 |
| bumperboat | oh i see https://github.com/nix-community/nixpkgs-update/issues/38 | 15:47:12 |
| 7 Jan 2025 |
|  SigmaSquadron changed their display name from SigmaSquadron to SigmaSquadron (Away until 2024-01-12). | 19:35:48 |
|  Renato Trevisan set a profile picture. | 21:58:28 |
| 8 Jan 2025 |
| 🐰 xiaoxiangmoe | Can we add a button or API to trigger @r-ryantm | 05:41:54 |
| 🐰 xiaoxiangmoe | 🤔 I found some package can update but the r-ryantm's regular check update schedule has not yet arrived. | 05:43:18 |
 Ramses 🇵🇸 | In that case, you can just run the update script locally and create a PR. With the gh tool it's very quick | 12:28:02 |
| 🐰 xiaoxiangmoe | But If this is created by me, it can't auto merged by my comment | 12:39:15 |
| Ramses 🇵🇸 | Yeah that's true. PRs made by or approved by the package maintainer, often get merged pretty quickly though (I often go through that list to merge the uncontroversial version bumps) | 14:17:38 |
| 9 Jan 2025 |
| 🐰 xiaoxiangmoe | https://github.com/NixOS/nixpkgs/pull/372293 | 11:03:47 |
| 🐰 xiaoxiangmoe | Why it will downgrade? | 11:04:08 |
| 🐰 xiaoxiangmoe | * Why will it downgrade? | 11:04:18 |
| 10 Jan 2025 |
|  tris203 joined the room. | 11:02:44 |
| SigmaSquadron changed their display name from SigmaSquadron (Away until 2024-01-12) to SigmaSquadron (Away until 2024-01-11). | 22:15:38 |
| SigmaSquadron changed their display name from SigmaSquadron (Away until 2024-01-11) to SigmaSquadron (Away until 2025-01-11). | 22:43:07 |
| 11 Jan 2025 |
| SigmaSquadron changed their display name from SigmaSquadron (Away until 2025-01-11) to SigmaSquadron. | 15:06:28 |
| 13 Jan 2025 |
|  codgician changed their profile picture. | 11:13:38 |
| 15 Jan 2025 |
 Perchun Pak [don't ping; dm instead] | why did it collect it?
https://nixpkgs-update-logs.nix-community.org/rquickshare-legacy/2025-01-09.log | 10:25:51 |
 Tom (deprecated) | The URL in the room topic should probably be updated to https://github.com/nix-community/infra/blob/master/hosts/build02/nixpkgs-update.nix :) | 20:31:28 |
|  pistache changed their profile picture. | 22:06:47 |
| pistache changed their profile picture. | 22:07:30 |
| 16 Jan 2025 |
 asymmetric | hey, is any action needed on nixpkgs-update's part when repology changes the name of a package?
pebble had a name clash between two separate projects, which was causing build failures. now they've renamed the two projects to different names, and pebble doesn't exist anymore: https://repology.org/project/pebble/versions
| 09:28:53 |
| asymmetric | * hey, is any action needed on nixpkgs-update's part when repology changes the name of a package?
pebble had a name clash on repology between two separate upstream projects, which was causing build failures. now they've renamed the two projects to different names, and pebble doesn't exist anymore: https://repology.org/project/pebble/versions
| 09:29:11 |
