# Linux packages status

**URL:** <https://help.nextcloud.com/t/linux-packages-status/10216>\
**Category:** ℹ️ Support\
**Created:** [March 16, 2017, 11:32am UTC](https://help.nextcloud.com/t/linux-packages-status/10216 "2017-03-16T11:32:08Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![jospoortvliet](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jospoortvliet/32/3_2.png) [@jospoortvliet](https://help.nextcloud.com/u/jospoortvliet)\
**Post date:** [March 16, 2017, 11:32am UTC](https://help.nextcloud.com/t/linux-packages-status/10216/1 "2017-03-16T11:32:09Z")

</div>

We now have packages for all major distributions:

- [Fedora](https://www.hogarthuk.com/?q=node/17) (server & client included) & RHEL (server & client in EPEL7 repo)
- openSUSE & SLE (server in [offical server applications OBS (how-to)](https://en.opensuse.org/SDB:Nextcloud), client included)
- Debian and Ubuntu Server:
  - [client and server packages by @morph027](http://repo.morph027.de/#nextcloud-server). This project is on [gitlab](https://gitlab.com/packaging/nextcloud). (NOTE: seems no longer maintained :()
    - [Stretch and Jessie pacakages for server and client](https://www.jurisic.org/index.php) by @ijurisic

- Debian Client:
  - [client packages by @ivaradi](http://download.opensuse.org/repositories/home:/ivaradi/) for Debian 7 Wheezy, 8 Jessie and 9 Stretch (and `9.0_update` which I guess is buster?). This project is on [OBS](https://build.opensuse.org/package/show/home:ivaradi/nextcloud-client), currently has no Dolphin integration.
  - [client packages by @m4lvin](https://m4lvin.github.io/nextcloud-client-debian-packaging/) for Debian 9 Stretch only. This project is on [github](https://github.com/m4lvin/nextcloud-client-debian-packaging) and [built on travis-ci.org](https://travis-ci.org/m4lvin/nextcloud-client-debian-packaging), with Dolphin integration.

- Ubuntu Client:
  - [client packages by @morph027](http://repo.morph027.de/#nextcloud-client). This project is on [gitlab](https://gitlab.com/packaging/nextcloud-client/).
  - [launchpad ppa:nextcloud-devs/client](https://launchpad.net/~nextcloud-devs/+archive/ubuntu/client)

- [Arch Linux moved to Nextcloud](https://wiki.archlinux.org/index.php/Nextcloud) (server & client included)
- [Mageia moved to Nextcloud](https://wiki.mageia.org/en/OwnCloud#ownCloud_and_Nextcloud) (server & client included)
- if you have a QNAP NAS, grab a maintained image [from this community store](https://www.qnapclub.eu/index.php?act=detail&qpkg_id=348) [(forum thread here)](https://forum.qnap.com/viewtopic.php?f=320&t=124954)
- [Client and server in OpenBSD-current, on the ports tree and also packages](https://help.nextcloud.com/t/linux-packages-status/10216/18)
- Cross-distribution solutions for the server:
  - [we have a Virtual Machine image](https://www.hanssonit.se/nextcloud-vm/)
  - [and a Nextcloud Snap.](https://uappexplorer.com/snap/ubuntu/nextcloud)
  - and a [Nextcloud Docker image](https://hub.docker.com/_/nextcloud/)

- Cross-distribution solutions for the client:
  - 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````
  - On [our installation page](https://nextcloud.com/install/#install-clients) you can download an AppImage of the client.
  - 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](https://help.nextcloud.com/t/copy-the-owncloud-sync-client-configuration-when-switching-to-the-nextcloud-client/2537).

Feedback, updates, new packages - please let me know below and I’ll update this post.

---

<div class="post-metadata">

**Author:** ![jospoortvliet](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jospoortvliet/32/3_2.png) [@jospoortvliet](https://help.nextcloud.com/u/jospoortvliet)\
**Post date:** [March 16, 2017, 11:42am UTC](https://help.nextcloud.com/t/linux-packages-status/10216/2 "2017-03-16T11:42:54Z")

</div>

Pinging @James_Hogarth @morph027 @ivaradi @JasonBayton @tflidd and others that care 😉

We should perhaps keep this first post up to date and link to it from the install page. What do you think?

---

<div class="post-metadata">

**Author:** ![JasonBayton](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jasonbayton/32/297_2.png) [@JasonBayton](https://help.nextcloud.com/u/JasonBayton)\
**Post date:** [March 16, 2017, 11:55am UTC](https://help.nextcloud.com/t/linux-packages-status/10216/3 "2017-03-16T11:55:57Z")

</div>



---

<div class="post-metadata">

**Author:** ![JasonBayton](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jasonbayton/32/297_2.png) [@JasonBayton](https://help.nextcloud.com/u/JasonBayton)\
**Post date:** [March 16, 2017, 11:57am UTC](https://help.nextcloud.com/t/linux-packages-status/10216/4 "2017-03-16T11:57:35Z")

</div>

I agree this topic should be kept updated. Is installation the best category? This could well sit as a how to for Linux installation

---

<div class="post-metadata">

**Author:** ![MichaIng](https://help.nextcloud.com/user_avatar/help.nextcloud.com/michaing/32/2125_2.png) [@MichaIng](https://help.nextcloud.com/u/MichaIng)\
**Post date:** [March 16, 2017, 3:47pm UTC](https://help.nextcloud.com/t/linux-packages-status/10216/5 "2017-03-16T15:47:08Z")

</div>

No armhf package so far for raspberry pi, right? Anyway not necessary with nice new updater 🙂.

---

<div class="post-metadata">

**Author:** ![Therion7777](https://help.nextcloud.com/user_avatar/help.nextcloud.com/therion7777/32/15432_2.png) [@Therion7777](https://help.nextcloud.com/u/Therion7777)\
**Post date:** [March 16, 2017, 8:16pm UTC](https://help.nextcloud.com/t/linux-packages-status/10216/6 "2017-03-16T20:16:23Z")

</div>

> [@jospoortvliet](#):
>
> - Fedora (server & client included) & RHEL (server & client in EPL7 repo)

Only 10.0.4 from EPEL7 i Fedora – [https://apps.fedoraproject.org/packages/nextcloud](https://apps.fedoraproject.org/packages/nextcloud)

> [@Will Nextcloud be "inviting" to distribution packages?](https://help.nextcloud.com/t/will-nextcloud-be-inviting-to-distribution-packages/89/44):
>
> It is in the EPEL7 repos so easy to install on CentOS/RHEL 7 Due to PHP version limitations I can’t build this there on EL6 Do note that with the min PHP version being bumped in nextcloud 12 to 5.6 there cannot be an EPEL7 package for that then. I’m not 100% sure if I’ll continue to maintain nextcloud 11 in EPEL7 for as long as it gets updates or if it’ll be retired at that point - but that’s still some way off and I’ll have an article with the options available to people nearer the time of t…

---

<div class="post-metadata">

**Author:** ![JaredBusch](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jaredbusch/32/67_2.png) [@JaredBusch](https://help.nextcloud.com/u/JaredBusch)\
**Post date:** [March 16, 2017, 8:26pm UTC](https://help.nextcloud.com/t/linux-packages-status/10216/7 "2017-03-16T20:26:38Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/5_5575768a8748004e209b776fc1b2916d.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\
**Post date:** [March 16, 2017, 8:41pm UTC](https://help.nextcloud.com/t/linux-packages-status/10216/8 "2017-03-16T20:41:58Z")

</div>

> [@JaredBusch](#):
>
> I thought that the point was not to use repos any longer because the updater was the right way to do it.

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.

---

<div class="post-metadata">

**Author:** ![JaredBusch](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jaredbusch/32/67_2.png) [@JaredBusch](https://help.nextcloud.com/u/JaredBusch)\
**Post date:** [March 16, 2017, 9:00pm UTC](https://help.nextcloud.com/t/linux-packages-status/10216/9 "2017-03-16T21:00:09Z")

</div>

> [@tflidd](#):
>
> It’s also for the client,

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.

---

<div class="post-metadata">

**Author:** ![jospoortvliet](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jospoortvliet/32/3_2.png) [@jospoortvliet](https://help.nextcloud.com/u/jospoortvliet)\
**Post date:** [March 17, 2017, 4:30pm UTC](https://help.nextcloud.com/t/linux-packages-status/10216/10 "2017-03-17T16:30:50Z")

</div>

> [@JaredBusch](#):
>
> 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.

Good that there is choice!

---

<div class="post-metadata">

**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/5_5575768a8748004e209b776fc1b2916d.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\
**Post date:** [March 26, 2017, 9:31am UTC](https://help.nextcloud.com/t/linux-packages-status/10216/11 "2017-03-26T09:31:57Z")

</div>

4 posts were split to a new topic: [Packages for Nextcloud on RH/CentOS](https://help.nextcloud.com/t/packages-for-nextcloud-client-on-rh-centos/10682)

---

<div class="post-metadata">

**Author:** ![JaredBusch](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jaredbusch/32/67_2.png) [@JaredBusch](https://help.nextcloud.com/u/JaredBusch)\
**Post date:** [March 18, 2017, 4:38pm UTC](https://help.nextcloud.com/t/linux-packages-status/10216/14 "2017-03-18T16:38:17Z")

</div>

> [@jospoortvliet](#):
>
> Never heard of it before but hey, it would be great to have it in there.

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.

---

<div class="post-metadata">

**Author:** ![jospoortvliet](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jospoortvliet/32/3_2.png) [@jospoortvliet](https://help.nextcloud.com/u/jospoortvliet)\
**Post date:** [March 19, 2017, 1:12pm UTC](https://help.nextcloud.com/t/linux-packages-status/10216/16 "2017-03-19T13:12:25Z")

</div>

> [@JaredBusch](#):
>
> 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.

If you feel like it - you’re entirely welcome to help out with this.You clearly know more about this subject than I do, I’d just sound clueless 😉

---

<div class="post-metadata">

**Author:** ![jospoortvliet](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jospoortvliet/32/3_2.png) [@jospoortvliet](https://help.nextcloud.com/u/jospoortvliet)\
**Post date:** [March 19, 2017, 1:13pm UTC](https://help.nextcloud.com/t/linux-packages-status/10216/17 "2017-03-19T13:13:10Z")

</div>

> [@mcostan](#):
>
> Out of interest, will nextcloud 11 be packaged in the same way for Rhel / Fedora? I.e. would the dependencies resolve themselves with the software collections?

@James_Hogarth might know more about this, he’s the one doing the packaging.

---

<div class="post-metadata">

**Author:** ![gonzalo](https://help.nextcloud.com/letter_avatar/gonzalo/32/5_5575768a8748004e209b776fc1b2916d.png) [@gonzalo](https://help.nextcloud.com/u/gonzalo)\
**Post date:** [March 19, 2017, 3:41pm UTC](https://help.nextcloud.com/t/linux-packages-status/10216/18 "2017-03-19T15:41:47Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![James\_Hogarth](https://help.nextcloud.com/letter_avatar/james_hogarth/32/5_5575768a8748004e209b776fc1b2916d.png) [@James\_Hogarth](https://help.nextcloud.com/u/James_Hogarth)\
**Post date:** [March 20, 2017, 11:42am UTC](https://help.nextcloud.com/t/linux-packages-status/10216/19 "2017-03-20T11:42:59Z")

</div>

@mcostan

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.

You can keep track of the NC 11 status with this bug: [https://bugzilla.redhat.com/show\_bug.cgi?id=1433919](https://bugzilla.redhat.com/show_bug.cgi?id=1433919)

---

<div class="post-metadata">

**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/5_5575768a8748004e209b776fc1b2916d.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\
**Post date:** [March 26, 2017, 9:26am UTC](https://help.nextcloud.com/t/linux-packages-status/10216/20 "2017-03-26T09:26:20Z")

</div>

A post was split to a new topic: [Migrate RH 7 client to Nextcloud](https://help.nextcloud.com/t/migrate-rh-7-client-to-nextcloud/10681)

---

<div class="post-metadata">

**Author:** ![giacomo](https://help.nextcloud.com/user_avatar/help.nextcloud.com/giacomo/32/660_2.png) [@giacomo](https://help.nextcloud.com/u/giacomo)\
**Post date:** [March 23, 2017, 1:00pm UTC](https://help.nextcloud.com/t/linux-packages-status/10216/21 "2017-03-23T13:00:54Z")

</div>

> [@jospoortvliet](#):
>
> Something not included?

Actually I’m the maintainer for this repository:

> **[GitHub - nextcloud/server-packages: 📦 Server packages for Nextcloud](https://github.com/nextcloud/server-packages)**
>
> 📦 Server packages for Nextcloud. Contribute to nextcloud/server-packages development by creating an account on GitHub.

It’s very simple package for CentOS 7 which we are currently using on our project (NethServer).

> [@mcostan](#):
>
> Will version 11 of nextcloud also be packaged for Epel 7?

I managed to make it work with php-fpm-56 from SCL.

> [@James\_Hogarth](#):
>
> To confirm NextCloud 11 will be packaged for EPEL7 as the bump in PHP minimum version isn’t until NC12.

Any developer can confirm it? The official doc says that PHP 5.6 is required for NC 11 ([https://docs.nextcloud.com/server/11/admin\_manual/installation/system\_requirements.html#supported-platforms](https://docs.nextcloud.com/server/11/admin_manual/installation/system_requirements.html#supported-platforms))

---

<div class="post-metadata">

**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/5_5575768a8748004e209b776fc1b2916d.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\
**Post date:** [March 26, 2017, 9:27am UTC](https://help.nextcloud.com/t/linux-packages-status/10216/22 "2017-03-26T09:27:34Z")

</div>

A post was merged into an existing topic: [Migrate ownCloud on RH 7 to Nextcloud](https://help.nextcloud.com/t/migrate-rh-7-client-to-nextcloud/10681)

---

<div class="post-metadata">

**Author:** ![jospoortvliet](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jospoortvliet/32/3_2.png) [@jospoortvliet](https://help.nextcloud.com/u/jospoortvliet)\
**Post date:** [April 19, 2017, 4:08pm UTC](https://help.nextcloud.com/t/linux-packages-status/10216/23 "2017-04-19T16:08:15Z")

</div>

@ivaradi I just added a link to your (I think) OBS repo. A user is asking about the Dolphin integration - [Client for Dolphin file manager (KDE)?](https://help.nextcloud.com/t/client-for-dolphin-file-manager-kde/11327/3)

[Next page](https://help.nextcloud.com/t/linux-packages-status/10216.md?page=2)
