aaaaxy: 1.6.64 -> 1.6.176

[r-ryantm]

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/divVerent/aaaaxy/releases.

meta.description for aaaaxy is: Nonlinear 2D puzzle platformer taking place in impossible spaces

meta.homepage for aaaaxy is: https://divverent.github.io/aaaaxy/

Updates performed

• Golang update

To inspect upstream changes

Impact

Checks done

---

• built on NixOS

Caution

A test defined in passthru.tests did not pass.

• found 1.6.176 with grep in /nix/store/injq8h415w0w2wm23l2h0inpfnr3vyas-aaaaxy-1.6.176
• found 1.6.176 in filename of file in /nix/store/injq8h415w0w2wm23l2h0inpfnr3vyas-aaaaxy-1.6.176

---

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

aaaaxy

Instructions to test this update (click to expand)

---

Either download from the cache:

nix-store -r /nix/store/injq8h415w0w2wm23l2h0inpfnr3vyas-aaaaxy-1.6.176 \
  --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 aaaaxy https://github.com/r-ryantm/nixpkgs/archive/fe66309160e0c99cdcbfab63a0a18f57a4568079.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/fe66309160e0c99cdcbfab63a0a18f57a4568079#aaaaxy

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

ls -la /nix/store/injq8h415w0w2wm23l2h0inpfnr3vyas-aaaaxy-1.6.176
ls -la /nix/store/injq8h415w0w2wm23l2h0inpfnr3vyas-aaaaxy-1.6.176/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

✅ 2 packages built:

• aaaaxy
• aaaaxy.testing_infra

---

Maintainer pings

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

[Luflosi]

Hmm, @r-ryantm wrote:

A test defined in passthru.tests did not pass.

But on my machine it passes. Is there a way to see the logs?
I'll wait and see what OfBorg says.

@wegank you added the 2.status: merge conflict label but GitHub does not show a merge conflict. Did you add the label in error?

[wegank]

The previous merge conflict was introduced by #396749, which was later reverted in #397016.

[Luflosi]

Ah, thank you for that piece of information.

[wegank]

The test failure is not reproducible on ofborg or on my machine.