Skip to content

Conversation

@r-ryantm
Copy link
Contributor

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for aliyun-cli is: Tool to manage and use Alibaba Cloud resources through a command line interface

meta.homepage for aliyun-cli is: https://github.com/aliyun/aliyun-cli

meta.changelog for aliyun-cli is: https://github.com/aliyun/aliyun-cli/releases/tag/v3.0.270

Updates performed
  • Ran passthru.UpdateScript
To inspect upstream changes
Impact

Checks done


  • built on NixOS
  • The tests defined in passthru.tests, if any, passed
  • found 3.0.270 in filename of file in /nix/store/krfpk3nz5afy7ywwn1c51kqfzvzrikqn-aliyun-cli-3.0.270

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

2 package rebuild(s)

First fifty rebuilds by attrpath

aliyun-cli
Instructions to test this update (click to expand)

Either download from the cache:

nix-store -r /nix/store/krfpk3nz5afy7ywwn1c51kqfzvzrikqn-aliyun-cli-3.0.270 \
  --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 aliyun-cli https://github.com/r-ryantm/nixpkgs/archive/1af6f3353fffbe89b4092d2c5483815672ed9268.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/1af6f3353fffbe89b4092d2c5483815672ed9268#aliyun-cli

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

ls -la /nix/store/krfpk3nz5afy7ywwn1c51kqfzvzrikqn-aliyun-cli-3.0.270
ls -la /nix/store/krfpk3nz5afy7ywwn1c51kqfzvzrikqn-aliyun-cli-3.0.270/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

✅ 1 package built:
  • aliyun-cli

Maintainer pings

cc @ornxka 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 This PR causes 1 package to rebuild on Darwin. 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-linux: 1 This PR causes 1 package to rebuild on Linux. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. labels Apr 18, 2025
Copy link
Member

@NickCao NickCao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ldflags needs an update.

@r-ryantm r-ryantm changed the title aliyun-cli: 3.0.266 -> 3.0.270 aliyun-cli: 3.0.266 -> 3.0.272 Apr 27, 2025
@r-ryantm r-ryantm force-pushed the auto-update/aliyun-cli branch from 1af6f33 to c4da40c Compare April 27, 2025 13:19
@r-ryantm
Copy link
Contributor Author

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for aliyun-cli is: Tool to manage and use Alibaba Cloud resources through a command line interface

meta.homepage for aliyun-cli is: https://github.com/aliyun/aliyun-cli

meta.changelog for aliyun-cli is: https://github.com/aliyun/aliyun-cli/releases/tag/v3.0.272

Updates performed
  • Ran passthru.UpdateScript
To inspect upstream changes
Impact

Checks done


  • built on NixOS
  • The tests defined in passthru.tests, if any, passed
  • found 3.0.272 in filename of file in /nix/store/5x9b66y7qw46q7czj1bpji7g232m26rd-aliyun-cli-3.0.272

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

2 package rebuild(s)

First fifty rebuilds by attrpath

aliyun-cli
Instructions to test this update (click to expand)

Either download from the cache:

nix-store -r /nix/store/5x9b66y7qw46q7czj1bpji7g232m26rd-aliyun-cli-3.0.272 \
  --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 aliyun-cli https://github.com/r-ryantm/nixpkgs/archive/c4da40cddc13fe1b96321354abc851fc99dca163.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/c4da40cddc13fe1b96321354abc851fc99dca163#aliyun-cli

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

ls -la /nix/store/5x9b66y7qw46q7czj1bpji7g232m26rd-aliyun-cli-3.0.272
ls -la /nix/store/5x9b66y7qw46q7czj1bpji7g232m26rd-aliyun-cli-3.0.272/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

✅ 1 package built:
  • aliyun-cli

Maintainer pings

cc @ornxka 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.

@r-ryantm r-ryantm changed the title aliyun-cli: 3.0.266 -> 3.0.272 aliyun-cli: 3.0.266 -> 3.0.273 May 7, 2025
@r-ryantm r-ryantm force-pushed the auto-update/aliyun-cli branch from c4da40c to 56e5b8f Compare May 7, 2025 12:12
@r-ryantm
Copy link
Contributor Author

r-ryantm commented May 7, 2025

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for aliyun-cli is: Tool to manage and use Alibaba Cloud resources through a command line interface

meta.homepage for aliyun-cli is: https://github.com/aliyun/aliyun-cli

meta.changelog for aliyun-cli is: https://github.com/aliyun/aliyun-cli/releases/tag/v3.0.273

Updates performed
  • Ran passthru.UpdateScript
To inspect upstream changes
Impact

Checks done


  • built on NixOS
  • The tests defined in passthru.tests, if any, passed
  • found 3.0.273 in filename of file in /nix/store/1xfd70685j3x25ryvq9sqvdfvk1raf2q-aliyun-cli-3.0.273

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

2 package rebuild(s)

First fifty rebuilds by attrpath

aliyun-cli
Instructions to test this update (click to expand)

Either download from the cache:

nix-store -r /nix/store/1xfd70685j3x25ryvq9sqvdfvk1raf2q-aliyun-cli-3.0.273 \
  --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 aliyun-cli https://github.com/r-ryantm/nixpkgs/archive/56e5b8f1d27e368a7f71c5601a3f11762d6fe041.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/56e5b8f1d27e368a7f71c5601a3f11762d6fe041#aliyun-cli

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

ls -la /nix/store/1xfd70685j3x25ryvq9sqvdfvk1raf2q-aliyun-cli-3.0.273
ls -la /nix/store/1xfd70685j3x25ryvq9sqvdfvk1raf2q-aliyun-cli-3.0.273/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

✅ 1 package built:
  • aliyun-cli

Maintainer pings

cc @ornxka 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.

@wegank wegank force-pushed the auto-update/aliyun-cli branch from 56e5b8f to 2c89e11 Compare May 17, 2025 21:54
@wegank
Copy link
Member

wegank commented May 18, 2025

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 399764


aarch64-linux

✅ 1 package built:
  • aliyun-cli

@wegank wegank merged commit b2f96ba into NixOS:master May 18, 2025
19 of 21 checks passed
@r-ryantm r-ryantm deleted the auto-update/aliyun-cli 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-darwin: 1 This PR causes 1 package to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-linux: 1 This PR causes 1 package to rebuild on Linux.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants