client packages by @ivaradi for Debian 7 Wheezy, 8 Jessie and 9 Stretch (and 9.0_update which I guess is buster?). This project is on OBS, currently has no Dolphin integration.
For flatpack run: flatpak install --from https://flathub.org/repo/appstream/org.nextcloud.Nextcloud.flatpakref
After installing you can start the client using ```flatpak run org.nextcloud.Nextcloud````
There is a snap you can install with sudo snap install --edge nextcloud-client-kyrofa but it seems unmaintained at the moment.
THANK YOU to all distribution packagers. Amazing documentation too, btw! Some good migration documentation and so on. Very nice work, showing once again the power of community!
For instructions how to convert from the ownCloud client to the Nextcloud client see here.
Feedback, updates, new packages - please let me know below and I’ll update this post.
I thought that the point was not to use repos any longer because the updater was the right way to do it.
I have long been a proponent of repo based methods for reliability, but I have finally given up on that for Nextcloud because they chose not to do anything official with repos after leaving ownCloud.
It’s also for the client, there repos are really useful. For the server it still can be nice but the main purpose was that NC does not have to manage the repos themselves.
@jospoortvliet: good idea to put all repos together and I agree on keeping this list updated.
Well, speaking of the client and repos, where does chocolatey fit into the picture? Someone has submitted it there and that is awesome as I use Chocolatey to manage applications on Windows machines.
Never heard of it before but hey, it would be great to have it in there.
Note that all the packages are provided by the distributions, not us - that is how it works on Linux in general… When they are included officially (like in openSUSE, Arch) that makes it super easy to install for users.
WRT packages vs tarball with our updater, I think the updater is generally a better solution because I know and trust the team maintaining that part (us…) but of course it is totally understandable that some people prefer packages or trust their distribution to keep things up to date.
It is an awesome tool for Windows admins. I would suggest that you reach out to whoever put it in there to make sure it is pointing to the proper source and all that.
Hello, I just want to tell you guys, that Nextcloud is avariable on OpenBSD-current, on the ports tree and also packages, the very last version to this point.
To confirm NextCloud 11 will be packaged for EPEL7 as the bump in PHP minimum version isn’t until NC12.
At that point I’m not sure what I’ll do yet, as I cannot use SCL in an EPEL package.
My options are:
To maintain 11 for as long as NC maintains support for 11
To retire from EPEL and see if I can maintain it as part of the CentOS SCL SIG
To advise people to use upstream packages, or to switch to RemiRepo, as I believe Remi will continue to maintain it on his PHP stack there using the Fedora SRPMs I’ll be generating
To use the upcoming Fedora nextcloud container on an EL7 box using docker/runc.
However, that decision is indeed still a little way off.
In terms of Fedora at least Nextcloud will be maintained so long as it exists
I ended up packaging NC 10 rather than the 11 build to get through the review quicker as there were some dependency issues.
.