Bug 1471469
Summary: | Cannot migrate from owncloud 9.1.5 to nextcloud 10.0.4 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Marek Greško <marek.gresko> |
Component: | nextcloud | Assignee: | James Hogarth <james.hogarth> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 28 | CC: | bugzilla, clemens.nafe, fabrice, james.hogarth, olivier.lahaye1, redhat-bugzilla, russ+bugzilla-redhat, samuel-rhbugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-28 23:42:35 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Marek Greško
2017-07-16 07:15:05 UTC
hello guys! I've got the same issue. If nextcloud 10.0.5 is the solution, is there a plan for release this version? Even updates-testing doesn't provide an update to it. Nextcloud 10.0.5 definitely is a solution. I prepared rpm packages myself, updated and it works. But remember, the version 10.x of nextcloud is rather outdated now. It is better to upgrade to currently supported version. Hi Marek, the issue is, that FC 26 doesn't ship NC 11. The current versions of OC and NC are: Name : nextcloud Version : 10.0.4 Release : 2.fc26 Name : owncloud Version : 9.1.5 Release : 1.fc26 If one (and I did) uses the migration description shipped with Fedora (/usr/share/doc/nextcloud/MIGRATION.fedora) then it is not possible to migrate due to the version mismatch. NC should be updated to 10.0.5 anyway. CVE-2017-0893 would be fixed then (despite the low risk level). Yes, fedora does not ship nextcloud 11. But nextcloud 10 is not supported any more. Only 11 and 12. It should not be a problem. Owncloud was upgraded from 8 to 9 as a regular update during fedora 24. Compare fedora 24 release and updates repositories. Definitely, at least 10.0.5 version is required to migrate. I can confirm that migration works with installed nextcloud version 10.0.5. Note that either bug 1444007 or 1433919 could fix this, depending on the exact versions eventually built. (In reply to bugzilla from comment #5) > I can confirm that migration works with installed nextcloud version 10.0.5. James, can't we upgrade Nextcloud to 10.0.5 so that Owncloud users can migrate to Nextcloud, and then finally move to Nextcloud >= 11? This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Same problem for me on CentOS-7 using EPEL-7 packages as of date 14 June 2019 rebuilding rpm with v 10.0.5 fixes the problem on CentOS-7 as well. |