!lZLfSUtSOVjwYTmPbU:nixos.org

nixpkgs-update

185 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.nix58 Servers

Load older messages


SenderMessageTime
10 Jan 2026
@magnetophon:matrix.orgmagnetophonHi! r-ryantm did a PR to update one of my packages on the day the new version came out: https://github.com/NixOS/nixpkgs/pull/478282 But the next update has not been picked up by it yet: https://github.com/tiagolr/qdelay/releases/tag/v1.0.6 I read through the documentation and it mentions the logs, but doesn't link to them. Anything else I can do to find out why r-ryantm is not (yet) picking up on this?11:55:03
@hexa:lossy.networkhexahttps://nixpkgs-update-logs.nix-community.org/qdelay/11:59:25
@hexa:lossy.networkhexait has lots of packages to check, so it passes yours only so often11:59:42
@hexa:lossy.networkhexalast time yesterday11:59:51
@bandithedoge:matrix.orgbandithedogeyou can make an update pr yourself or just wait for it to check again in a few days or so15:32:51
@ljxfstorm:matrix.orgljxfstorm joined the room.17:19:23
@ljxfstorm:matrix.orgljxfstorm According to log of r-ryantm bot for gemini-cli-bin, the update for gemini-cli-bin was skipped because of the existing update PR for gemini-cli. Is there any method to resolve it? 17:28:13
11 Jan 2026
@mh0386:matrix.orgMohamed Hisham Abdelzaher joined the room.15:28:56
12 Jan 2026
@magnetophon:matrix.orgmagnetophonThanks. The advantage of a r-ryantm PR is that I can merge it myself.19:34:14
13 Jan 2026
@jopejoe1:matrix.orgjopejoe1 (4094@39c3) changed their display name from jopejoe1 (4094@39c3) to jopejoe1 (4094@epvpn).08:26:04
14 Jan 2026
@annaaurora:artemislena.euAnna Aurora (superseded by: @anna:annaaurora.eu) left the room.17:18:21
16 Jan 2026
@mh0386:beeper.comMohamed Hisham Abdelzaher joined the room.13:06:27
17 Jan 2026
@tollb1:matrix.orgtollb1 joined the room.16:58:01
@marcel:envs.netMarcel changed their display name from Marcel to Marcel (@).23:44:15
@marcel:envs.netMarcel changed their display name from Marcel (@) to Marcel => @me:m4rc3l.de.23:44:59
18 Jan 2026
@marcel:envs.netMarcel left the room.17:48:20
19 Jan 2026
@whispers:catgirl.cloudwhispers (it/fae) joined the room.21:46:55
22 Jan 2026
@thefossguy:matrix.orgPratham Patel joined the room.05:59:10
@thefossguy:matrix.orgPratham Patel

Is it possible to tell the auto-update bot to group commits for a specific set of packages into a single PR? At the moment, auto-updates for COSMIC packages are turned off and I "manually" auto-update them with the following command on my local machine and then creating a PR:

nix-shell maintainers/scripts/update.nix \
    --argstr commit true \
    --argstr keep-going true \
    --argstr max-workers 1 \
    --argstr skip-prompt true \
    --arg predicate '(path: pkg: let lib = import <nixpkgs/lib>; in lib.lists.elem lib.teams.cosmic (pkg.meta.teams or []))'

I was wondering if this could be automated in such a way that all package update commits are in a single PR. This is because upstream tags new versions for all stable packages at once, meaning we update all stable packages with each new release. But the motivating factor for automating this is that upstream is switching to weekly releases. I'd much rather spend my time on reviewing and let the auto-update bot handle updates, if possible.

I have given this some thought and am thinking of creating these two files in nixpkgs:

# pkgs/by-name/co/cosmic-packages-upgrade-script/package.nix
{
  stdenvNoCC,
  writeShellScript,
  lib,
}:

stdenvNoCC.mkDerivation {
  name = "cosmic-packages-upgrade-script";

  passthru.updateScript = import ./update-script.nix { inherit writeShellScript; };

  meta = {
    description = "A package to auto-upgrade all COSMIC packages maintained by the nixpkgs COSMIC team";
    license = lib.licenses.mit;
    teams = [ lib.teams.cosmic ];
    platforms = lib.platforms.linux;
  };
}
# pkgs/by-name/co/cosmic-packages-upgrade-script/update-script.nix
{ writeShellScript }:

writeShellScript "cosmic-packages-upgrade-script" ''
  cd "$(git rev-parse --show-toplevel)" || exit 1
  exec nix-shell maintainers/scripts/update.nix \
    --argstr commit true \
    --argstr keep-going true \
    --argstr max-workers 1 \
    --argstr skip-prompt true \
    --arg predicate '(path: pkg: let lib = import <nixpkgs/lib>; in lib.lists.elem lib.teams.cosmic (pkg.meta.teams or []))'
''

Is this cursed? Would it even work? What's the recommended method here?

06:09:00
@gus:gu5.orgGus left the room.15:35:27
19 Sep 2023
@evils:nixos.devevils joined the room.16:15:20
@ryantm:matrix.orgryantm raitobezarius: No, not really. It's been an idea for a long time to have grouped package updates like that, but it hasn't been implemented. 16:52:21
@evils:nixos.devevilshi, second link in the channel topic is dead19:21:58
@evils:nixos.devevilsis there a way to see what packages the bot tried to update but failed on?19:22:23
@artturin:matrix.orgArtturin
In reply to @evils:nixos.dev
is there a way to see what packages the bot tried to update but failed on?
https://r.ryantm.com/log/
19:23:49
@artturin:matrix.orgArtturinhttps://ryantm.github.io/nixpkgs-update/nixpkgs-maintainer-faq/#nixpkgs-maintainer-faq19:23:56
@artturin:matrix.orgArtturin * from https://ryantm.github.io/nixpkgs-update/nixpkgs-maintainer-faq/#nixpkgs-maintainer-faq19:23:58
@evils:nixos.devevilsimage.png
Download image.png
19:24:43
@evils:nixos.devevilsoof that's a subtle link underline19:24:50
@evils:nixos.devevils(i was looking at the page :)19:25:02

Show newer messages


Back to Room ListRoom Version: 9