Description of problem: Similar to bug 1321417 except that in 9.1.3, the splash page for owncloud recognises when your database is large and requires you to use the CLI upgrade. This is ultimately a good thing. However, they point one to the OC documentation on how to do CLI upgrades at https://doc.owncloud.org/server/9.1/admin_manual/configuration_server/occ_command.html#command-line-upgrade which is once again not accurate for EPEL installed OC since it describes using an "occ" command with no path component. Version-Release number of selected component (if applicable): owncloud-9.1.3-1.el7.noarch Actual results: One has to figure out how to apply the generic OC documentation to the EPEL installation where the occ command is not in the $PATH. Expected results: One should not have to reverse engineer the packaging differences to figure out what the actual command to upgrade is. It should be on the splash page.
I searched for the relevant text whilst preparing 9.1.4 just now so I could include this but am having difficulty locating it. Would you happen to have the actual message as that would make finding the right place to patch much easier?
I'm afraid I don't now that I have upgraded to the latest. I can of course update this ticket with the exact text the next time I need to upgrade.
Appreciate it 9.1.4 is built and pending being pushed to testing now.
Upgraded to 9.1.4-1.el7. The splash-page dialog now says: Update needed Please use the command line updater because you have a big instance. For help, see the documentation. where "documentation" is a link to https://doc.owncloud.org/server/9.1/go.php?to=admin-cli-upgrade.
It begs the question though, why not run the occ upgrade in the rpm %postinstall with success/failure and output mailed to root?
Cheers, I'll look to patch that in my next build. And the reason I don't do that is because it's not a safe operation. The disabling of apps etc needs to have active admin interaction. Also if it fails then it's not great to have the the %post script complain. Finally if it runs a long time (due to a large install) it'll hold up the yum transaction until it completes. For all those reasons I don't deem it safe to do so automatically and just let it notify the admin it needs to be done.
owncloud-9.1.4-3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-de7e0fcf36
owncloud-9.1.4-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-0249b24b63
owncloud-9.1.4-3.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-6aba9d37e1
owncloud-9.1.4-3.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-0249b24b63
owncloud-9.1.4-3.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-de7e0fcf36
owncloud-9.1.4-3.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-6aba9d37e1
owncloud-9.1.4-4.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-c2325c9cc8
owncloud-9.1.4-4.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-c3d50f7e9d
owncloud-9.1.4-4.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-c2325c9cc8
owncloud-9.1.4-4.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-c3d50f7e9d
owncloud-9.1.4-4.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
owncloud-9.1.4-4.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
owncloud-9.1.4-3.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
The command-line is still wrong. In owncloud-9.1.4-5.el7.noarch the command line the splash screen says to use to upgrade is: sudo -u apache php /usr/share/nextcloud/occ upgrade where of course the correct command is s/next/own/