!lZLfSUtSOVjwYTmPbU:nixos.org

nixpkgs-update

179 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.nix57 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
3 Apr 2025
@quantenzitrone:matrix.orgzitroner-ryantm was able to update my package https://nixpkgs-update-logs.nix-community.org/wl-gammarelay-rs/2025-04-03.log but it didn't open a pr for it13:00:04
5 Apr 2025
@zexu:matrix.orgzexu joined the room.13:09:08
11 Apr 2025
@ambroisie:belanyi.fr@ambroisie:belanyi.fr left the room.22:08:49
13 Apr 2025
@bot-wxt1221:matrix.orgBot_wxt1221 joined the room.13:32:29
15 Apr 2025
@ingramz:matrix.orgIndrek joined the room.11:55:07
@ingramz:matrix.orgIndrekThis is an interesting failure, seems to perform the update sucessfully but unable to commit the result after https://nixpkgs-update-logs.nix-community.org/bitwarden-desktop/2025-04-15.log also found another one at https://nixpkgs-update-logs.nix-community.org/tabnine/2025-04-10.log13:22:39
@sandro:supersandro.deSandro 🐧
No auto update branch exists
Successfully finished processing
Received ExitFailure 1 when running
Raw command: git commit -am "bitwarden-desktop: 2025.2.0 -> 2025.3.1"
Standard output:

On branch auto-update/bitwarden-desktop
nothing to commit, working tree clean
15:03:08
@perchun:matrix.orgPerchun Pakthis is probably because the update script commits changes and r-ryantm tries to create a second commit https://github.com/NixOS/nixpkgs/blob/2631b0b7abcea6e640ce31cd78ea58910d31e650/pkgs/by-name/bi/bitwarden-desktop/package.nix#L225 https://github.com/NixOS/nixpkgs/blob/2631b0b7abcea6e640ce31cd78ea58910d31e650/pkgs/by-name/ta/tabnine/update.sh#L4617:57:02
@ingramz:matrix.orgIndrekYeah, that's most likely it. I'm pretty new to all things nix so it's difficult to say if this is a nixpkgs issue or nixpkgs-update issue. I guess the automation could soft reset the git state back to what it started with and then perform a commit of its own, but this sounds a little hacky. On the other hand nixpkgs could simply state that update scripts should not be allowed to perform git operations on the repository by default and then things would just work on r-ryantm side. There's probably other solutions may exist as well, but this is just to illustrate my point that it's not clear to me what's the next step from here.21:45:10
19 Apr 2025
@jopejoe1:matrix.orgjopejoe1 changed their display name from jopejoe1 to jopejoe1 (4094@eh22).12:59:35
21 Apr 2025
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all) joined the room.10:54:13
22 Apr 2025
@sistema.matrix:matrix.orgThomas joined the room.17:31:10

Show newer messages


Back to Room ListRoom Version: 9