Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update from Repository broken #10685

Closed
mcnesium opened this issue Aug 28, 2014 · 9 comments
Closed

Update from Repository broken #10685

mcnesium opened this issue Aug 28, 2014 · 9 comments

Comments

@mcnesium
Copy link

I installed owncloud on ubuntu 14.04 via repository. Having unattended upgrades running I assume owncloud to upgrade automatically. Also I run a cronjob every 15 minutes on cron.php.

Still, every time an upgrade is released, the caldav server is no more reachable. Why? After the upgrade is installed, I still have to go to my owncloud instance in the browser and manually hit the Upgrade button.

Follow-up issue

@stonerl
Copy link

stonerl commented Aug 28, 2014

That's the normal behavior. It just upgrades the installed files. Your either have to go on your owncloud instance and click the update button or you connect to your server via ssh and do the following.

cd /var/www/owncloud/
sudo chmod +x occ
./occ upgrade

@mcnesium
Copy link
Author

Why is this not done by cron.php?

@stonerl
Copy link

stonerl commented Aug 28, 2014

@jnweiger the file-permission should be changed to 744 or 754 maybe 755 for the occ-file. Could you add a notification to the package to inform the user? Maybe this command could be executed at the end of the upgrade-process?

@PVince81
Copy link
Contributor

PVince81 commented Sep 1, 2014

The openSUSE package also seem to lack ./occ file permissions. Maybe the original tarball didn't have it and the package script needs to automatically set it.

@jnweiger
Copy link
Contributor

jnweiger commented Sep 2, 2014

Tar ball does not have proper permissions. Enforcing mode 755 in the specfile for all four:
6/7 ee/community.
(Also removed some horrible ntp cruft from the specfiles)

@mcnesium
Copy link
Author

Even though this issue has been closed, it persists up to todays 7.0.3 update. Mirall-, CalDAV- and other clients throw connection failiures and other error messages, until someone goes ahead and opens up the instance in the browser and hits update.

This might be bearable for advanced IT professionals running their very own infrastructure and deal with error messages every day. But for pretty much everyone else who uses the instance that behavior is just uncertainly inconvenient.

So again I am wondering, why this update is not at least done by cron.php. There obviously must be an opt-in for it, but it should be possible.

Also, servers that run unattended upgrades on software installed via repository, should be able to unstall those minor updates this way. That's one of the major points of having software repositories IMHO.

#2ct

@PVince81
Copy link
Contributor

I suppose the upgrade could be triggered by the postinstall part of distro packages.
It would need to run ./occ upgrade on the command line to trigger it automatically.

@PVince81
Copy link
Contributor

I raised #12125 to discuss this

@mcnesium
Copy link
Author

great, thx

also thank you for doing great work on owncloud in general. just saying…

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants