___Description of problem: Mageia 6 now have Nextcloud 11 (and no ownCloud) so in order to make mga5 -> mga6 follow recommended upgrade/migration paths reliable we need in mga5 have all major versions of ownCloud and Nextcloud needed before Nextcloud 11 available in Mageia 5! For earlier work on this see Bug 17279, Bug 19634, Bug 19662 Now time have pased so we need more versions... ___Specifications: A) ownCloud/Nextcloud upgrades may not skip x.y versions B) according to official https://nextcloud.com/migration/ migration to Nextcloud is only supported for same lever version, i.e Owncloud 9.0 -> Nextcloud 9 or Owncloud 9.1 -> Nextcloud 10 C) upstream also recommends to always upgrade from latest x.y.z to next x.y.latest D) Upgrades are disruptive and need user interactions, sometimes user must have read documentation too, upgrades may not start by normal system updates. ___Suggested actions: We curently have 9.0.5 in mga5 backports, so: C) above -> we need ownCloud 9.0.latest (9.0.9 currently) A), B) -> we need also ownCloud 9.1.latest and Nextcloud 10.latest So in all 3 versions! D) above -> put updates in core_backports, like before Also see https://wiki.mageia.org/en/OwnCloud#To_do_in_this_document and https://wiki.mageia.org/en/OwnCloud#Server_upgrading which are to be updated as this bug progress. I currently have ownCloud 9.0.5 on an mga5 on which i can test the above on.
Above is by following official recommendations. There exist varying information on Nextcloud capabilities for upgrading while migrating so one or even two versions can be skipped, but results vary. So i think it is best to provide our users with all versions needed to follow official advice, and leave to them if they want to experiment with shortcuts. When asking on forum i did not get a reply for over a week: https://help.nextcloud.com/t/migrating-from-owncloud-to-nextcloud/551/116
CC:ing earlier packagers
CC: (none) => lists.jjorge, luigiwalser, mageia
I will push all this to MGA5 backports.
Status: NEW => ASSIGNEDAssignee: bugsquad => lists.jjorge
Many thanks José. Ping this bug when something is ready to test :)
9.0.9 is submitted to 5/backports_testing, please report your tests in 20961. I will submit 9.1.x when 9.0.9 will be validated.
nextcloud-client is considered obsolete by nextcloud themselves. Also, I am having a hard time getting nextcloud-client to accept my internal CA by installing the CA in /etc/pki/tls/rootcerts/
CC: (none) => zombie_ryushu
Thanks for the heads up on client version! -> Bug 21015 (i guess you dont mean they deprecate their client per se and prefer other?) Regarding rootcerts i suggest ask forum, or maybe José here have a clue? When you get it to work (or any other addition correction) please add that valuable info to our wiki :)
under owncloud, (not nextCloud) putting your CA PEM in /etc/pki/tls/rootcerts/ and pidgin, and ownCloud would respect that. (FireFox won't.) Mageia doesn't have the update-ca-trust command.
I dont know much about rootcerts, but sure we must have some package that updates it somewhere, and we could symlink that? (i did struggle regarding BOINC: Bug 14751 - Boinc do not use correct certificates.) Who @mageia can shed a light here?
RPM based distros do it one way, DEB Based Distros do it another. Sometimes cat "ca-bundle.crt newcert.pem" > ca-bundle.new works. (assuming your application looks for the CA bundle.)
Different distros do it different ways, different libraries (openssl, gnutls, nss) do it different ways, and different applications do it different ways. It's a complicated mess. Some applications will, or can be configured to, use /etc/pki/tls/certs as a directory containing certificates so you can just drop it in there. Sometimes you can configure an application by giving it the exact path to your CA cert. Often this is fine, as you're only using a non-standard CA cert for one or two things. NSS is the most difficult one, and that's what Firefox (and possibly Chrome) uses. It technically does have an ability to use a system-wide cert DB in /etc/pki/nssdb, but you have to run with environment variables that tell it to use the newer version of the DB format, as this doesn't work with the older default version. It's just like the cert8.db in your Firefox profile, but it's cert9.db of course. It's also possible to put a cert8.db in the system Firefox directory, which will automatically get merged into newly created Firefox profiles. That was the solution I chose at my last job. You can also rebuild rootcerts with your additional cert and then rebuild nss against that, but you have to re-do it every time we update rootcerts. Fedora has a more integrated way of doing it, but it required them to hack nss to bits and split it into multiple SRPMS and patch it, and it makes it very hard to maintain, so that's why we haven't adopted their solution. What we really need is upstream NSS to implement a way to make this easier, and for there to be more standardization across distros, libraries, and applications as to how this is handled.
(In reply to Zombie Ryushu from comment #6) > Also, I am having a hard time getting nextcloud-client to accept my internal > CA by installing the CA in /etc/pki/tls/rootcerts/ I am using Let's Encrypt in two setups, this make both browser and client happy. Basically, I use the acme.sh client, and added this 3 lines to Apache 2.4 conf file of owncloud : SSLCertificateFile /etc/ssl/certs/site/site.cer SSLCertificateChainFile /etc/ssl/certs/site/fullchain.cer SSLCertificateKeyFile /etc/ssl/private/site.key I get an A- in Qualys test, after also disabling RC4 and 3DES. But we are far from this bug report...
Bug 20961 done; Owncloud 9.0.9 is backported
Rising the importance as we need be done before mga6 release and it is close :)
Priority: Normal => High
Owncloud 9.1.6 is in backports testing, bug MGA#21064.
Owncloud 9.0.10 is out.
(In reply to Zombie Ryushu from comment #16) > Owncloud 9.0.10 is out. Yes, but we don't need it to upgrade to 9.1.6, and then nextcloud 10.x
Nextcloud 10.0.5 is in backports testing, bug 21065 . So we will be able to test both steps and then test upgrade to MGA6.
Thanks José :) I will try upgrading tomorrow. @Zombie This series of upgrades aims to provide most importantly a full upgrade path to Nextcloud 11 in Mageia 6. A side accomplishment is that Mageia 5 users will get to ownCloud 9.1.6 and can then chose to migrate to Nextcloud 10 ( All steps must be done before upgrading to Mageia 6, per comment 0 )
Correct bug no for Nextcloud 10.0.5 is bug 21066 ;)
Status: waiting for removal of 9.1.6 from backports testing bug 21064, as it is not migrateable to Nextcloud 10.0.5 bug 21066. Then José can push ownCloud 9.1.5 All need will be tested before mga6 release...
Target Milestone: --- => Mageia 6Depends on: (none) => 20961, 21064, 21066
No, we better * keep ownCloud 9.1.6 * It is OK with a trick: https://help.nextcloud.com/t/migration-from-owncloud-9-1-6-to-nextcloud-10-0-5-fails/13523/14
Status: We a while ago decided to have ownCloud 9.1.5 Migration to NC10.0.5 then tested OK using MariaDB and separate data location. Both are in updates testing. Strange quirk: NC10 offer upgrade to NC11 if it was migrated from ownCloud 9.1, but not on fresh install. https://bugs.mageia.org/show_bug.cgi?id=21066#c30 PROBLEM: When i installed OC with default database SQLite and data location, migration fails: https://bugs.mageia.org/show_bug.cgi?id=21066#c32 I guess it is because of the folder name change .../owncloud/ -> .../nextcloud/ Personally i do not have time in near future to test or look more into this :(
Status: OC 9.1.5-2 and NC 10.0.5-5 in backports. - thank you guys :) I will update wiki soon and then close this bug.
https://wiki.mageia.org/en/OwnCloud done. Closing :)
Resolution: (none) => FIXEDStatus: ASSIGNED => RESOLVED