Bug 22254 - Update candidate: Lutris 0.4.14
Summary: Update candidate: Lutris 0.4.14
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA6-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2017-12-22 21:34 CET by Rémi Verschelde
Modified: 2017-12-31 01:11 CET (History)
1 user (show)

See Also:
Source RPM: lutris-0.4.13-1.mga6
CVE:
Status comment:


Attachments

Description Rémi Verschelde 2017-12-22 21:34:01 CET
Another update to Lutris to keep it in sync with the online installation scripts. See bug 20458 for examples of how it was tested previously.

Advisory:
=========

Updated lutris package improves compatibility with lutris.net scripts

  The lutris application relies on scripts hosted at the upstream website
  lutris.net. For an optimal experience, the client should be kept relatively
  in sync with the API used for the scripts of the online database.

  This update brings the latest version of Lutris with new features and bug
  fixes.

References:
 - https://github.com/lutris/lutris/releases/tag/v0.4.14


RPMs in core/updates_testing:
=============================

6:
 lutris-0.4.14-1.mga6.noarch


SRPMs in core/updates_testing:
==============================

6:
 lutris-0.4.14-1.mga6
Comment 1 Rémi Verschelde 2017-12-30 18:42:10 CET
I've been using this update candidate on Mageia 6 x86_64 for the last few days without any issue.

As it's a non-critical update with low risk of regression, and since the QA team has a lot on their hands, validating based on this single-arch test.

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

Comment 2 Mageia Robot 2017-12-31 01:11:09 CET
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2017-0139.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED


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