Bug 1321417

This is by design so that it cannot run except explicitly, and it should be run as the apache user.

sudo -u apache php /usr/share/owncloud occ

Just to be clear noticed a slight typo there with the missing /

It should be:

sudo -u apache php /usr/share/owncloud/occ

But why?  If you run it as some user other than apache, it bails out and tells you.

But if you did want to have this restriction/convenience, then why not include a /usr/bin/occ something along the lines of:

------------------------
#!/bin/sh

exec sudo -u apache php /usr/share/owncloud/occ "$@"
------------------------

So as to maintain the usefulness of the recommended "occ" command.

The upstream documentation does not run it directly but being passed to php.

https://doc.owncloud.org/server/8.2/admin_manual/configuration_server/occ_command.html

A script like that would make us differ from upstream documentation and introduce new edge cases (eg only runnable by root without additional configuration) that would be Fedora/EPEL specific.

If occ is used by you sufficiently often that a single occ would be useful to you I suggest you add your script to your systems but it's not an addition I'm willing to carry in the Fedora/EPEL packages for the above reasoning.

When an upgrade needs doing, the OC main page says:

    To avoid timeouts with larger installations, you
    can instead run the following command from your
                 installation directory:
                    ./occ upgrade

That of course does not work on Fedora/EPEL.  Perhaps that at least ought to be updated in Fedora/EPEL packaging to display the correct command rather than leaving it up to admins to figure out what is different?

Now that I can do and will add to the upcoming packages.

That's a fair enough compromise.

Speaking of upcoming... is OC 9 in the near future, for EPEL7 in particular?  :-)

It depends exactly how you define near ...

Have a read through the (long) 9.0.0 is available bug for Fedora:

https://bugzilla.redhat.com/show_bug.cgi?id=1261011

The short version is it is coming - but it will take a while since we need to upgrade from 8.0 to 8.1 first, then from 8.1 to 8.2 and finally up to 9.0 since upstream doesn't support skipping 'major' versions.

I'm doing this in fedora first to flush out issues before looking to the more enteprisey EPEL7 packages (and EPEL6 will be retired soon due to dependency issues).

If you're willing to do some early testing Didier in that thread has a COPR up with the changes I'm making in Fedora mirrored there.

I imagine in the next few months we'll be caught up again and it'll be easier staying up to date then but it depends on $life and how things go in Fedora.

php-sabre-event-2.0.2-1.el7 php-sabre-vobject-3.5.0-1.el7 php-sabre-http-3.0.5-1.el7 php-sabre-dav-2.1.10-1.el7 owncloud-8.1.6-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-3945697efc

owncloud-8.1.6-1.el7, php-sabre-dav-2.1.10-1.el7, php-sabre-event-2.0.2-1.el7, php-sabre-http-3.0.5-1.el7, php-sabre-vobject-3.5.0-1.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-2016-3945697efc

owncloud-8.1.6-1.el7, php-sabre-dav-2.1.10-1.el7, php-sabre-event-2.0.2-1.el7, php-sabre-http-3.0.5-1.el7, php-sabre-vobject-3.5.0-1.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 version now out has the patch to display the correct command in the web upgrade screen.

As a reminder per my mail to the EPEL and CentOS lists 8.2.3 will be pushed into testing shortly, please make sure you've updated to 8.1.6 before 8.2.3 is pushed live in a few weeks.