This update candidate brings pcsx2 from a dev snapshot to the newly released 1.6.0 (close to what this dev snapshot was, but now stable). pcsx2 is a PlayStation 2 emulator, and requires a BIOS file dumped from a PS2 (subject to copyright) as well as a ROM image of a PS2 game (also subject to copyright). As such, while the emulator is FOSS and legal, its use might be subject to restrictions and I wouldn't ask the QA team to dig into it too deep. Just check that the emulator GUI opens fine, without trying to play an actual game (unless you're familiar with emulation and own the relevant devices and games that can make emulating them *somewhat* legal). NOTE: Package provided in tainted, and only in i586 flavor, so "Tainted 32bit Updates Testing" should be enabled to install this update candidate. Advisory: ========= Updated pcsx2 package provides new 1.6.0 stable release The pcsx2 package in Mageia 7 provided a pre-release snapshot of the 1.6.0, which was 4 year in development. This update provides the newly released 1.6.0, providing some further fixes and stability improvements. References: - https://pcsx2.net/293-pcsx2-1-6-0-is-out.html RPM in tainted/updates_testing: =============================== pcsx2-1.6.0-1.mga7.i586 SRPM in tainted/updates_testing: ================================ pcsx2-1.6.0-1.mga7
mga7, x86_64. Enabled 32-bit release and tainted updates. Installing pcsx2 hauled in 118 packages, mostly libraries. No problems. The application needs to be run from the Games menu and generates an openingui which allows the user to read documentation and invoke a wizard to lead her through the configuration steps and set options for drivers. As Rémi says, not much for QA to do. It looks OK anyway but holding off for a while in case somebody turns up to use it in anger.
CC: (none) => tarazed25
How do we label this one? Is it 32-bit notwithstanding the 64-bit hardware or 32-bit because it is emulated (like our 32-bit tests in 64-bit virtualbox)?
Whiteboard: (none) => MGA7-32-OK
Validating this for 32-bits. Advisory in the description, comment 0.
CC: (none) => sysadmin-bugsKeywords: (none) => validated_update
Keywords: (none) => advisoryCC: (none) => tmb
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2020-0128.html
Status: NEW => RESOLVEDResolution: (none) => FIXED