[Solved] Mageia 4, KDE, unable to select packages for update

[olorinpc]

Ok, searching didn't turn anything up, so I suspect this is something I did. A bit rusty in the linux world - so trying to resolve this issue and hopefully it is something simple.

I installed Mageia 4 last night on my laptop, during the process of setting up, config, etc... ran into the following error message:

Sorry, the following packages cannot be selected:

- lib64avcodec55-2.0.3-1.mga4.tainted.x86_64 (due to unsatisfied libvo-amrwbenc.so.0()(64bit))
- lib64mesagl1-10.0.5-1.mga4.tainted.x86_64 (due to unsatisfied lib64txc-dxtn)
- mesa-10.0.5-1.mga4.tainted.x86_64

I suspect that means a dependency is missing somehow.

It looks like the unsatisfied libraries are blocking those other packages from updating, anything that requires them from being installed etc. Are those supposed to be a part of something else that should have been installed etc? ie - what is the cleanest way to resolve without borking an otherwise clean install.

Thanks

[jkerr82508]

Have you enabled the /tainted/release repos?

https://wiki.mageia.org/en/Installing_a ... rrectly.3F

Jim

[olorinpc]

Hi Jim - good question, yes, though maybe I am missing one?

Code: Select all

urpmq --list-media active
Core Release
Nonfree Release
Core Updates (distrib1)
Nonfree Updates (distrib2)
Tainted Updates (distrib3)
Core 32bit Updates (distrib4)
Nonfree 32bit Updates (distrib5)
Tainted 32bit Updates (distrib6)
Core Release (distrib7)
Core Updates (distrib9)
Nonfree Release (distrib17)
Nonfree Updates (distrib19)
Core 32bit Release (distrib37)
Core 32bit Updates (distrib38)
Nonfree 32bit Release (distrib42)
Nonfree 32bit Updates (distrib43)

[jkerr82508]

As I indicated in my earlier post, you need to activate /tainted/release and /tainted32bit/release.

You should also remove the first two in that list /core/release and /nonfree/release (without the "distrib" number) - those are the repo's on the installation CD/DVD and are of limited use after installation.

Jim

[olorinpc]

Oh... I think I just noticed the difference then as you *were* pointing out.

I have the tainted *updates* activated... but not the tainted release...

Which you can't update something that you don't have installed in the first place. When I get back to that PC I will try that, report back, and hopefully resolve the thread

[olorinpc]

Yep, that was it. Somehow had everything turned on put the repo I needed.

Thanks for helping identify that!