Bug 28498 - Update Candidate: qgis 3.16.4 'Hannover' (new LTR)
Summary: Update Candidate: qgis 3.16.4 'Hannover' (new LTR)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL: https://www.qgis.org/en/site/getinvol...
Whiteboard: MGA8-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2021-03-01 13:32 CET by David GEIGER
Modified: 2021-03-22 18:18 CET (History)
2 users (show)

See Also:
Source RPM: qgis-3.10.13-1.mga8.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description David GEIGER 2021-03-01 13:32:57 CET 
Assigning to QA now,


Advisory:
========================

Upstream Qgis announced their new LTR 'Hannover' the 3.16.x series. Our current release is the previous LTR the 3.10.x series that is now EOL since January 2021.
So it is preferable to switch to the new LTR supported upstream.

========================

Packages in 8/core/updates_testing:
========================
qgis-grass-3.16.4-1.mga8.i586.rpm
qgis-devel-3.16.4-1.mga8.i586.rpm
python3-qgis-3.16.4-1.mga8.i586.rpm
qgis-3.16.4-1.mga8.i586.rpm

qgis-grass-3.16.4-1.mga8.x86_64.rpm
qgis-devel-3.16.4-1.mga8.x86_64.rpm
python3-qgis-3.16.4-1.mga8.x86_64.rpm
qgis-3.16.4-1.mga8.x86_64.rpm

Source RPM: 
========================
qgis-3.16.4-1.mga8.src.rpm
Comment 1 Aurelien Oudelet 2021-03-22 16:02:35 CET 
Installs well over existing version.

Opening https://docs.qgis.org/3.16/fr/docs/training_manual/index.html
to see some tutorial.

Give this an OK.
MGA8-64-OK.
Validating.

CC: (none) => ouaurelien, sysadmin-bugs
Whiteboard: (none) => MGA8-64-OK
Keywords: (none) => advisory, validated_update

Comment 2 Mageia Robot 2021-03-22 18:18:34 CET 
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2021-0047.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.