The warning at upgrade screen about file_locking is normal, and should be ignored according to the documentation :

https://doc.owncloud.org/server/8.2/admin_manual/configuration_files/files_locking_transactional.html

Transactional file locking is in core, and replaces the old File Locking app. The File Locking app has been removed from ownCloud in version 8.2.

Status: NEW => ASSIGNED

Sysadmins, please remove owncloud-8.1.10-3.mga5 from backports testing as my Ctrl+C was not in time.

Strange, I can not find it.
(and my mirror is up to date)

CC: (none) => fri

...I mean i can not find owncloud-8.2*

Regarding removal from backports testing, also remove
.../distrib/5/x86_64/media/core/backports_testing/owncloud-8.1.10-2.mga5.noarch.rpm    

(it seem removed from i586 but not x86_64, at least on my mirror)

NOTE regarding errata: see
https://wiki.mageia.org/en/OwnCloud#Upgrading
and
https://bugs.mageia.org/show_bug.cgi?id=17279

I still cant see 8.2.8 in mga5 backports testing.


Anyway, you said you will after this is confirmed OK, push 9.0.latest to mga5 backports (testing), great.

I think we then should then replace cauldron OwnCloud 9.0.x with 9.1.latest in cauldron release - what do you think?

(In reply to Morgan Leijström from comment #6)
> I still cant see 8.2.8 in mga5 backports testing.

I have pushed  a release 2 as it seems previous one made a bug in the mirrors.

> Anyway, you said you will after this is confirmed OK, push 9.0.latest to
> mga5 backports (testing), great.
> 
> I think we then should then replace cauldron OwnCloud 9.0.x with 9.1.latest
> in cauldron release - what do you think?

After talking with neoclust, we are going the nextcloud way : MGA6 will bring Oc9.0 and Nc10.x. The version 8.2 in backports is enough to upgrade to MGA6 Oc9, and then nextcloud10.

We can't afford providing security updates for both, and Nextcloud seems much better at providing updates, so we can hope not have the same hell for MGA7.

OK I understand no unecessary work is wanted.
I have updated the wiki with correct versions according to your decisions :)
This afternoon i will try 8.2.8 (i see it landed now) and report back.

Test OK mga5-64 upgrade 8.1.10-3 -> 8.2.8-2  :)

Do we have any notes on upgrading Oc9.0 to Nc10.x?
It just works like any other ownCloud update?

Whiteboard: (none) => MGA5-64-OK

Test OK also on mga5-32 upgrade 8.1.10-3 -> 8.2.8-2 .

I have never tested oc to nc upgrade, but it should be like this ones.

Whiteboard: MGA5-64-OK => MGA5-64-OK MGA5-32-OK

Withold validation temporarily?
------------------------------
I notice that both OKs above are the upgrade from owncloud-8.1.10-3 (only just released), to owncloud-8.2.8-1.mga5. That previous - and very recent - upgrade was from version 8.0.9 :
 https://bugs.mageia.org/show_bug.cgi?id=17279

From the previous bug, Comment 0:
Major releases are 8.0, 8.1, 8.2, and 9.0 ... Skipping major releases is not supported
So we need to ship update to 8.1.x first.
Then the delay between releasing that and next should be long enough that "everybody" get the 8.1.x update AND perform the web initiated upgrade before we push 8.2.x

Comment 19:
"the plan is to push 8.2.8 in backports when 8.1.10 will be validated and pushed to core/backports"

Which taken together I take to mean that the 8.1.10 update must be (has been) pushed *and implemented* by users *before* this update to 8.2.8 is pushed. A month interval?

So it looks as if validating this backport should be postponed for some time, for the previous one to be implemented in the field everywhere first. If this is correct - held for how long?

Keywords: (none) => validated_backport
CC: (none) => lewyssmith

Good of you to check.
Yes the original thinking was that the major updates should go in normal updates, and then delay would be needed.

- But that is since abandoned because major updates are more likely to cause breakage.  

-> It is decided 8.1.10 and 8.2.8 are to be in backports only, so user installs them only after some thought, and is prepared.

ref: further down in bug 17279, and <dev> ML

The procedure is clearly stated at https://wiki.mageia.org/en/OwnCloud#Upgrading, which is to be referenced in mga6 errata.

I have also tested to try skip a major revision: what then happened was that ownCloud refused to update the database, and i could just install the old rpm again and it continued to work. https://bugs.mageia.org/show_bug.cgi?id=17279#c0 (no guarantees, but owncloud tries protect from such cases)

So i think we should have both 8.1.10 and 8.2.8 in mga5 backport ASAP, to enable mga5 users to upgrade to newer ownCloud, and those few that have ownCloud and want to upgrade to mga6 now can try that ASAP.
- Next versions - ownCloud c9.0 and Nextcloud 10.x - are already in mga6.

Practically, it is also more convenient to do one backup, then perform several upgrades directly after each other, then full check - than to pause between upgrades and need to perform intermediate backups and more intermediate testing.

That said we have not tested fresh installs - only upgrades... it feels a bit sloppy not to test fresh but there are other things to put energy into...

*idea* could a link to https://wiki.mageia.org/en/OwnCloud be included in descriptions in our owncloud rpms?  (that is analoguous to that urpmi-proxy have a link to our wikipage about it) OK maybe a bit late to start now...

moved.

Status: ASSIGNED => RESOLVED
CC: (none) => mageia
Resolution: (none) => FIXED