[Bug 293318] New port net/telemt - MTProxy for Telegram on Rust + Tokio

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293318

Yusuf Yaman <nxjoseph@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
           Assignee|ports-bugs@FreeBSD.org      |nxjoseph@freebsd.org
           Severity|Affects Only Me             |Affects Some People
             Status|New                         |Closed

--- Comment #25 from Yusuf Yaman <nxjoseph@freebsd.org> ---
I think you're right on your points.

I have committed this port to the tree after testing with Poudriere on
14.4-RELEASE-amd64-main-7c7aef17f3c6 and it seems OK. In `make test`, 6 tests
failed, I guess they're caused by strict jail.



failures:
   
proxy::client::security_tests::idle_pooled_connection_closes_cleanly_in_client_handler_path
   
proxy::direct_relay::security_tests::adversarial_check_then_symlink_flip_is_blocked_by_nofollow_open
   
proxy::direct_relay::security_tests::adversarial_parent_swap_after_check_is_blocked_by_anchored_open
   
proxy::direct_relay::security_tests::anchored_open_rejects_existing_symlink_target
   
proxy::direct_relay::security_tests::unknown_dc_open_append_rejects_broken_symlink_target_with_nofollow
   
proxy::direct_relay::security_tests::unknown_dc_open_append_rejects_symlink_target_with_nofollow

test result: FAILED. 1701 passed; 6 failed; 68 ignored; 0 measured; 0 filtered
out; finished in 172.47s

I also slightly adjusted like this:

-USES=  cargo
+USES=          cargo

 USE_GITHUB=    yes
-GH_ACCOUNT=    telemt
-GH_PROJECT=    telemt
 USE_RC_SUBR=   ${PORTNAME}

-.include "${.CURDIR}/Makefile.crates"
-

pkg-descr:

-production-ready improvements such as connection pooling,
-replay protection, detailed statistics, masking from "prying" eyes.
+production-ready improvements such as connection pooling, replay
+protection, detailed statistics, masking from "prying" eyes.


I tried running the daemon service, it seems to launch fine, I won't be able to
test further than that though.

-- 
You are receiving this mail because:
You are the assignee for the bug.