(and of course 8 is better than 7 - especially in performance they say) Description of problem: I noticed owncloud server 8.0.0 is out Updating from current version 7 can not be automatic, so if we have time to package and test, we should ship mga5 with version 8. If not we can not update to 8 until next mageia release (or we can have it in backports, just make sure it do not install by accident) Upgrade to OC 8 (known issues) : http://forum.owncloud.org/viewtopic.php?f=31&t=26310 http://doc.owncloud.org/server/8.0/admin_manual/maintenance/upgrade.html If someone package it, i can try remove version 7 and install 8, or if you want me to try upgrade. In a week or two. I wrote https://wiki.mageia.org/en/OwnCloud and will update it accordingly. Reproducible: Steps to Reproduce:
CC Oden E, David W, Thomas S What do you think?
CC: (none) => luigiwalser, oe, thomas
I have been thinking about this, and given our delayed release, I imagine it's probably a good idea, but it's up to the maintainers. I've included them now on the bug.
CC: (none) => mageiaAssignee: bugsquad => mageia
i am in favor of this
i will push it as an update when mga5 will be released.
It would be better to do it now so that people don't have to do the major upgrade twice, if possible.
this is not late ? if not, i will do this today
Great if it could be done today :) I will then try it tomorrow. -Without any caching... (I broke my OC7 installation a couple days ago before by trying different caches, not sure if apcu or xcache broke it or it was some other latent error... will remove it and try a clean OC8 then) OC upgrades are known to sometimes be problematic.
It's a leaf package that doesn't affect anything else, and shipping with version 8 will greatly increase our ability to support it for mga5's lifetime, so it isn't too late. It only makes sense to do this now.
Reflecting over that there is owncloud 6 in mga4, and from https://doc.owncloud.org/server/8.0/admin_manual/maintenance/upgrade.html: " It is best to keep your ownCloud server upgraded regularly, and to install all point releases and major releases without skipping any of them, as skipping releases increases the risk of errors. " If we were to follow owncloud official recommendation we should first release first revision of owncloud 7, then all 7 point releases. Then 8 and all 8 point releases. (but i have read in the forum that point revisions actually at better at upgrades from earlier main release what so that official page is not quite right...) Also, if following mageia policy of not changing main revision during a mageia version we can not change from owncloud 7 to 8 until mga6, and by then owncloud is probably at version 9 or higher... coming far to far behind. Maybe have any owncloud new main versions in backports, so now owncloud 7 in mga4 backport. So users can upgrade that way. If they know.... Before next main mageia hits with nextnext ownclod version. We simply can not release all 7.x as intermediate versions for mga4 owncloud 6 users as upgrade pathstones to owncloud 8 latest because of too much work i think. There are even much that can go wrong from latest OC7 to OC8. I think the least wrong, and least work, but breaking mageia policy, is to ship mga5 with this OC7 we have already here in cauldron, and a couple weeks after release put latest point release of OC8 in updates. (Feel free to put OC8 in updates testing asap.)
(In reply to Morgan Leijström from comment #9) > I think the least wrong, and least work, but breaking mageia policy, is to > ship mga5 with this OC7 we have already here in cauldron, and a couple weeks > after release put latest point release of OC8 in updates. You suppose people will upgrade before we release OC8 in updates, which we can't guarantee. If owncloud folk are not capable of supporting upgrades correctly, they're doing a bad job, but there's not much we can do about it, except maybe warn in Errata and/or Release Notes.
This way we at least provide a way. mga4 OC6 -> OC7 mga5 release -> OC8 mga5 updates If users happen to upgrade OC6 -> OC8 and it works, great. If not, they have a chance to uninstall OC8, restore backups (that are noted everywhere should be done), and have a chance to install OC7 from mga5 release. Owncloud is such a beast that i think users who run it are aware of issues ;)
package is ready here, i am doing QA ( pb with .htaccess for ex ).
Great :) What about having both OC7 and OC8 in release then? (for said reasons, and because we already have OC7 package) Or would that be considered bloat?
We can't have both, and I see no point in shipping 7 if we're not going to be able to support it for mga5's lifetime. Updating it to 8 during the mga5 cycle would technically be against policy (unless it was later, when 7 was no longer supportable). Basically, ideally, it's now or never, at least if we want to minimize headaches.
CC: thomas => (none)
owncloud-8.0.3-1.mga5 is in Cauldron. Please test.
Status: NEW => RESOLVEDResolution: (none) => FIXED
Thank you Nicholas :) Successively upgraded from the OC7 package to this OC 8, by just urpmi --auto-update, and then in owncloud web interface login click to execute the upgrade. No php cache of any kind (apc, apcu, opcache, xcache...) I do not have time right now to do a full clean and reinstall. (This is my production server for internal use and i am swamped.) ( Sidenote: on my problem i had with OC7: Like before the upgrade, CPU went to 100% when trying (and failed) to delete some of the files in a folder also after the upgrade, but that got solved by pausing all clients sync, removing folder from clients and server (by web interface), and then moving back that whole folder in one of the clients and reenable sync. Now all seem OK. That problem came up while i was trying apcu + xcache last week. I had no problem using opcache but others have had, so i skip all caching for now...)