Actual stable Ebuild was removed with this commit: https://github.com/gentoo/gentoo/commit/d64934420550149a01f1e8c28c4a04e478a866b9 Please restore it.
This package has never been stabilised.
(In reply to Andreas Sturmlechner from comment #1) > This package has never been stabilised. Yes you are right, I had forgotten to look in my files under package.keywords. The problem is that the versions >=2.5.0 require >=dev-libs/openssl-1.1.0:0. There is a porting tracker bug ticket for openssl, but not even a stabilization tracker ticket. That's why mostly stable users like me, currently do not want to or can not switch to the newer version of openssl, and only because of this one package here. Of course I could solve the problem for myself and put the ebuild in my local overlay. But I think I'm not the only one affected here.
Thanks for the report! Indeed, current nextcloud-client requires openssl-1.1, but I am afraid it is the price to pay to use it. 2.3.3 was just a reskinned owncloud-client, is not supported upstream anymore ( https://github.com/nextcloud/client_theming ), and as both apps diverge more and more, will probably not work properly with newer nextcloud releases. So from a disto perspective, it was more than enough time to clean it (and yes sadly we lag behind on stable openssl-1.1 support). Until 2.5.x can be easily installed on stable systems, I guess it is down to local/alternate solutions: local overlay for 2.3, generic webdav client or upstream appimage binary
Thank you for the detailed comment Bernard. I can understand your point of view. Yesterday I changed my main system (~1,900 packages] to openssl-1.1.0 and then made some stabilization request tickets for the few missing packages. Actually, when these tickets are done, it should then not take much longer to finally stabilize openssl-1.1.0.
Thanks for filling them! As recent good news, we now have a tracker to stable openssl 1.1: https://bugs.gentoo.org/684590 And a stable request for nextcloud-client I kept open now depends on it: https://bugs.gentoo.org/show_bug.cgi?id=674740 So, soon even with only stable keywords you should get an "emergable" nextcloud-client
