Bug 26741 - Backport nextcloud 18 to MGA7
Summary: Backport nextcloud 18 to MGA7
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Backports (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7-64-OK
Keywords: validated_backport
Depends on:
Blocks:
 
Reported: 2020-06-08 10:01 CEST by José Jorge
Modified: 2020-08-25 11:04 CEST (History)
4 users (show)

See Also:
Source RPM: nextcloud
CVE:
Status comment:


Attachments

Description José Jorge 2020-06-08 10:01:11 CEST
We will ship at least Nextcloud 19 in MGA8. Upgrading from  MGA7  a nextcloud setup will need a version 18 between 17 and 19.

This is the third backport with version 18 after versions 17 and 16.
Comment 1 José Jorge 2020-06-08 11:10:26 CEST
Tested in a first x86_64 server. All seems ok.

Whiteboard: (none) => MGA7-64-OK
Status: NEW => ASSIGNED

José Jorge 2020-06-08 11:10:35 CEST

CC: (none) => lists.jjorge

Comment 2 Thomas Andrews 2020-06-10 15:12:54 CEST
Validating.

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

Comment 3 José Jorge 2020-07-12 12:40:34 CEST
As this 18.0.5 was never pushed, I have updated to latest bugfix 18.0.6.

Files list :

Suggested Advisory:
Nextcloud 17 is needed as intermediate to upgrade to MGA8 which will bring at least Nextcloud 18. 

SRPM :

nextcloud-18.0.6-1.mga7.srpm

RPMS :
nextcloud-18.0.6-1.mga7.noarch.rpm
nextcloud-mysql-18.0.6-1.mga7.noarch.rpm
nextcloud-postgresql-18.0.6-1.mga7.noarch.rpm
nextcloud-sqlite-18.0.6-1.mga7.noarch.rpm

Keywords: validated_backport => (none)

Comment 4 José Jorge 2020-07-12 16:37:41 CEST
Tested again in 2 x86_64 servers.
Comment 5 Morgan Leijström 2020-07-12 23:39:50 CEST
Validating according to tests by José

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

Comment 6 Nicolas Lécureuil 2020-08-25 11:04:46 CEST
moved

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


Note You need to log in before you can comment on or make changes to this bug.