Instruction: https://github.com/nextcloud/server/issues/5426 (first issued as https://github.com/nextcloud/nextcloud.com/issues/496 )
Script: https://github.com/nextcloud/server/issues/5425 (first issued as https://github.com/nextcloud/nextcloud.com/issues/497 )
@Morgano thanks for filing the issues. The Nextcloud updater should ignore minor versions (the .5 vs .6) on migration between different products (oC to Nc), but apparently something is wrong. It might be that oC didn’t properly set the vendor on install or update, there was a bug with that. Once 10.0.6 is out it should of course work but this isn’t nice so we have to look if we can work around it…
A work-around from this blog is to set the version of your ownCloud server to 220.127.116.11, see:
edit your config/config.php and set version to 18.104.22.168 or lower.
From @nickvergessen - if the reason is that oC didn’t set the vendor properly, you should run this before you try to upgrade to Nextcloud:
occ config:app:set --value "owncloud" core vendor
Reading from posts earlier in this thread, and other places, I am told that OC 9.1.6 use a newer engine than OC 9.1.5 and NC 10.0.5, so that is not a safe path anyhow. Or is there news on that?
It do seem to work for some anyhow, but i am trying to define an official upgrade path for Mageia 5 (owncloud) to Mageia 6 (nextcloud) that is doable ASAP. https://bugs.mageia.org/show_bug.cgi?id=20953#c21 , https://wiki.mageia.org/en/OwnCloud#IMPORTANT_:.2ABEFORE.2A_upgrading_to_Mageia_6.21
It there any idea yet when NC 10.0.6 (or other compatible NC) is out: like in a week, or four weeks?
If soon, maybe we can get NC 10.0.6 into Mageia5 backports
I agree with the assesment from the blog on https://0xstubs.org/migrating-from-owncloud-9-1-6-to-nextcloud-10/ that there don’t seem to be any changes to the database, which would indeed be unlikely in such a late-in-the-series bugfix. This should not cause any problems.
However, I’m testing this myself now with a fresh 9.1.6 and will try to fix this out. Will get back to you all.
If the workaround is safe, it will save a lot of people some work.
In my case, I had to set version
22.214.171.124 in file
version.php. When I set
config/config.php, the updater still recognize installed owncloud version as
In the end, migration from owncloud
9.1.6 (faking it as a
126.96.36.199 version) to nextcloud
10 to nextcloud
11 went well.
I modified version.php to refer to 188.8.131.52 which worked for me but didn’t work for a user on twitter. We have to fix the migration script… The upgrade itself, if you manually replace the files that is, does work.
I see you fixed the migration information
The updater script issue https://github.com/nextcloud/server/issues/5425 got closed now with “There is a patch in the repo for this already.”
The documentation issue https://github.com/nextcloud/server/issues/5426 erroneoulsy got closed as a duplicate of above, while it should be closed fixed, as i now see at https://nextcloud.com/migration/ :
Note that ownCloud 9.1.6 breaks easy upgrading to Nextcloud 10.0.5. We will fix this in 10.0.6! Similar, ownCloud 10.0.2 and 10.0.3 can’t yet be upgraded to Nextcloud 12, which will be fixed with Nextcloud 12.0.1. We want to make sure we properly test the upgrade paths!
As always there may be further issues too… Just run into this theming bug https://github.com/nextcloud/server/issues/4987 on 11 something to 12.0.0 upgrade
Nextcloud 10.0.6 is available since August 7th. But:
- Migration script still detects 10.0.5 NC version to be the upgrade path for my 9.1.6 OC instance.
- Migration instruction still state that 10.0.6 will fix the issue
What’s the status then?
seems like the update server tells the migration script what to do:
<?xml version="1.0" encoding="UTF-8"?> <nextcloud> <version>184.108.40.206</version> <versionstring>Nextcloud 10.0.5</versionstring> <url>https://download.nextcloud.com/server/releases/nextcloud-10.0.5.zip</url> <web>https://docs.nextcloud.org/server/10/admin_manual/maintenance/manual_upgrade.html</web> <autoupdater>1</autoupdater> <signature>WuAMs8EGo8FD9ETw+TkeMAv8XjDv45/wiq/AAXBX8PuvJORdLhqyy2KwUiR/ztWZ DUpINgFm110o4J4kghZTGYGhgFr0iVJ07pwVnDXC1NGGz8UdVFPPp1vJbmAiLFGB IVnydDmx+PWI6ECcktUw5W9QRFmIc67bNoKlUXJi5XT6cLQNQnH2mAingNC5ya0T qvqPmHIzwVu1gafxHtJfc4ZPcc6dLoAQdu9WLcIqALqd/1DEASNkZD06LVJvuWIB HFjQtul/3pj4bC2zhX0QiubBfa3n2bA9Hq8nRVj0MLRezT0FS0ObhL4C16xT6/nE oMp/buXZlLjkgI1RLwWvTg==</signature> </nextcloud>
Any update? Migration is still broke.
Migration tool report
Current version is 9.1.6.
Migration to Nextcloud 10.0.5 available.
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-10.0.5.zip
Can’t continue migration … Nextcloud 10.0.6 is needed during migration … and is available for download
Nobody there to correct the migration process … ???
I’ve hit the same wall a few weeks ago and I found a workaround that worked for me: perhaps can help someone.
I downloaded the owncloud-10.0.0 tarball from owncloud and used it to upgrade my former owncloud installation. After that the nextcloud upgrade to 12.0.0 worked like a charm…
I’m in discussion about this subject on Github: