I've been wanting to issue a backport for the game Valyria Tear, which reached version 1.0.0 earlier in 2014. But since backports seem stalled, and that the new version brings many new hours of gaming over the incomplete 0.6.0 version of Mageia 4, I'm going the updates way if such an exception is deemed reasonable. Basically version 1.0.0 implements the full story of "Episode 1", which all the corresponding gameplay mechanics and translations (thus fixing mga#12773). The previous Mageia 4 version had only the beginning of the story, less translations and of course a good share of bugs. Reproducible: Steps to Reproduce:
Blocks: (none) => 12773
Suggested advisory: =================== Valyria Tear 0.6.0 included Mageia 4 only contained a small subset of the storyline and gameplay elements that are now part of Valyria Tear 1.0.0 aka "Episode I". This version update brings the rest of the story to Mageia 4 users (the game is now 2 to 3 times longer than in 0.6.0), along with lots of new and improved translations (mga#12773) and many bug fixes. It is also the best version for players to try and give constructive feedback to the development team. References: http://valyriatear.blogspot.fr/2014/09/episode-i-release.html https://bugs.mageia.org/show_bug.cgi?id=12773 Packages: ========= SRPM: valyriatear-1.0.0-1.mga4 RPMs: valyriatear-1.0.0-1.mga4 valyriatear-data-1.0.0-1.mga4.noarch
Severity: normal => enhancementAssignee: remi => qa-bugsPriority: Normal => Low
Testing procedure: Install valyriatear and its valyriatear-data dependency (automatically pulled in by RPM). Launch the game, play around with the menu (press F1 to know the keys, it's not straight forward), try to change the language in the options, start a game and watch the intro. Then you can try to save the game (there is a save point in the room where the game starts), quit and make sure the saved game can be loaded. If you're into this type of game, you can play a bit more, but the above should already be sufficient ;-)
Whiteboard: (none) => has_procedure
I'm setting the feedback marker for now until MrsB, wilcal or Dave confirm that this update candidate is acceptable, seems I'm obviously hijacking the updates channel to push a backport :-)
Whiteboard: has_procedure => has_procedure feedback
Ok I changed my mind, I get this through the normal channel, i.e. backports. The packages are the same as in comment 1, but in the Core Backports Testing repo: Packages: ========= SRPM: valyriatear-1.0.0-1.mga4 RPMs: valyriatear-1.0.0-1.mga4 valyriatear-data-1.0.0-1.mga4.noarch
Priority: Low => NormalComponent: RPM Packages => BackportsWhiteboard: has_procedure feedback => has_procedureSeverity: enhancement => normal
Summary: Update candidate: valyriatear 1.0.0 => Backport candidate: valyriatear 1.0.0
Adding feedback marker until the backports process is up and running. It's currently awaiting some sysadmin stuff.
Whiteboard: has_procedure => has_procedure feedbackPriority: Normal => LowKeywords: (none) => Backport
This backport won't happen before the Mageia 4 EOL IMO, and we can use a QA testing list with less items :)
Status: NEW => RESOLVEDResolution: (none) => WONTFIX