Description of problem: some (potential) new users find it too hard to add wine(32), as a search in MCC with default settings only returns wine(64).Like steam,(proposed) ensure 32bit repos are enabled - should be by default anyway. see https://distrowatch.com/dwres.php?resource=ratings&distro=mageia comment: Date: 2021-02-21 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Hi, thanks reporting this. Hum, a link to a wiki page that can be translated should be also a good point, should not it? Meanwhile, Assigned to the package maintainer. (Please set the status to 'assigned' if you are working on it)
Whiteboard: (none) => MGA7TOO MGA8TOOTarget Milestone: --- => Mageia 9Source RPM: (none) => mageiawelcome-2.11-1.mga8.src.rpmStatus comment: (none) => Request for enhancementCC: (none) => ouaurelienAssignee: bugsquad => yves.brungard_mageia
Status: NEW => ASSIGNED
Hello, I don't mean to add Wine in Mageia Welcome. The software doesn't seem to be enough important to be in it. The way to improve the situation could be the wiki, as Aurelien said.
Version: Cauldron => trunkSummary: Please add Wine(32) to Mageia Welcome applications tab. => Explain how to add Wine(32) in a wiki pageComponent: RPM Packages => wiki.mageia.orgAssignee: yves.brungard_mageia => doc-bugsProduct: Mageia => WebsitesTarget Milestone: Mageia 9 => ---
Whiteboard: MGA7TOO MGA8TOO => (none)CC: (none) => yves.brungard_mageia
We could also add the link to the wiki page in MageiaWelcome...;)
Most of the emulators(Wine, PlayOnLinux, not sure about Lutris) and game platforms(Steam) need 32bit repos in order to be fully functional and headache free for inexperienced users. There are two major steps to solve this in order to have a non-complicated experience with these packages. 1 - First is to make sure that users know/are informed that 32bit repos are needed/desired to be made available every time they want packages that are dependent/enhanced by 32bit libraries. 2 - Clear instructions on how to do a proper repository access/management for their needs. Second point is straight forward for you, but it needs to be somehow easily accessible on the physical system and online. The first point is more difficult as it really needs to pop up in different places( MageiaWelcome, Rpm description/summary, ...) to be sure Mageia users notice and are aware of the steps( second point mainly ) they need to take for an optimal experience. One other issue, more like a third step, is to make sure the 64bit rpms have been build with "Recommends" for 32bit rpms that "enhances" them such that they are automatically selected to be installed if the 32bit repos are available and the user doesn't have to chase down these packages one by one. As an example, installing wine64 should pull wine32 and at least opengl/graphical 32bit libraries it the 32bit repos are available, similarly for PlayOnLinux. This is my opinion as a mageia user. Keep up the good work guys, as I honestly appreciate it.
CC: (none) => arusanu
Is there any downside to enabling the core 32-bit repository in the installer by default ? I would think that it's harmless, since we're not going to fish for 586 packages explicitly on a 64-bit system unless a 64-bit package wants them. That way the 32-bit repos are available later if needed without the need for any action on the users' part.
CC: (none) => ftg
not a downside, just that the CI only has the 32 or 64 bit repos (core / non-free)respectively. need to be sure that the new user is able to get on line to add the extra repos. due to space issues, no 32bit rpms are included in the 64 Live or CI .isos. If there is no way to get on line, (think Broadcom WIFI) any automated method during the install will mark the 32bit repos with an error and they will not be enabled. I am happy to be wrong here, though.
One option is to setup the 32bit repos from the first installation/upgrade of the distribution on the 64bit installs but don't enable/activate them unless the user does it explicitly for his/hers needs. However he needs to be aware of these needs, and understands the issues of permanently enabling them.
We have in our wiki https://wiki.mageia.org/en/Ways_to_install_programs#32_bit_repos_on_64_bit_systems https://wiki.mageia.org/en/Ways_to_install_programs#Wine I think that is enough for the wiki, per this bug description. Of someone have other ideas, please fix and comment, or reopen this bug. For discussing automation of getting 32 bit wine on 64 bit Mageia, please open a separate bug. This all said we have several open bugs on wine.
CC: (none) => friResolution: (none) => FIXEDStatus: ASSIGNED => RESOLVED