Linux packages status

After posting I saw in the top right corner of the link I posted they updated about the exact time I had things going on wierd.

Can I purchase support from you? We have it installed but it crashes frequently.

You can see your options at nextcloud.com/enterprise for that.

How do I install the nextcloud client on Debian 12 (Bookworm) ? Most of the documentation here is for Jesse or older, the current release of Debian is named Bullseye and the testing version is currently Bookworm. Is the downloadable client able to run on the newest build??

You can just apt install nextcloud-desktop

BTW, I maintain a COPR for RHEL 8 (and CentOS 8, Alma, Rocky, etc.) here:

Itā€™s based on using the Remi repos for PHP.

Itā€™s what I use for myself- I only push a new RPM to COPR once I have updated my server successfully.

I basically rebuild the Fedora packages with as few modifications as I can, and I try to follow upstream as much as I can (in the COPR page you can see when I upload). Actually, for 24.0.6 Iā€™m lagging a bit, because the Fedora package has seen some improvements and I want to adapt them, but test them carefully.

(I noticed I hadnā€™t posted here just now- I came here to see if anyone had posted about RHEL 9ā€¦ At some point Iā€™ll want to move to RHEL 9- I think that will be easier to maintainā€¦)

edit: if you donā€™t trust the packages, thereā€™s a script to build them using Podman that requires 0 setup (except having rootless podman working). I have adapted the other COPR I have to run the build in COPR itself (so you can inspect the build and I cannot ā€œcheatā€), but I have not done this yet.

Hey there!
I have a question regarding which installation method is recommended. In the past the official instructions installed the client via a PPA on Ubuntu which was changed to AppImage ā€“ I think recently.

My impression would be that AppImage has the following disadvantages over the more native PPA version:

  • Limited integration with nautilus
  • No auto-update (or am I missing that this is part of AppImage?)
  • Autostart needs to be setup manually (again I might be missing that this actually exists)

Hence my question:

  • Why favor AppImage over the previous PPA installation?
    • Does that make development easier / more unified?
    • Is the PPA actually 3rd party (in this case Nextcloud development in Launchpad should really be changed as the name ā€œnextcloud-devsā€ suggests that this is official)?
    • Is the PPA installation actually preferred on Ubuntu?
    • Are my concerns misguided or am I missing something else?

Because itā€™s the only package that is currently maintained by Nextcloud. Most of the other, distro-specific packages and repositories were always built and maintained by third parties. They were just mentioned more prominently on the old website, a few of them even with direct links to the respective repos, while the new website only links to this forum post.

Probably not as much the development itself, but building packages and maintaining repos for every possible distribution would be a huge amount of work.

This is entirely up to you.

The advantage of the PPA over the packages in the Ubuntu repositories is, that you always get the latest version, at least if you are on the latest LTS release of Ubuntu, while the package in the Ubuntu repos never changes during the life time of a specific Ubuntu release.

The advantage of the AppImage is that it is completely independent from the underlying distro, and therefore also from the distroā€™s release-cycles. You can always use the latest version even if you are still on Ubuntu 18.04. But it also has a few disadvantages, which you have already mentioned, like e.g. limited integration with Nautilusā€¦

1 Like

About the appimage ā€œlimited integration with Nautilus,ā€ is that the reason the appimage silently quits shortly after starting and never restarts? And if youā€™re familiar with this issue, is there any way to fix this? When the appimage stops running and syncing changes, It completely obviates the whole reason I use Nextcloud, which is to provide cloud access to files. When it isnā€™t running, I cannot remotely access my most recent files and changes.

By ā€œNautilus integrationā€, I mean the context menu for file sharing and the sync status icons in the file manager. Using the Synchronization Client ā€” Nextcloud Client Manual 3.11.0 documentation AFAIK, these are not included in the AppImage.

I donā€™t think so. The actual file synchronization should still work, even without the ā€œNautilus integrationā€.

Unfortunately, Iā€™m not, since I never used it myself. Also, I donā€™t have much experience with AppImages in general.

1 Like

Thank you for the reply! I posted about the issue Iā€™m having, but so far I have not received any response. I noticed other posts about appimage issues have also been left languishing. Iā€™m worried that Iā€™m just stuck with something that prevents me from using Nextcloud as intended, which makes me wonder why Iā€™m paying for hosted space that is just sitting there without being used (since the defective appimage renders Nextcloud useless to me).

Donā€™t use the appimage , use the nextcloud from your distro package manager

2 Likes

:arrow_up: This! :arrow_up:

Respectively, there is a PPA for Ubuntu:

https://help.nextcloud.com/t/updated-more-detail-linux-appimage-quits-after-sync-and-must-be-restarted-manually-to-sync-any-changes-how-to-fix/153711/2

2 Likes

Thanks , but setting a PPA needs command line or complex copy paste , not acceptable for professional. We need a click and install way

Youā€™re kidding, right? :wink:

Btw, you can add PPAs via GUI: How to Add or Remove PPA in Ubuntu Using GUI and Terminal

I wouldnā€™t say this process is easier, though :wink:

Tell a client he needs to do that to use your nextcloud hosting and you will see his reaction.

Then you do it for the customer, or you could write a guide.

Sure, you could also use the package from the Ubuntu repos, which I would not recommend, especially if you are using Ubuntu LTS. The package nextcloud-desktop is in the Universe repos and these packages never get any updates. Neither security nor bug fixes and certainly no feature updates.

This solved the problem! Thank you so much!

2 Likes

In case anyone wanders here and Iā€™m luckyā€¦

Iā€™m looking to migrate my NextCloud from EL8 to EL9. I just did an experiment rebuilding the NextCloud Fedora RPM directly on COPRā€¦ and it worked OOB! However, NextCloud requires newer versions of PHP than what EL8 and EL9 haveā€¦ but! It works with the Remi newer PHP packages (php:remi-8.2 works on EL9, and Iā€™ve been doing a similar build with php:remi-8.0 on EL8 that also works).

Hereā€™s the COPR:

https://copr.fedorainfracloud.org/coprs/koalillo/nextcloud-test/

Iā€™ve posted in the Remi forum to see if thereā€™s any possibility to add them to the Remi repos themselves (I think itā€™s impossible to get them into EPEL, due to depending on Remi):

ā€¦

Is anyone interested in working on this? I think itā€™s pretty interesting because the Fedora packages seem to be well-maintained, with frequent updatesā€¦ And itā€™s quite nice to run NextCloud on EL as a package.

Cheers,

Ɓlex

Why not just setup a LAMP or LEMP Stack and using the zip or tarball from here?

Or if it needs to be pre-packaged you could use Docker, Nextcloud AIO or the Snap Package.

Distro-specific packages of the Nextcloud server, whether created by third parties or by official maintainers of the distro, in my experience always cause some kind of problems sooner or later, and then you have exactly the hassle you have now :wink: