Description of problem: After the Mesa update, Steam has been uninstalled. It's imopossible to install it now. There are some packages missing in the new version (sorry for the french message): root@localhost ~]# urpmi steam Les paquetages suivants ne peuvent pas être installés, car ils dépendent de paquetages qui sont plus anciens que les versions installées : libdri-drivers-19.1.0-2.mga7 libmesagl1-19.1.0-2.mga7 steam-1.0.0.61-1.mga7.nonfree Version-Release number of selected component (if applicable): mesa 19.1.2.1 mga7 How reproducible: allways Steps to Reproduce: 1. 2. 3.
@ Rémi This is probably a duplicate of another bug I assigned to you this morning, but this one gives a hint about the cause :-) @ Philippe I'm assigning this report to our steam maintainer, because I think he can fix steam to use new mesa
Source RPM: Mesa => Mesa, steamCC: (none) => marja11Assignee: bugsquad => rverschelde
You need 32bit repos enabled to get the 32bit mesa installed on a 64bit system
CC: (none) => tmb
@ Thomas, I already have the 32bit repos enabled, the trouble came with the mesa update because probably some packages were missing in the update. I have only libdri-drivers-19.1.0-2.mga7 visible in MCC, no 19.1.2.x and the old one cannot be installed. It has been uninstalled as Steam during the mesa update.
They are there in the Core Updates media. Try to update the metadata with: urpmi.update -a Also, what does: urpmq --list-media active say ?
Also make sure that "Update" is ticked for 32bit Release and 32bit Updates media in `drakrpm-edit-media --expert`.
Why would 32bit Release need to be marked "Update"? Its static
(In reply to Thomas Backlund from comment #6) > Why would 32bit Release need to be marked "Update"? > > Its static Right, my mistake. Only 32 Updates media should be ticked as "Update".
@ Thomas, [phil@localhost ~]$ urpmq --list-media active Core Release Core Updates Core Backports Nonfree Release Nonfree Updates Nonfree Backports Tainted Release Tainted Backports Core 32bit Release Core 32bit Backports Nonfree 32bit Release Nonfree 32bit Backports Tainted 32bit Release Tainted 32bit Backports @Rémi, Core 32 bits Release is ticked and Core 32 bits Updates is ticked for updates. But Core 32 bits Update isn't in the list above. If I clicked the Core 32 bits Updates as activated, it appears in the list but there is still the same message for urpmi steam.
You should always enable all "Updates" repos matching "Release" repos that you're using, so if you use "Tainted Release", you also need "Tainted Updates" activated. You should also enable "Tainted 32bit Updates" for the same reason. > But Core 32 bits Update isn't in the list above. If I clicked the Core 32 bits Updates as activated, it appears in the list but there is still the same message for urpmi steam. After activating all missing Updates repositories, run `urpmi.update -a` and it should solve the issue.
Thanks Rémi, that did the job. What I don't understand is why I have to click for activation as the update was clicked automatically.
Status: NEW => RESOLVEDResolution: (none) => FIXED
The update checkbox means that this repository will be used by MageiaUpdate to check for new versions of packages. But the repository still has to be activated, otherwise it will be skipped. Repos which are activated but without the update checkbox will not be checked for updates, which is what happens for "Release" repositories which never change (so there's no point checking them all the time for new versions).
*** Bug 25222 has been marked as a duplicate of this bug. ***
CC: (none) => laidlaws
(In reply to Rémi Verschelde from comment #11) > The update checkbox means that this repository will be used by MageiaUpdate > to check for new versions of packages. But the repository still has to be > activated, otherwise it will be skipped. > > Repos which are activated but without the update checkbox will not be > checked for updates, which is what happens for "Release" repositories which > never change (so there's no point checking them all the time for new > versions). That makes sense, but it seems odd. That was going to be my next question. Repos which are checked only in the Updates column show the check mark as grayed out. In my case, I make it a rule to check Core 32 bit Release and Core 32 Bit updates, but this time, I had to re-install because dnf converted my Release 7 to Cauldron 8 (newsgroup post of Aug 2; not reported as a bug, but David said he was going to put a word in the right ears.) This time, apparently, I overlooked enabling the 32 bit repos, and the two packages involved are 32 bit (their developers are dragging the chain.) I just enabled the repos, and 32-bit updates of liblm_sensors, libglmapi and libsystemd0 were downloaded. I held off filing a bug report because something similar happened with the previous installation, and came good within 24 hours. Maybe I checked the repos in the meantime? "sudo urpmi steam" called in the 3 ones that Philippe mentions (and all the other Steam dependencies.) I will try Crossover next, but its case is identical. (Apologies: words are my tools in trade, but my mind is becoming cobwebby.)