Skip to content

Conversation

@r-ryantm
Copy link
Contributor

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/regclient/versions.

meta.description for regbot is: Docker and OCI Registry Client in Go and tooling using those libraries

meta.homepage for regbot is: https://github.com/regclient/regclient

Updates performed
  • Golang update
To inspect upstream changes
Impact

Checks done


  • built on NixOS
  • The tests defined in passthru.tests, if any, passed
  • found 0.8.3 with grep in /nix/store/d8ym6sgg6r9nv78qcvrxvwwjl6s6p2jf-source

Rebuild report (if merged into master) (click to expand)
5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

regbot
regclient
regctl
regsync
Instructions to test this update (click to expand)

Either download from the cache:

nix-store -r /nix/store/d8ym6sgg6r9nv78qcvrxvwwjl6s6p2jf-source \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.

Or, build yourself:

nix-build -A regbot https://github.com/r-ryantm/nixpkgs/archive/343d477014d9c849fbc8de2929fc51e7b5612892.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/343d477014d9c849fbc8de2929fc51e7b5612892#regbot

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/d8ym6sgg6r9nv78qcvrxvwwjl6s6p2jf-source
ls -la /nix/store/d8ym6sgg6r9nv78qcvrxvwwjl6s6p2jf-source/bin


Pre-merge build results

We have automatically built all packages that will get rebuilt due to
this change.

This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review


x86_64-linux

✅ 4 packages built:
  • regbot (regbot.regbot ,regbot.regctl ,regbot.regsync ,regclient.regbot)
  • regclient
  • regctl (regclient.regctl ,regctl.regbot ,regctl.regctl ,regctl.regsync)
  • regsync (regclient.regsync ,regsync.regbot ,regsync.regctl ,regsync.regsync)

Maintainer pings

cc @maxbrunet for testing.

Tip

As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.


Add a 👍 reaction to pull requests you find important.

@github-actions github-actions bot added 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. labels Apr 24, 2025
@nix-owners nix-owners bot requested a review from maxbrunet April 24, 2025 01:01
@wegank
Copy link
Member

wegank commented May 17, 2025

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 401280


aarch64-darwin

✅ 4 packages built:
  • regbot (regbot.regbot, regbot.regctl, regbot.regsync, regclient.regbot)
  • regclient
  • regctl (regclient.regctl, regctl.regbot, regctl.regctl, regctl.regsync)
  • regsync (regclient.regsync, regsync.regbot, regsync.regctl, regsync.regsync)

@wegank wegank merged commit 21d06c2 into NixOS:master May 18, 2025
27 checks passed
@r-ryantm r-ryantm deleted the auto-update/regbot branch May 18, 2025 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants