7 Jan 2025 |
| 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 |
asymmetric | so basically, we should be tracking this one: https://repology.org/project/pebble-acme-test-server/versions | 09:30:01 |
| FliegendeWurst (@GPN23) joined the room. | 09:38:13 |
19 Jan 2025 |
zowoq | Setting null for updateScript doesn't work (and can sometimes break the bot).
This should work for the updateScript:
passthru = lib.optionalAttrs (app-type == "main") {
updateScript = writeShellScript "update-rquickshare.sh" ''
${lib.getExe nix-update} rquickshare
sed -i 's/version = "0.0.0";/' pkgs/by-name/rq/rquickshare/package.nix
${lib.getExe nix-update} rquickshare-legacy
'';
};
Would also need to add rquickshare-legacy to https://github.com/nix-community/nixpkgs-update/blob/main/src/Skiplist.hs, currently it isn't otherwise possible to tell the bot to ignore the legacy version without splitting them into separate packages.
| 01:34:52 |
zowoq | I didn't notice that there were links in the topic. I keep https://nix-community.org/update-bot/ updated with links for the bot but I'll need to get someone to update the topic or give me permissions. | 01:43:13 |
zowoq | No, shouldn't need to do anything as the package versions will be correct after the rename. | 01:49:23 |
zowoq | You'll need to use version-regex in the nix-update-script. | 04:14:51 |
zowoq | I don't see much to be gained from this feature, most of the time it will only save a day or so. | 04:19:23 |
23 Jan 2025 |
| Yogansh joined the room. | 08:09:31 |
24 Jan 2025 |
| Paul Meyer (katexochen) joined the room. | 15:52:04 |
Paul Meyer (katexochen) | Hey, I merged https://github.com/NixOS/nixpkgs/pull/376046 yesterday, which added updateScript to azure-cli-extensions, but it looks like it's not working in nixpkgs-update. Locally I get the following:
❯ nix-shell maintainers/scripts/update.nix --argstr path azure-cli-extensions.ssh
Going to be running update for following packages:
- python3.12-ssh-2.0.5
Press Enter key to continue...
Running update for:
- python3.12-ssh-2.0.5: UPDATING ...
- python3.12-ssh-2.0.5: DONE.
Packages updated!
❯ git diff --no-ext-diff
diff --git a/pkgs/by-name/az/azure-cli/extensions-manual.nix b/pkgs/by-name/az/azure-cli/extensions-manual.nix
index 254ad69d2c23..823ab0fb0989 100644
--- a/pkgs/by-name/az/azure-cli/extensions-manual.nix
+++ b/pkgs/by-name/az/azure-cli/extensions-manual.nix
@@ -113,9 +113,9 @@
ssh = mkAzExtension rec {
pname = "ssh";
- version = "2.0.5";
+ version = "2.0.6";
url = "https://azcliprod.blob.core.windows.net/cli-extensions/ssh-${version}-py3-none-any.whl";
- hash = "sha256-gMmLENe/HOQAW3aUrt0FxHNVRWd1umElMIvmX7D+/JM=";
+ hash = "sha256-PSIGtOa91WxpzFCauZ5d5tx/ZtCRsBhbejtVfY3Bgss=";
description = "SSH into Azure VMs using RBAC and AAD OpenSSH Certificates";
propagatedBuildInputs = with python3Packages; [
oras
but the log says there was no diff: https://nixpkgs-update-logs.nix-community.org/azure-cli-extensions.ssh/2025-01-24.log Any ideas what could be wrong?
| 16:01:49 |