Despite efforst the Nextcloud Desktop version in Discover and dnf5 are still stale, broken versions. Yes I know there are AppImage and Flatpak versions. The version has a e2ee version that is incompatible with other version and seriously breaks users files making the inaccessible.
It is beyond my comprehension why this is not addressed. And why there are no means to discuss this with Fedora package managemen.
What would the means be to have this package removed?
From the report which you link, simply updating the client is not a full solution. It might be a prerequisite, but even that is not clear.
You mentioned “efforts” but did not link to them. So you may or may not have undertaken some of these steps:
Complaining here in this way won’t get you far.
I suggest you manage your expectations, fedora is maintained by volunteers.
If you require better, try looking elsewhere!
is this about nextcloud-client?
'tis. And I am not I repeat not complaing here. I want to point out a flaring ommision at Fedora’s package management triage.
I found this forum thread because it was not clear for me how the update policy for nextcloud-client is.
Upfront, also I’m not here to complain, but I looking for clarification on the update process, so that I can make a well informed decision whether to move to a flatpak or AppImage install.
The current nextcloud-client version in the Fedora repository is 4.0.7. The latest 4.0.x release is: 4.0.10.
The latest released nextcloud-client version is 33.0.5.
Nextcloud-client is an important application for me that I use continuously. My question is: what is the update policy for nextcloud-client? Will Fedora follow minor releases, on what time-frame? What will trigger the process of providing a new major release?
And, a huge thanks to all people who work on Fedora and the nextcloud-client package for providing such a great distro with important packages all in the repositories!
For whatever reason these pages don’t seem to surface that high in search results, but there are documentation pages for these topics: Updates Policy, Non-responsive maintainer policy
Thanks, I followed the Non-responsive maintainer policy, and filed this bug:
I asked here in the Fedora devel mailing list if the nextcloud-client package is still being maintained.
FTR: nextcloud-client currently fails to build in fedora rawhide (45) because of the openssl version (4 vs 3). I"ve filed a PR which solves this.
Updating nextcloud-client from 4.0.7 to 4.0.11 would be no biggy. I don’t know about the 33.x branch. 34.x is not stable yet.
Still, it seems there is no active maintainer.
“I could not resist.”
If you feel curious and have backups, please try Making sure you're not a bot!
and report back. It’s a build of the Fedora package with minimal adjustments so that it provides version 33.0.7, the latest on the 33.x branch. I have not done any testing myself, and I’m not the Fedora maintainer of that package (but of a few others).
Thanks @mjg. Unfortunately, I do not have a test system at hand to do some testing. And I do not want to put my production computers at risk. Maybe I will setup a VM later to do some testing.
For now I also created this Non-responsive maintainer FESCo ticket.
FYI: nextcloud-client 34 has landed in Fedora 44 and up. Thanks to whoever took care of it !
First look is promising.
In ticket Non-responsive maintainer FESCo ticket it is confirmed that the nextcloud-client package is still maintained.