Bug 20961

Summary: Owncloud 9.0.9 is backported to make easier MGA6 upgrade
Product: Mageia Reporter: José Jorge <lists.jjorge>
Component: BackportsAssignee: QA Team <qa-bugs>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: fri, lewyssmith, lists.jjorge, mageia
Version: 5Keywords: Backport, validated_backport
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard: MGA5-32-OK MGA5-64-OK
Source RPM: owncloud CVE:
Status comment:
Bug Depends on:    
Bug Blocks: 20953    

Description José Jorge 2017-05-28 16:16:04 CEST
As decided in bug 20953, I have uploaded owncloud version 9.0.9 to backports testing.

The only rpm is a noarch owncloud-9.0.9-1.mga5
José Jorge 2017-05-28 16:16:37 CEST

Keywords: (none) => Backport
Status: NEW => ASSIGNED
Assignee: bugsquad => qa-bugs
CC: (none) => lists.jjorge

Comment 1 Morgan Leijström 2017-05-28 21:10:13 CEST
Update 9.0.5 -> 9.0.9 went OK an a fully updated mga5 64bit (incl recent MariaDB)

Using: mariaDB, no LDAP or other fanciness, no sharing between other servers.

Method: disabled all apps in OC web UI, then without shutting down ownCloud, I issued 
# urpmi http://www.mirrorservice.org/sites/mageia.org/pub/mageia/distrib/5/x86_64/media/core/backports_testing/owncloud-9.0.9-1.mga5.noarch.rpm 

Then in ownCloud web UI i pressed the button to start update.  No issues reported.

It needed an update of an app which it prompted for and fetched automatically when i reenabled the app after owncloud update -> app update test OK.

File sharing tested OK.

Log looks like before (old minor problems i have not tracked down. I plan to do a full reinstall on Nextcloud 11 after i have tried all upgrades incl to NC11 on mga6).

Like earlier it complains at top of WebUI that some files did not pass integrity check which seems OK in this configuration.

CC: (none) => fri

Comment 2 José Jorge 2017-05-30 21:00:08 CEST
I have also tested this package with my 2 owncloud x86_64 servers. No problem, except what Morgan mentionned : "some files did not pass integrity".

This is the same tests that were done for previous backport, so marking it uploadable.

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

Comment 3 Lewis Smith 2017-06-02 21:43:36 CEST
Is there any reason not to 'validated_backport' this in keywords? It should then be pushed [I think].

CC: (none) => lewyssmith

Comment 4 José Jorge 2017-06-02 22:40:28 CEST
Right, I tagged it.

Keywords: (none) => validated_backport

Comment 5 Morgan Leijström 2017-06-06 16:09:53 CEST
Do we need to ping somebody to do the push?
Comment 6 Lewis Smith 2017-06-07 22:22:35 CEST
José: thanks for the validation. (I did not feel competent to judge).
Morgan: it is in the list to be pushed, no need to do more.
Comment 7 Morgan Leijström 2017-06-07 22:26:16 CEST
OK thanks for the info.

We got two more versions of ownCloud in the pipe to make mga5 ready for upgrading to mga 6; bug 20953.

(not to mention the upgrades would be valuable for mga 5 itself already for long...)
Comment 8 Nicolas Lécureuil 2017-06-10 08:38:05 CEST
moved.

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

Comment 9 Morgan Leijström 2017-06-10 09:25:27 CEST
Thanks :)
I am ready to try next per Bug 20953.
Comment 10 Morgan Leijström 2017-06-18 01:39:37 CEST
FYI, i made a fresh install of 9.0.9:
It went OK but still the following files "do not pass integrity check":

Results
=======
- core
	- INVALID_HASH
		- .htaccess
		- core/doc/admin/_sources/configuration_files/collaborative_documents_configuration.txt
		- core/doc/admin/_static/img/note_pencil.svg
		- core/doc/admin/_static/img/warning.svg
		- core/doc/admin/_static/style.css
		- core/fonts/LICENSE.txt
		- core/vendor/jquery-migrate/jquery-migrate.js
		- core/vendor/jsTimezoneDetect/jstz.js
		- resources/config/ca-bundle.crt
	- FILE_MISSING
		- .user.ini
		- AUTHORS
		- COPYING-AGPL
- files_external
	- INVALID_HASH
		- 3rdparty/Dropbox/API.php
Morgan Leijström 2017-06-18 13:53:13 CEST

Blocks: (none) => 20953