Hi Francisco! Thank you for the information provided. I didn't know you were a maintainer of this package in the past. If you want to keep it, feel free.
As you may know, I've been working on this project for two years. During this period, the project underwent some changes, but all were resolved. Yes, I have exchanged several emails and participated in various discussions about the project with members of the project's official team. https://github.com/ProtonVPN/proton-vpn-cli/graphs/contributors https://github.com/ProtonVPN/proton-vpn-gtk-app/issues/69#issuecomment-2694617150 Currently, I am uploading most of the packages needed to run proton-vpn-gtk-app on Debian. I recently received an email, I believe from the ProtonVPN team leader. In it, they ask for my help with a package https://github.com/ProtonVPN/local-agent-rs written in Rust, which, due to the absence of a dependency, we had to fix to make it work. If you want to check it out: https://salsa.debian.org/python-team/packages/python-proton-vpn-local-agent > Hi Nilson, > I hope this message finds you well! I'm Pep, Proton VPN's Linux team lead. > I'm reaching out because we > received quite a few bug reports from debian > users installing our app from Proton VPN's debian repositories. > The issue > is that our python3-proton-vpn-local-agent gets replaced by the version you > are maintaining in > Debian Trixie repos, which results in the following > crash due to a missing dependency: > thread 'tokio-runtime-worker' (7463) panicked at > /usr/share/cargo/registry/rustls-> 0.23.37/src/crypto/mod.rs:249:14: Could > not automatically determine the process-level CryptoProvider from > Rustls > crate features. Call CryptoProvider::install_default() before this point to > select a provider manually, > or make sure exactly one of the 'aws-lc-rs' and > 'ring' features is enabled. See the documentation of the > CryptoProvider > type for more information. > The issue is that the rustls crate relies on aws-lc-rs, which is not packaged > for debian (librust-aws-lc-rs-> dev in not available). > In the meantime, we published a new python3-proton-vpn-local-agent version to > our Proton VPN debian > repositories so that apt chooses this newer version > over the older one from official Debian repos. > Would you be willing to collaborating with us to get this sorted and to have > Proton VPN published in the > official Debian repositories? > Looking forward to hearing from you! > Best, > Pep > Proton AG I created its repository on Salsa: https://salsa.debian.org/python-team/packages/proton-vpn-cli, with the current project name, which differs from yours. Regarding your version, I think they started a new project. Considering that the version you maintained was protonvpn-cli (2.2.4-1) and the one I intend to make available on Debian is https://github.com/ProtonVPN/proton-vpn-cli/tags 0.7.1. I'm finalizing the new package to send for review. This morning I received a test account to test all the commands in the CLI version. > Amazing! Here's a test account: > username: [email protected] If you want to continue maintaining this package, feel free. I'll be waiting! Nilson F. Silva
