Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 806097 - net-vpn/protonvpn-cli-2.2.11/3.7.2 version bump
Summary: net-vpn/protonvpn-cli-2.2.11/3.7.2 version bump
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Amel Hodzic
Keywords: PullRequest
Depends on:
Reported: 2021-08-01 23:34 UTC by Esteve Varela Colominas
Modified: 2021-12-29 12:26 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Esteve Varela Colominas 2021-08-01 23:34:49 UTC
A new version of protonvpn-cli has been released:

Many things have changed, but no comprehensive changelog could be found.
Comment 1 Ionen Wolkens gentoo-dev 2021-08-02 17:10:56 UTC
I don't think that's the same package, net-vpn/protonvpn-cli is:

Not that it isn't outdated too, current latest being 2.2.11
Comment 2 Esteve Varela Colominas 2021-08-02 18:31:20 UTC
It's the official continuation of old CLI, see the of linux-cli-community:
> The official ProtonVPN Linux app is available for Debian 10, Ubuntu 20+, Mint 19+, MX Linux 19+, Fedora 31+ and Archlinux / Manjaro. Where possible, we recommend that you upgrade to the official app. The community Linux client described below remains available for those who need it.

It's true that both CLIs are incompatible, but unless both CLIs are to be packaged, I'd suggest packaging the new one. I'm not aware of specific reasons to use one over the other, other than that -community might be phased out in the future. Though I should check if the new CLI supports anything other than networkmanager-based setups, as that'd be a reason for me to keep using the old one.

Depending on this and what the maintainer prefers I'll file a new package request.
Comment 3 Amel Hodzic 2021-09-07 05:05:50 UTC
Thank you for pointing this out.  I'll have to review the status of both; most likely I'll just bump this version to the latest available.
Comment 4 Amel Hodzic 2021-10-26 04:40:38 UTC
Sorry, I haven't had much time lately to deal with this.  Last I checked, I was a bit lost still about the changes that were implemented upstream.  Trying to keep track of the various implementations that they have had...
Comment 5 Amel Hodzic 2021-10-26 05:03:23 UTC
yeah, the latest version seems to be renamed to "linux-cli-community".  If someone wants to take the new implementation and move this ebuild accordingly as well, I'm fine with that.  Otherwise, I'll update this to the most recent version and leave it at that; i.e. 2.2.11, as of right now (2021-10-26).
Comment 6 Amel Hodzic 2021-12-29 12:26:33 UTC
This can probably be closed, as the package was updated to the latest version available, which was (part of?) the reason that this bug-report was created.  

As for the "new"er application that was referenced here, we could create a new bug-report if/when someone decides to implement that.  As I eluded to before, there have been multiple similar implementation changes; e.g. previously, there was a client that was written in bash; then, the project was rewritten in python; now, some further breaking changes seem to have been introduced and it was forked into a new project or entirely rewritten again.  So, once again, I will stick with the "linux-cli-community" implementation for the time being.