FYI, nextcloud is now in the official Gentoo repository: nextcloud 
3 Likes
Have you checked under âAppsâ that it isnât just disbled? If it is, just click the âEnableâ button next to Gallery in the apps section.
I search in mijn app list and i canât found app Gallery. Not in installed, enabled and rest of other tabs.
What about in âNot enabledâ?
As noted at Test our new work-in-progress upgrader script we do also now have a new work-in-progress upgrader that also could be used for the purpose of migrating to Nextcloud.
Testing very much welcome. 
Thant wonât be of much use I fear. If Debian packages nextcloud weâll have packages which are years out of date in the stable distribution (probably with security patches). I guess this is fine for some use cases, but absolutely no replacement for the up-to-date packages provided by owncloud.
Can you elaborate what the problem is with the current packaging method used by owncloud?
Aside from it being the full-time job of one person and breaking things for users about every release, it results in being yelled at by distribution people who donât like that the packages do not follow all the various and conflicting policies for each distribution, which results in them claiming the packages are low quality. Which might or might not be true depending on your pov but in any case it isnât work which results in many grateful emails about how nice it is that there are packages.
Now customers might need packages for RHEL or something and we will have to provide those but on the community side I and the others strongly prefer to rely on volunteers. This isnât company policy or anything, note, it is just how most of the employees think about it and as weâre a company that works bottom up rather than having management meetings, this is pretty much the current state of affairs 
If you or others have a good reason to not hire somebody for coding or sales but, instead, for packaging - Iâm all ears and I am sure so are the others. But it will have to be somebody with a very thick skin, willingness to package for a wide variety of distributions AND be darn good at it so it doesnât break or change every 2nd release.
[quote=âjospoortvliet, post:49, topic:551, full:trueâ]
Aside from it being the full-time job of one person and breaking things for users about every release[/quote]
Câmon, things broke for users about every release for a wild variety of reasons. Upgrading owncloud has been a rough experience at the best of days. Just to give one example: remember someone changing the URL pattern for caldav/carddav between two versions of OC? It broke functionality for clients using the legacy pattern. And thatâs just one example. No need to single out the Debian packages here. I canât remember a single issue caused by the packages, but thatâs not to say they werenât there.
I didnât mean to single those out, and it wasnât the Debian packages but all of them. And with âbreakageâ I mean that in every other release I heard the days before or (more often) after the release I had to inform people our packages had moved to a new repo, had been renamed, dropped support for one or another platform and so on and on. Thereâs plenty more broken, for sure, but packages didnât work well. Iâd rather follow the example of Wordpress and provide a great built in updater. See also [wp-hackers] Long term suckage
[quote=âjospoortvliet, post:51, topic:551, full:trueâ]I didnât mean to single those out, and it wasnât the Debian packages but all of them.[/quote]We could well stop developing new features if the risk of breaking something is unacceptable. But I never heard that argument before.[quote=âjospoortvliet, post:51, topic:551, full:trueâ]And with âbreakageâ I mean that in every other release I heard the days before or (more often) after the release I had to inform people our packages had moved to a new repo, had been renamed, dropped support for one or another platform and so on and on.[/quote]The decision to play around with the repos was misinformed in my opinion. Sure does it make upgrading more difficult. You canât blame the repo-mechanism for that; it was an entirely arbitrary decision. Not different from changing the URL patterns I made reference to.[quote=âjospoortvliet, post:51, topic:551, full:trueâ]Thereâs plenty more broken, for sure, but packages didnât work well.[/quote]For me it did work insofar nothing else kept owncloud from upgrading.[quote=âjospoortvliet, post:51, topic:551, full:trueâ]Iâd rather follow the example of Wordpress and provide a great built in updater.[/quote]The packages at the repo did more than just update owncloud. The whole dependency tree was managed by it.
2 Likes
I know. I used them, too⌠Iâm not against packages. Iâm against having us provide them, unilaterally, rather than the distributions.
What about the packages owncloud-deps-php5 owncloud-files, can they be removed as well?
owncloud-deps-php5 is nothing more than a meta package for PHP5 dependencies. It doesnât install any file, but will âcatchâ all required PHP5 dependencies required by owncloud (and nextcloud).
So, when you remove it, apt will say : [quote=âcoolnodje, post:11, topic:551â]
The following packages were automatically installed and are no longer required:
[/quote] [quote=âcoolnodje, post:11, topic:551â]
Use âapt-get autoremoveâ to remove them
[/quote]
Donât use autoremove (see my previous post #12) and read #16 for how to mark these PHP5 dependencies as âmanualâ.
Right, I am not trying to remove then, and started to mark needed package with apt-mark manual.
But at this stage, when you moved from packaged Owncloud to manually installed Nextcloud thereâs a new issue:
when you apt update && apt upgrade your system, Owncloud is providing a 9.0.3 version and this is a mess, even if youâve uninstalled owncloud
So from your answer I gather I can safely apt remove owncloud-deps-php5 owncloud-files as long as I donât run an autoremove for the time being, is that right?
Yes, if you have previously marked needed packages as âmanualâ with apt-mark, you can safely remove owncloud-deps-php5 and owncloud-files.
You can also delete your (old) owncloud repos in your sources of packages.
Upgrade worked great from owncloud 9.0.2 to nextcloud 9.0.50 on Ubuntu 14.04.
@LukasReschke do we want to make a note about preserving themes/ directory if modified?
Iâm also waiting for Ubuntu packages, or a really good updater that takes care of >everything< for me. Preferably via CLI.
Btw, what happens to the Database tables, they are all in ownCloud format. It doesnât feel safe to upgrade just yet. Clean install sure, but I had my ownCloud for 4 years now.
Not to talk about all the guidance for users that have to download new clients and reconfigure stuff to get pure Nextcloud. Naah, not yet.
Just sayin 
1 Like
What do you mean with âowncloudâ-format? That database design hasnât changed so much (yet).
Thatâs a good question. Would be great to have at least a client-installer that uninstalls owncloud and takes over the settings (perhaps allows url-update because many used example.org/owncloud).
Exactly, not yet But when it changes, what happens to all the old tables. For me to be convinced the database must also migrate to new tables (or at least tablenames).
The table-name is not shown to the end-user, so it wouldnât be a priority for me (my setup uses an empty table prefix, so no problems for me 
). If needed, you can just rename all tables from oc_* to nc_*.