Re: [NEW] net/arti

Andrew Kloet <[email protected]>
Newsgroups gmane.os.openbsd.ports
Message-ID <[email protected]>
On Sat Aug 8, 2026 at 2:00 AM EDT, yaydn wrote:
> One of the patches doesn't apply?
>
> $ cd /usr/ports/net/arti/ && make clean build package test 2>&1 | /usr/ports/infrastructure/bin/portslogger .
>
> ===>  Patching for arti-2.5.1
> ===>   Applying OpenBSD patch patch-crates_arti_src_arti-example-config_toml
> Hmm...  Looks like a unified diff to me...
> The text leading up to this was:
> --------------------------
> |Index: crates/arti/src/arti-example-config.toml
> |--- crates/arti/src/arti-example-config.toml.orig
> |+++ crates/arti/src/arti-example-config.toml
> --------------------------
> Patching file crates/arti/src/arti-example-config.toml using Plan A...
> Hunk #1 succeeded at 94.
> Hunk #2 succeeded at 199.
> Hunk #3 succeeded at 209.
> done
> ===>   Applying OpenBSD patch patch-crates_arti_src_cfg_rs
> Hmm...  Looks like a unified diff to me...
> The text leading up to this was:
> --------------------------
> |Our config patch breaks this test
> |
> |Index: crates/arti/src/cfg.rs
> |--- crates/arti/src/cfg.rs.orig
> |+++ crates/arti/src/cfg.rs
> --------------------------
> Patching file crates/arti/src/cfg.rs using Plan A...
> Hunk #1 succeeded at 763.
> done
> ===>   Applying OpenBSD patch patch-crates_tor-dirserver_src_http_rs
> Hmm...  Looks like a unified diff to me...
> The text leading up to this was:
> --------------------------
> |Backported fix from upstream:
> |https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4286
> |
> |Index: crates/tor-dirserver/src/http.rs
> |--- crates/tor-dirserver/src/http.rs.orig
> |+++ crates/tor-dirserver/src/http.rs
> --------------------------
> Patching file crates/tor-dirserver/src/http.rs using Plan A...
> Hunk #1 succeeded at 887.
> done
> ===>   Applying OpenBSD patch patch-crates_tor-dirserver_src_mirror_operation_rs
> Hmm...  Looks like a unified diff to me...
> The text leading up to this was:
> --------------------------
> |Backported fix from upstream:
> |https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4286
> |
> |Index: crates/tor-dirserver/src/mirror/operation.rs
> |--- crates/tor-dirserver/src/mirror/operation.rs.orig
> |+++ crates/tor-dirserver/src/mirror/operation.rs
> --------------------------
> Patching file crates/tor-dirserver/src/mirror/operation.rs using Plan A...
> Hunk #1 succeeded at 924.
> Hunk #2 succeeded at 984.
> done
> ===>   Applying OpenBSD patch patch-crates_tor-memquota_Cargo_toml
> Hmm...  Looks like a unified diff to me...
> The text leading up to this was:
> --------------------------
> |Needed for patch-crates_tor-memquota_src_config_rs
> |
> |Index: crates/tor-memquota/Cargo.toml
> |--- crates/tor-memquota/Cargo.toml.orig
> |+++ crates/tor-memquota/Cargo.toml
> --------------------------
> Patching file crates/tor-memquota/Cargo.toml using Plan A...
> Hunk #1 succeeded at 20.
> done
> ===>   Applying OpenBSD patch patch-crates_tor-memquota_src_config_rs
> Hmm...  Looks like a unified diff to me...
> The text leading up to this was:
> --------------------------
> |The sysinfo crate does not have support for OpenBSD yet.
> |https://github.com/GuillaumeGomez/sysinfo/issues/1318
> |
> |Index: crates/tor-memquota/src/config.rs
> |--- crates/tor-memquota/src/config.rs.orig
> |+++ crates/tor-memquota/src/config.rs
> --------------------------
> Patching file crates/tor-memquota/src/config.rs using Plan A...
> Ignoring previously applied (or reversed) patch.
> Hunk #1 ignored at 1.
> Hunk #2 ignored at 292.
> 2 out of 2 hunks ignored--saving rejects to crates/tor-memquota/src/config.rs.rej
> done
> ***>   patch-crates_tor-memquota_src_config_rs did not apply cleanly
> ===>   Applying OpenBSD patch patch-modcargo-crates_aws-lc-sys-0_42_0_aws-lc_third_party_s2n-bignum_s2n-bignum-imported_x86_att_curve25519_curve25519_x25519base_alt_S
> Hmm...  Looks like a unified diff to me...
> The text leading up to this was:
> --------------------------
> |aws-lc-sys vendors AWS-LC, which vendors s2n-bignum.
> |The x86_att curve25519_x25519base_alt implementation placed
> |readonly Edwards25519 tables in .text. OpenBSD maps .text
> |execute-only, causing SIGSEGV when the assembly loads the tables.
> |
> |Issue will persist until aws-lc bumps the vendored s2n-bignum to commit:
> |4d9b2c1793412692d54b4e2a8cf08123078778c7
> |
> |Related issue for vendored s2n-bignum:
> |https://github.com/aws/aws-lc/issues/3408
> |
> |Index: modcargo-crates/aws-lc-sys-0.42.0/aws-lc/third_party/s2n-bignum/s2n-bignum-imported/x86_att/curve25519/curve25519_x25519base_alt.S
> |--- modcargo-crates/aws-lc-sys-0.42.0/aws-lc/third_party/s2n-bignum/s2n-bignum-imported/x86_att/curve25519/curve25519_x25519base_alt.S.orig
> |+++ modcargo-crates/aws-lc-sys-0.42.0/aws-lc/third_party/s2n-bignum/s2n-bignum-imported/x86_att/curve25519/curve25519_x25519base_alt.S
> --------------------------
> Patching file modcargo-crates/aws-lc-sys-0.42.0/aws-lc/third_party/s2n-bignum/s2n-bignum-imported/x86_att/curve25519/curve25519_x25519base_alt.S using Plan A...
> Hunk #1 succeeded at 2360.
> Hunk #2 succeeded at 2379.
> Hunk #3 succeeded at 2401.
> done
> ===>   Failed patches: 
>
>     patch-crates_tor-memquota_src_config_rs
>
> *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2949 '/usr/ports/pobj/arti-2.5.1/.patch_done': @if cd /usr/ports/net/arti/patches...)
> *** Error 2 in /usr/ports/net/arti (/usr/ports/infrastructure/mk/bsd.port.mk:2722 'build': @lock=arti-2.5.1;  export _LOCKS_HELD=" arti-2.5....)
> --
>
> Attached the log.

Apologies, attatched is an updated tarball.
I had forgotten to test after making some final edits

Andrew
arti.tar.gz (application/gzip, 55.4 KB) - not displayed
signature.asc (application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQQDYAWAj/Md1ZRJrhK0H7x/oPHhDgUCanc9gwAKCRC0H7x/oPHh
DrBlAQDvX6QdE6clSIAQHkG1+2iUihuPJlR8uhaSqOdFBqVuZQEAvFn2IjZWzP9Y
N8/dEtpQ6w0aImZ4f7J+pq7WmqWDfgo=
=hnHj
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.