OOPS yes i am tired, forgot the important "not":

I wrote   "did automatically deselect"

should be "did NOT automatically deselect"

I think that we should push this to backports : the version 8.0.x is still supported, and release notes for 8.1 and 8.2 explain that there are regressions like "Using ownCloud without a trusted_domain configuration will not work anymore." It also explains that migration is to be finished manually!

I would expect Mageia owncloud package to not break itself simply updating the system, so again please push as BACKPORT.

CC: (none) => lists.jjorge

Good catch.  There are also other issues that may emerge.   Backports then.

https://doc.owncloud.org/server/8.2/admin_manual/release_notes.html

Ping...
8.1x is needed as intermediate upgrade
8.2.2 was released december 22
I can back up my system and test built packages, upgrading to 8.1x first.

CC: (none) => luigiwalser, mageia

So I think we should push 8.1.x for now to backports, allowing voluntary upgrade for users. And add it to release notes of MGA6, that it is suggested to switch to backport version before upgrading to 8.2.x version.

If this is agreed, I can do this backport. WDYT Nicolas?

Status: NEW => ASSIGNED

I think we pretty much need to do this, since those upgrading to Mageia 6 will need to update to 8.1.x before upgrading to Mageia 6's 8.2.x.

Good point David.  8.1.x in mga5 is essential then.

And mga6 will have owncloud 8.3.x in release
then we absolutely also need 8.2.x too in mga5 backports.

As 8.2 is released it is of course good to have it too in mga5 backports...
(Coffe started working now)

Thank you for the 8.0.10 update david.
If anyone attempt 81 and 8.2 backports i can try them.

(In reply to Morgan Leijström from comment #9)
> Thank you for the 8.0.10 update david.
> If anyone attempt 81 and 8.2 backports i can try them.

I think we will only provide 8.1 backports when either :
- 8.0 is not provided anymore
- MGA6 will be out and then the upgrade path will be install MGA5 8.1 as update then upgrade to MGA6.

I am afraid many users then will upgrade mga5 to mga6 and not until after that realise they should have waited for owncloud 8.1 on mga5 first.
I added Upgrade chapter https://wiki.mageia.org/en/OwnCloud#Upgrading

Yes, we will need to add a note about this to the Mageia 6 Release Notes.

Now 9 and 9.0.1 have been released, with some issues.

There is interesting reading 
https://forum.owncloud.org/viewtopic.php?f=38&t=33274

So i suggest to have upcoming 9.0.2 or later in mga6 at release.

Maybe we should discuss if we should just simply skip making 8.1 and 8.2 ?
And in errata tell about the problem.
There are much possible troble for the user either way, three incremental updates, or one big, or reinstall and get new data synced/restored....

I think i will myself make a fresh install of mga6 including fresh install of owncloud 9.x...

Will mga6 release with PHP7.0.6? or update to it soon?

OwnCloud 9.0.3 (not 9.0.2 or earlier) will work with PHP7.0.6
https://github.com/owncloud/core/pull/24326
https://github.com/owncloud/core/pull/24343
(BTW, possibly there will be fix backported to owncloud 8.x and 9.0.0 )

9.0.2 is due may3
https://github.com/owncloud/core/milestones

When someone packages 9.0.2 for cauldron 64 bit, and we have PHP7 < 7.0.6 i will consider reinstalling my in-house production fileserver to mga6 and that owncloud - if i see no other problem.  Else maybe wait for 9.0.3.

For visibility i changed issue to concern Cauldron and MGA5TOO, as solving owncloud server upgrading concerns both.

Version: 5 => Cauldron
Whiteboard: (none) => MGA5TOO

As talked in MGA DEV ML, I have pushed version 8.1.10 to backports testing.
I will also push 8.2.8 version and 9.0.5 when this 8.1.10 version will be tested and validated.

The only rpm is a noarch owncloud-8.1.10-1.mga5

Keywords: (none) => Backport
Version: Cauldron => 5
Assignee: mageia => qa-bugs
Summary: Update owncloud server to 8.2.1 need first 8.1.x ! => Backport Candidate: Upgrade owncloud to 8.1.10
Whiteboard: MGA5TOO => (none)

Thank you for your work :)

First I updated to owncloud-8.0.15-1.mga5.noarch.rpm from /core/updates_testing
Test OK, see Bug 19574 - Owncloud 8.0.15 fixes bugs in upgrade to 8.1.x

Then using MCC I installed owncloud-8.1.10-1, rebooted.
Logged into owncloud web interface and initiated the update
Error popped upp immediately in that dialog:

  Exception: Please upload the ca-bundle.crt file into the 'config' directory.

which ca-bundle.crt ?


Question:
Are we going to skip and withdraw the 8.2.1 now in updates testing?
I *think* so, but am too lazy/busy read up on owncloud recommendations atm...

This is probably a manual solution: (i have not tested yet)
https://forum.owncloud.org/viewtopic.php?t=30540

-but best if package can be made to work without it.

This is a known bug which was targeted 8.0.15 (?)
https://github.com/owncloud/updater/issues/164
still "to review?!"
https://github.com/owncloud/updater/pull/367

Possibly i have long ago fiddeld with configuration files to make it work better then, so maybe i have done something then that borked the update now.

(In reply to Morgan Leijström from comment #17)
> Error popped upp immediately in that dialog:
> 
>   Exception: Please upload the ca-bundle.crt file into the 'config'
> directory.
> 
> which ca-bundle.crt ?

This was a bug in my packaging. Please try with owncloud-8.1.10-2.mga5 when it will it the mirrors. Which both fixes this and recommends php-opcache to give better default performance.

> Question:
> Are we going to skip and withdraw the 8.2.1 now in updates testing?
> I *think* so, but am too lazy/busy read up on owncloud recommendations atm...

Yes, the plan is to push 8.2.8 in backports when 8.1.10 will be validated and pushed to core/backports.

Test OK:
I did nothing more since comment 17, just urpmi owncloud-8.1.10-2.mga5,
and then into web interface (no need to reboot),
and initiated the upgrade which went quick, and it works.

Setting FOR ERRATA as per discussion in dev ML we need to write notes there,  https://wiki.mageia.org/en/Mageia_6_Errata

directing Owncloud Users to read https://wiki.mageia.org/en/OwnCloud#Upgrading


Waiting for your 8.2.latest and then 9.0.latest  :)

Summary: Backport Candidate: Upgrade owncloud to 8.1.10 => OwnCloud server upgrade path Mageia 5 to Mageia 6
Whiteboard: (none) => FOR ERRATA

(In reply to Morgan Leijström from comment #20)
> Setting FOR ERRATA as per discussion in dev ML we need to write notes there,
> https://wiki.mageia.org/en/Mageia_6_Errata

Changing to FOR_ERRATA6 which is what will be used for Mageia 6 Errata along with IN_ERRATA6 once written.

Whiteboard: FOR ERRATA => FOR_ERRATA6

Thanks Samuel.
Do we have a list of code words like this, where?

(In reply to Morgan Leijström from comment #22)
> Thanks Samuel.
> Do we have a list of code words like this, where?

Most are written in the wiki, but this one it probably not defined anywhere. I'm probably the first one to state it outside of IRC. We need to update the appropriate wiki page somewhere. We probably also need to make that a keyword rather than a whiteboard entry. Feel free to start the discussion on the dev ML, I'll follow-up.

Samuel

This commit is incorrect:
http://svnweb.mageia.org/packages/backports/5/owncloud/current/SPECS/owncloud.spec?r1=1060819&r2=1060818&pathrev=1060819

You should *not* bundle a ca-bundle.crt file, the package should install a symlink to the system one in /etc/pki/tls/certs.

Whiteboard: FOR_ERRATA6 => FOR_ERRATA6 feedback

(In reply to David Walser from comment #24)
> You should *not* bundle a ca-bundle.crt file, the package should install a
> symlink to the system one in /etc/pki/tls/certs.

Thanks for the hint. Fixed in 

owncloud-8.0.15-3.mga5.noarch.rpm

Me who installed 8.0.15-2, and then 8.1.10-1, what should i do to be on track?
(so i test next step from correct state)

(In reply to Morgan Leijström from comment #26)
> Me who installed 8.0.15-2, and then 8.1.10-1, what should i do to be on
> track?
> (so i test next step from correct state)

I said something silly. It is version 8.1.10-3 that fixes the problem. So you can just install it. I think we should validate this 8.1.10 and push it to backports before pushing 8.2.x to testing.

So please indicate if you tested on 32 or 64 bits.

Whiteboard: FOR_ERRATA6 feedback => FOR_ERRATA6 MGA5-64-OK

OK.  I urpmi 8.1.10-3, and also rebooted, this time no question of updating database (And i did not expect it)  It just continue to work.
mga5 64bit

IMO, fix that cert problem in 8.0.15 before pusing to updates

(In reply to Morgan Leijström from comment #28)
> IMO, fix that cert problem in 8.0.15 before pusing to updates

No, Owncloud started with this certificate only in 8.1.x versions...

I could test another system I have, which is 32 bit. All is Ok.

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

Many thanks to José & Morgan for your work on this difficult backport.
Validated.
Can sysadmins please push it.

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

done.

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

Upgrade to 8.2.8 in the #19634 bug.

@José

I wonder if you saw some problem with php-opcache?

I do not currently, but i have seen problems before:
https://wiki.mageia.org/en/OwnCloud#To_do_in_this_document
https://wiki.mageia.org/en/OwnCloud#PHP_caching

Of this problem is obsolete, we can strip the text about the problem from the wiki.

BTW I also split the wiki article "Introduction" so there now is a news section
https://wiki.mageia.org/en/OwnCloud#News

(In reply to Morgan Leijström from comment #33)
> @José
> 
> I wonder if you saw some problem with php-opcache?
> 

I've never had problems with php-opcache, which is Recommended by owncloud package. So if you have no reproductible bug, I think we can remove this warning.

OK, I removed the warning, and also added instruction on adding a line in config for enabling APCu, quick test OK here.

I have for long time not made a fresh install of owncloud.
Do you know if bug 16179 is resolved? - If so please close it.

Maybe also the Mageia 6 owncloud package should recommend php-opcache?

(In reply to Morgan Leijström from comment #36)
> Maybe also the Mageia 6 owncloud package should recommend php-opcache?

Or, let it be. I better re-add it to instructions instead?

(In reply to Morgan Leijström from comment #37)
> (In reply to Morgan Leijström from comment #36)
> > Maybe also the Mageia 6 owncloud package should recommend php-opcache?
> 
> Or, let it be. I better re-add it to instructions instead?

No need. owncloud requires php-opcache in Mageia 6.

Uhm.. i was going to check, but can not find any owncloud server in cauldron anywhere?? - Strange, i know i saw it before...?!

And if i on my cauldron try
 urpmi owncloud
it wants to install * Nextcloud 10 * ( and much more, including php-opcache )

In Cauldron, Nextcloud replaces ownCloud.

Ah, so no ownClud server at all in mga6?

OK clean and nice.


*  But, then we need also ownCloud 9.0.5 in mga5 backport, now !  *


BTW, What is the plan for nextcloud client ?

(In reply to Morgan Leijström from comment #41)
> Ah, so no ownClud server at all in mga6?

Nextcloud is a drop-in replacement, so it is the ownCloud server for mga6.

> OK clean and nice.
> 
> 
> *  But, then we need also ownCloud 9.0.5 in mga5 backport, now !  *

IIRC, Nextcloud can upgrade from oC 9, so yeah I guess so.

> BTW, What is the plan for nextcloud client ?

I have no idea.

Yes, upgrades from both OC 9.0 and 9.1 to Nextcloud 10 should officially work.

From 8.2 people have both failed and succeeded upgrading to Nextcloud after manual work... so we need (at least) 9.0.latest in mga5.


For Nextcloud clients it looks like it is still same as owncloud client, same last version numbers.

So i suggest we keep the owncloud client we have in cauldron, which is the latest, and when there is a newer Nextcloud client we switch brand.


BTW, someone still have to verify the newest client on mga5, Bug 19583 - Backport Candidate: Update owncloud-client to 2.2.4   Possibly i can try next week on a colleagues mga5-64

For mga5 the later clients are to come in backport because update 1.x to 2.x needed manual (re)configuration.

Unless they screw up compatibility again, client updates in cauldron can be in normal updates repo.


I guess Nextcloud server updates are disruptive like on mga5 (?), so server updates shall probably be in backports, analogous to what we now do on mga5

(In reply to Morgan Leijström from comment #43)
> I guess Nextcloud server updates are disruptive like on mga5 (?), so server
> updates shall probably be in backports, analogous to what we now do on mga5

My understanding is that Nextcloud plans to handle upgrades better and more responsibly than ownCloud has.

(In reply to Morgan Leijström from comment #41)
> Ah, so no ownClud server at all in mga6?
> 
> OK clean and nice.
> 
> 
> *  But, then we need also ownCloud 9.0.5 in mga5 backport, now !  *
> 
> 
> BTW, What is the plan for nextcloud client ?

it will be packaged

(In reply to David Walser from comment #44)
> My understanding is that Nextcloud plans to handle upgrades better and more
> responsibly than ownCloud has.

That is a good direction.
We need to test that practically in whatever_testing when it is due.

(In reply to David Walser from comment #40)
> In Cauldron, Nextcloud replaces ownCloud.

The owncloud package seems to have been dropped from mirrors, but the package was not moved to obsoletes?

Anyway, I will push Oc9.0 to MGA5 backports as this is now needed : #19662.

Great, i will test mga5 Oc9.0 when it lands

@José: if you in a comment write "bug " before the bug number it will automatically be a helpful link: bug 19662

Thx to whoever added this to the Mga6 errata

Keywords: FOR_ERRATA6 => IN_ERRATA6
CC: (none) => marja11

Thanks Marja, it was me :)
Now i also added a hint at https://wiki.mageia.org/en/Mageia_6_Release_Notes#Upgrading_from_Mageia_5 because this is a rather unusual procedure.

Time have passed and we now need more versions to bridge the gap mga5 to 6, i issued a fresh Bug 20953 for continued work.