arti: 1.2.8 -> 1.3.0

[r-ryantm]

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/arti/versions.

meta.description for arti is: Implementation of Tor in Rust

meta.homepage for arti is: https://arti.torproject.org/

meta.changelog for arti is: https://gitlab.torproject.org/tpo/core/arti/-/blob/arti-v1.3.0/CHANGELOG.md

Updates performed

• Rust version update

To inspect upstream changes

Impact

Checks done

---

• built on NixOS
• The tests defined in passthru.tests, if any, passed
• found 1.3.0 with grep in /nix/store/wasvmbjzz3pv7v6df3lla8cadqjnf16s-arti-1.3.0
• found 1.3.0 in filename of file in /nix/store/wasvmbjzz3pv7v6df3lla8cadqjnf16s-arti-1.3.0

---

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

arti

Instructions to test this update (click to expand)

---

Either download from Cachix:

nix-store -r /nix/store/wasvmbjzz3pv7v6df3lla8cadqjnf16s-arti-1.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix 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 arti https://github.com/r-ryantm/nixpkgs/archive/8b88b3a235421861d84b13653852edf551b14215.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/8b88b3a235421861d84b13653852edf551b14215#arti

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

ls -la /nix/store/wasvmbjzz3pv7v6df3lla8cadqjnf16s-arti-1.3.0
ls -la /nix/store/wasvmbjzz3pv7v6df3lla8cadqjnf16s-arti-1.3.0/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:

• arti

---

Maintainer pings

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

[natsukium]

1.3.0 has breaking changes. https://gitlab.torproject.org/tpo/core/arti/-/blob/arti-v1.3.0/CHANGELOG.md#breaking-changes

[Steinhagen]

@natsukium The basic functionality works as expected. Should this be merged as is? Since the changes are caused by the application itself and not something nix causes, I don't think we need to mention this anywhere.

[natsukium]

According to the release schedule, all breaking changes had been restricted since October 25.
Now it has done branch-off, and we can merge it.