Bug 23593 - Update candidate: wesnoth 1.14.5
Summary: Update candidate: wesnoth 1.14.5
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA6-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2018-09-19 09:43 CEST by Rémi Verschelde
Modified: 2018-09-21 01:18 CEST (History)
1 user (show)

See Also:
Source RPM: wesnoth-1.14.4-1.mga6
CVE:
Status comment:


Attachments

Description Rémi Verschelde 2018-09-19 09:43:04 CEST
Advisory:
=========

Updated wesnoth packages bring latest maintenance release

  The game "Battle for Wesnoth" is updated to its latest upstream installment,
  fixing various bugs in campaigns or the engine.

  See the changelog for details.

References:
 - https://github.com/wesnoth/wesnoth/blob/1.14.5/changelog.md

SRPM in core/updates_testing:
=============================

wesnoth-1.14.5-1.mga6

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

wesnoth-1.14.5-1.mga6
wesnoth-data-1.14.5-1.mga6
wesnoth-server-1.14.5-1.mga6


Testing procedure:
==================

Run the "wesnoth" binary (directly and/or via desktop launcher) and check that the game runs fine. If you have time to spare and would enjoy it, feel free to try a campaign :)
Comment 1 Rémi Verschelde 2018-09-19 09:51:08 CEST
Tested successfully on Mageia 6 x86_64, loading a campaign I already started in an earlier version. Saved games are compatible and everything seems to work OK (though I only tested for a minute or so).

Whiteboard: (none) => MGA6-64-OK

Comment 2 Rémi Verschelde 2018-09-19 20:45:34 CEST
Advisory uploaded, validating.

Keywords: (none) => advisory, validated_update
CC: (none) => sysadmin-bugs

Comment 3 Mageia Robot 2018-09-21 01:18:58 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2018-0152.html

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


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