Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: smartdns 47 -> 48.2 https://repology.org/project/smartdns/versions attrpath: smartdns Checking auto update branch... An auto update branch exists with message `smartdns: 47 -> 48.1`. New version is 48.2. The auto update branch does not match or exceed the new version. [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/sm/smartdns/package.nix b/pkgs/by-name/sm/smartdns/package.nix index e9e260daceca..3e6cd514aa1d 100644 --- a/pkgs/by-name/sm/smartdns/package.nix +++ b/pkgs/by-name/sm/smartdns/package.nix @@ -9,13 +9,13 @@ stdenv.mkDerivation (finalAttrs: { pname = "smartdns"; - version = "47"; + version = "48.2"; src = fetchFromGitHub { owner = "pymumu"; repo = "smartdns"; rev = "Release${finalAttrs.version}"; - hash = "sha256-8OK1OV3Jvj/5nUOxnWTTQAa1Qe3RGxNwJhYEZ7O1RIE="; + hash = "sha256-QSE1vLjZS6K/mpHeIbJn5SVkZZ2NgelXtB/9rspHPxs="; }; buildInputs = [ openssl ]; 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: `614a028f7674f47ea893abc6e770bab606788e17` --- ### `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/smartdns/versions. meta.description for smartdns is: Local DNS server to obtain the fastest website IP for the best Internet experience meta.homepage for smartdns is: https://github.com/pymumu/smartdns ###### Updates performed - Version update ###### To inspect upstream changes - [Release on GitHub](https://github.com/pymumu/smartdns/releases/tag/Release48.2) - [Compare changes on GitHub](https://github.com/pymumu/smartdns/compare/Release47...Release48.2) ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 48.2 with grep in /nix/store/rvy4fbafxd5i6j1hs36czmcc5y82ni5w-smartdns-48.2 - found 48.2 in filename of file in /nix/store/rvy4fbafxd5i6j1hs36czmcc5y82ni5w-smartdns-48.2 ---
Rebuild report (if merged into master) (click to expand) ``` 4 total rebuild path(s) 2 package rebuild(s) First fifty rebuilds by attrpath smartdns ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/rvy4fbafxd5i6j1hs36czmcc5y82ni5w-smartdns-48.2 \ --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 smartdns https://github.com/r-ryantm/nixpkgs/archive/614a028f7674f47ea893abc6e770bab606788e17.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/614a028f7674f47ea893abc6e770bab606788e17#smartdns ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/rvy4fbafxd5i6j1hs36czmcc5y82ni5w-smartdns-48.2 ls -la /nix/store/rvy4fbafxd5i6j1hs36czmcc5y82ni5w-smartdns-48.2/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: `614a028f7674f47ea893abc6e770bab606788e17` --- ### `x86_64-linux`
:white_check_mark: 1 package built:
--- ###### Maintainer pings cc @LEXUGE 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). Updated existing PR https://api.github.com/repos/NixOS/nixpkgs/pulls/463171