From nobody Tue Dec 12 13:29:54 2023 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SqKH01BbVz53yXX for ; Tue, 12 Dec 2023 13:30:04 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.netfence.it (mailserver.netfence.it [78.134.96.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mailserver.netfence.it", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SqKGz168gz4Fqq for ; Tue, 12 Dec 2023 13:30:03 +0000 (UTC) (envelope-from ml@netfence.it) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=netfence.it header.s=202310 header.b=ByFWFzmA; spf=pass (mx1.freebsd.org: domain of ml@netfence.it designates 78.134.96.152 as permitted sender) smtp.mailfrom=ml@netfence.it; dmarc=pass (policy=none) header.from=netfence.it Received: from [10.1.2.18] (alamar.local.netfence.it [10.1.2.18]) (authenticated bits=0) by soth.netfence.it (8.17.2/8.17.1) with ESMTPSA id 3BCDTsER089278 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for ; Tue, 12 Dec 2023 14:29:54 +0100 (CET) (envelope-from ml@netfence.it) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netfence.it; s=202310; t=1702387794; bh=N34U9mwbLjf3JLOTM6CYSi3ShCWdAxz7mnmnpDBvlac=; h=Date:Subject:To:References:From:In-Reply-To; b=ByFWFzmAHpxthOsJNns0ieYjH0GpYaN50R8fHFKvqyTb881q2NOnvryICaAojY1su awmQiEfDd+fqwiMiAu/YuqDIqFvL2H+SHCyjZRaSr7BZXFuLmd/09JfnpnqO/NUdV5 bPqTTMf3izrbZ1dcm0Ip1Dhr4/mfi7CKONFvQ/p4= X-Authentication-Warning: soth.netfence.it: Host alamar.local.netfence.it [10.1.2.18] claimed to be [10.1.2.18] Message-ID: <447588a2-38b9-4644-ad38-c2822577c9f5@netfence.it> Date: Tue, 12 Dec 2023 14:29:54 +0100 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: signal-cli not working anymore (help porting) Content-Language: en-US To: ports@freebsd.org References: From: Andrea Venturoli In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; DMARC_POLICY_ALLOW(-0.50)[netfence.it,none]; R_SPF_ALLOW(-0.20)[+ip4:78.134.96.152]; R_DKIM_ALLOW(-0.20)[netfence.it:s=202310]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; ASN(0.00)[asn:35612, ipnet:78.134.0.0/17, country:IT]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[ports@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[netfence.it:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_XAW(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[ports@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4SqKGz168gz4Fqq X-Spamd-Bar: --- On 12/9/23 12:27, Andrea Venturoli wrote: > Has anyone tried working on updating it? > If so, what are the problems blocking such an update? Well, no one answered, so I'm giving it a try in my spare time. I started upgrading net-im/libsignal-client, but I already came to a showstopper (probably because I know close to nothing about rust :( ). I've followed the Porters' Handbook on the make makesum/make cargo-crates/make makesum instructions. However, the port build fails with: > Running `/usr/ports/net-im/libsignal-client/work/target/release/build/boring-sys-0dffa970497cad40/build-script-build` > [boring-sys 2.1.0] cargo:rerun-if-env-changed=BORING_BSSL_PATH > [boring-sys 2.1.0] cargo:warning=fetching boringssl git submodule > [boring-sys 2.1.0] error: pathspec 'deps/boringssl' did not match any file(s) known to git > [boring-sys 2.1.0] thread 'main' panicked at 'failed to fetch submodule - consider running `git submodule update --init --recursive deps/boringssl` yourself', /usr/ports/net-im/libsignal-client/work/boring-3809a7e1ca2f60a9495620da514f8432f148cde7/boring-sys/build.rs:447:17 > [boring-sys 2.1.0] stack backtrace: > [boring-sys 2.1.0] 0: std::panicking::begin_panic > [boring-sys 2.1.0] 1: build_script_build::main::{{closure}} > [boring-sys 2.1.0] 2: core::result::Result::unwrap_or_else > [boring-sys 2.1.0] 3: build_script_build::main > [boring-sys 2.1.0] 4: core::ops::function::FnOnce::call_once > [boring-sys 2.1.0] note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. > The following warnings were emitted during compilation: > > warning: fetching boringssl git submodule > > error: failed to run custom build command for `boring-sys v2.1.0 (/usr/ports/net-im/libsignal-client/work/boring-3809a7e1ca2f60a9495620da514f8432f148cde7/boring-sys)` > note: To improve backtraces for build dependencies, set the CARGO_PROFILE_RELEASE_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation. > > Caused by: > process didn't exit successfully: `/usr/ports/net-im/libsignal-client/work/target/release/build/boring-sys-0dffa970497cad40/build-script-build` (exit status: 101) > --- stdout > cargo:rerun-if-env-changed=BORING_BSSL_PATH > cargo:warning=fetching boringssl git submodule > > --- stderr > error: pathspec 'deps/boringssl' did not match any file(s) known to git > thread 'main' panicked at 'failed to fetch submodule - consider running `git submodule update --init --recursive deps/boringssl` yourself', /usr/ports/net-im/libsignal-client/work/boring-3809a7e1ca2f60a9495620da514f8432f148cde7/boring-sys/build.rs:447:17 > stack backtrace: > 0: std::panicking::begin_panic > 1: build_script_build::main::{{closure}} > 2: core::result::Result::unwrap_or_else > 3: build_script_build::main > 4: core::ops::function::FnOnce::call_once > note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. > *** Error code 101 > > Stop. I guess this is because of the following in Cargo.toml: > # Use our fork of curve25519-dalek for zkgroup support. > curve25519-dalek = { git = 'https://github.com/signalapp/curve25519-dalek', tag = 'signal-curve25519-4.0.0' } > boring = { git = 'https://github.com/signalapp/boring', branch = 'libsignal' } I tried playing with CARGO_USE_GITHUB=yes & Co., but I got up to nothing. Any hint is appreciated. bye & Thanks av.