Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: android-studio-tools 14742923 -> 15859902 https://repology.org/project/android-studio-tools/versions attrpath: android-studio-tools Checking auto update branch... No auto update branch exists [version] [version] updated version and sha256 [rustCrateVersion] [rustCrateVersion] No cargoHash found [golangModuleVersion] [golangModuleVersion] Not a buildGoModule package with vendorHash [npmDepsVersion] [npmDepsVersion] No npmDepsHash [updateScript] [updateScript] skipping because derivation has no updateScript Diff after rewrites: diff --git a/pkgs/by-name/an/android-studio-tools/package.nix b/pkgs/by-name/an/android-studio-tools/package.nix index a461d9b81ec7..ea2d93edd66f 100644 --- a/pkgs/by-name/an/android-studio-tools/package.nix +++ b/pkgs/by-name/an/android-studio-tools/package.nix @@ -8,13 +8,13 @@ stdenvNoCC.mkDerivation { pname = "android-studio-tools"; - version = "14742923"; + version = "15859902"; src = fetchzip { # The only difference between the Linux and Mac versions is a single comment at the top of all the scripts # Therefore, we will use the Linux version and just patch the comment - url = "https://dl.google.com/android/repository/commandlinetools-linux-14742923_latest.zip"; - hash = "sha256-oimC4ToDFIa8Rlv+5RB+swl8M5PHdX4omlrMZMQEx8M="; + url = "https://dl.google.com/android/repository/commandlinetools-linux-15859902_latest.zip"; + hash = "sha256-tCbccw7qa7ncHGyWPWjwQOpaisN3QMRYXRpK7WtyjWY="; }; postPatch = '' Successfully finished processing [check][nixpkgs-review] ## `nixpkgs-review` result Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review). Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'` Commit: `5f5ca071b5cd396482d1e3154ee76eaff176c0fe` --- ### `x86_64-linux`
:white_check_mark: 1 package built:
Automatic update generated by [nixpkgs-update](https://github.com/nix-community/nixpkgs-update) tools. This update was made based on information from https://repology.org/project/android-studio-tools/versions. meta.description for android-studio-tools is: Android Studio CLI Tools meta.homepage for android-studio-tools is: https://developer.android.com/studio meta.changelog for android-studio-tools is: https://developer.android.com/studio/releases ###### Updates performed - Version update ###### To inspect upstream changes ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 15859902 with grep in /nix/store/ggj27gf7l8g0x485igp8mzasbdab2638-android-studio-tools-15859902 - found 15859902 in filename of file in /nix/store/ggj27gf7l8g0x485igp8mzasbdab2638-android-studio-tools-15859902 ---
Rebuild report (if merged into master) (click to expand) ``` 4 total rebuild path(s) 2 package rebuild(s) First fifty rebuilds by attrpath android-studio-tools ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/ggj27gf7l8g0x485igp8mzasbdab2638-android-studio-tools-15859902 \ --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 android-studio-tools https://github.com/r-ryantm/nixpkgs/archive/5f5ca071b5cd396482d1e3154ee76eaff176c0fe.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/5f5ca071b5cd396482d1e3154ee76eaff176c0fe#android-studio-tools ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/ggj27gf7l8g0x485igp8mzasbdab2638-android-studio-tools-15859902 ls -la /nix/store/ggj27gf7l8g0x485igp8mzasbdab2638-android-studio-tools-15859902/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`](https://github.com/Mic92/nixpkgs-review). Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'` Commit: `5f5ca071b5cd396482d1e3154ee76eaff176c0fe` --- ### `x86_64-linux`
:white_check_mark: 1 package built:
--- ###### Maintainer pings cc @Pandapip1 @RossComputerGuy @numinit @johnrtitor @adrian-gierakowski @hadilq for [testing](https://github.com/nix-community/nixpkgs-update/blob/main/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do). > [!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`](https://github.com/NixOS/nixpkgs/blob/master/ci/README.md#nixpkgs-merge-bot). https://api.github.com/repos/NixOS/nixpkgs/pulls/544019