go-ios: 1.0.202 -> 1.0.204

[r-ryantm]

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

meta.description for go-ios is: Operating system independent implementation of iOS device features

meta.homepage for go-ios is: https://github.com/danielpaulus/go-ios

Updates performed

• Ran passthru.UpdateScript

To inspect upstream changes

• Release on GitHub

• Compare changes on GitHub

Impact

Checks done

---

• built on NixOS
• The tests defined in passthru.tests, if any, passed
• found 1.0.204 in filename of file in /nix/store/pdr3lhy1h54d47xws4j77r31x7h1gdcs-go-ios-1.0.204

---

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

go-ios

Instructions to test this update (click to expand)

---

Either download from the cache:

nix-store -r /nix/store/pdr3lhy1h54d47xws4j77r31x7h1gdcs-go-ios-1.0.204 \
  --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 go-ios https://github.com/r-ryantm/nixpkgs/archive/366a2a06f5af492987f9f204c472d19db816f582.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/366a2a06f5af492987f9f204c472d19db816f582#go-ios

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

ls -la /nix/store/pdr3lhy1h54d47xws4j77r31x7h1gdcs-go-ios-1.0.204
ls -la /nix/store/pdr3lhy1h54d47xws4j77r31x7h1gdcs-go-ios-1.0.204/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 failed

---

Maintainer pings

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