!lZLfSUtSOVjwYTmPbU:nixos.org

nixpkgs-update

147 Members
Keeping nixpkgs up to date. r-ryantm bot. https://github.com/ryantm/nixpkgs-update and https://github.com/nix-community/infra/blob/master/build02/nixpkgs-update.nix42 Servers

Load older messages


SenderMessageTime
9 Jan 2025
@xiaoxiangmoe:matrix.org🐰 xiaoxiangmoehttps://github.com/NixOS/nixpkgs/pull/37229311:03:47
@xiaoxiangmoe:matrix.org🐰 xiaoxiangmoeWhy it will downgrade?11:04:08
@xiaoxiangmoe:matrix.org🐰 xiaoxiangmoe* Why will it downgrade?11:04:18
10 Jan 2025
@tris203:matrix.orgtris203 joined the room.11:02:44
@sigmasquadron:matrix.orgSigmaSquadron changed their display name from SigmaSquadron (Away until 2024-01-12) to SigmaSquadron (Away until 2024-01-11).22:15:38
@sigmasquadron:matrix.orgSigmaSquadron 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:matrix.orgSigmaSquadron changed their display name from SigmaSquadron (Away until 2025-01-11) to SigmaSquadron.15:06:28
13 Jan 2025
@codgician:matrix.codgician.mecodgician changed their profile picture.11:13:38
15 Jan 2025
@perchun:matrix.orgPerchun Pakwhy did it collect it? https://nixpkgs-update-logs.nix-community.org/rquickshare-legacy/2025-01-09.log10:25:51
@tomherbers:matrix.orgTom (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:systemli.orgpistache changed their profile picture.22:06:47
@pistache:systemli.orgpistache changed their profile picture.22:07:30
16 Jan 2025
@asymmetric:matrix.dapp.org.ukasymmetric

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:matrix.dapp.org.ukasymmetric *

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:matrix.dapp.org.ukasymmetricso basically, we should be tracking this one: https://repology.org/project/pebble-acme-test-server/versions09:30:01
@fliegendewurst:matrix.orgFliegendeWurst joined the room.09:38:13
19 Jan 2025
@zowoq:matrix.orgzowoq

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:matrix.orgzowoqI 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:matrix.orgzowoqNo, shouldn't need to do anything as the package versions will be correct after the rename.01:49:23
@zowoq:matrix.orgzowoqYou'll need to use version-regex in the nix-update-script.04:14:51
@zowoq:matrix.orgzowoqI 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
@yoganshsharma:matrix.orgYogansh joined the room.08:09:31
24 Jan 2025
@katexochen:matrix.orgPaul Meyer (katexochen) joined the room.15:52:04
@katexochen:matrix.orgPaul 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
@zowoq:matrix.orgzowoqThe bot checks for new update scripts twice a day and updates are run on the merge base of master and staging so sometimes the the bot attempts an update script that doesn't work on the current merge base.23:39:57
25 Jan 2025
@katexochen:matrix.orgPaul Meyer (katexochen)Makes sense, thanks. Will wait and observe. :)09:00:11
27 Jan 2025
@srhb:matrix.orgsrhb joined the room.07:39:29
@srhb:matrix.orgsrhb

Can someone help me understand by the bot created https://github.com/NixOS/nixpkgs/pull/374876 ? (downgrade filebeat 8 -> filebeat 7) -- is it because I, in a misguided attempt to stay consistent with the existing filebeat7 attr named it filebeat8 rather than filebeat_8 ?

I tried loading up nixpkgs-update in a ghci repl, but it appears to indicate I'm good on that front,

ghci> versionCompatibleWithPathPin "filebeat8" "8.16.1"
True

ghci> versionCompatibleWithPathPin "filebeat8" "7.17.27"
False

How do I fix this? :)

08:21:04
@srhb:matrix.orgsrhb *

Can someone help me understand why the bot created https://github.com/NixOS/nixpkgs/pull/374876 ? (downgrade filebeat 8 -> filebeat 7) -- is it because I, in a misguided attempt to stay consistent with the existing filebeat7 attr named it filebeat8 rather than filebeat_8 ?

I tried loading up nixpkgs-update in a ghci repl, but it appears to indicate I'm good on that front,

ghci> versionCompatibleWithPathPin "filebeat8" "8.16.1"
True

ghci> versionCompatibleWithPathPin "filebeat8" "7.17.27"
False

How do I fix this? :)

08:24:43
@fliegendewurst:matrix.orgFliegendeWurst
In reply to @srhb:matrix.org

Can someone help me understand why the bot created https://github.com/NixOS/nixpkgs/pull/374876 ? (downgrade filebeat 8 -> filebeat 7) -- is it because I, in a misguided attempt to stay consistent with the existing filebeat7 attr named it filebeat8 rather than filebeat_8 ?

I tried loading up nixpkgs-update in a ghci repl, but it appears to indicate I'm good on that front,

ghci> versionCompatibleWithPathPin "filebeat8" "8.16.1"
True

ghci> versionCompatibleWithPathPin "filebeat8" "7.17.27"
False

How do I fix this? :)

Probably you need to fix the updateScript, that is what the bot used.
08:54:21

Show newer messages


Back to Room ListRoom Version: 9