Description of problem: How reproducible: always Steps to Reproduce: ask for updating mageia then you have an error message : Désolé, le paquetage suivant ne peut pas être sélectionné (you cans select the packet) : - mencoder-1.0-1.rc4.0.r32713.5.mga1.tainted.x86_64 (car libtwolame.so.0()(64bit) est non satisfait) i checked that libtwolame x86_64 version is not in the list of the packets
it's work here, the x86_64 package is lib64twolame0 something wrong with your media ?
ok i use wrong name lib64twolame is in the list what i don't understand is : if this is a dependancy for mencoder why the installation of mencoder does not install lib64twolame packet ? i must manualy install it then i can update mencoder.
Well here it's without any issue :) Can you paste the output of rpm -qa | grep twolame ? and maybe rpm -qa | grep mencoder Something is wrong by you but I don't know why.
Looks like a combination of bug 2317, and problems with the requires on mencoder. bug 2317 is causing a problem trying to update mencoder from the core release, to the tainted version as twolame is not in the tainted repository. Due to bug 2317 all packages required by the tainted version, that are not required by the core version, will have to be linked to the tainted release repository. The same will apply to tainted updates when an update is added. Also, it looks like the tainted version is missing a bunch of requires. $ urpmq --media "Core Release (distrib1)" --requires-recursive mencoder|wc -l 395 $ urpmq --media "Tainted Release (distrib21)" --requires-recursive mencoder|wc -l 8 The tainted version should (I expect) have all of the requires that apply to the core version, just in case the program is installed from the tainted repository as a clean install, not as an update after installing from the core version.
CC: (none) => davidwhodgins
Looking through this again, I'm not sure what's going on here. Episteme, can you clarify how you are installing? Are you using urpmi, rpmdrake, or mgaapplet? Are you installing mencoder from tainted for the first time, or are you trying to update from an install of the core version, to the tainted version?
(In reply to comment #3) > Well here it's without any issue :) > > Can you paste the output of rpm -qa | grep twolame ? and maybe rpm -qa | grep > mencoder > > Something is wrong by you but I don't know why. [root@localhost ~]# rpm -qa | grep twolame lib64twolame0-0.3.12-7.mga1 [root@localhost ~]# rpm -qa | grep mencoder mencoder-1.0-1.rc4.0.r32713.5.mga1.tainted [root@localhost ~]#
Created attachment 923 [details] my drakrpm settings
(In reply to comment #5) > Looking through this again, I'm not sure what's going on here. > > Are you using urpmi, rpmdrake, or mgaapplet? rpmdrake > > Episteme, can you clarify how you are installing? > i install mageia (during the install i ask for updating) then i open the fist kde session then i checked the checkboxes of the sources according to the attachment 923 [details] (see comment 7) then i ask for updating then i have pb with mencoder and lib64twolame as reported then i manually install lib64twolame then i can update mencoder
Ok, so this is a bug 2317 problem. The tainted release version of mencoder has the following dependencies that the core release version does not have. # diff mencoder.Core.Release mencoder.Tainted.Release|grep '>' > libdca.so.0 > libmp3lame.so.0 > libopencore-amrnb.so.0 > libopencore-amrwb.so.0 > libtwolame.so.0 > libx264.so.110 > libxvidcore.so.4 These correspond to the packages libdca0 liblame0 libopencore-amr0 libtwolame0 libx264_110 libxvid4 All of these are in Tainted Release except libtwolame0, which is only in Core Release. Anyone who has mencoder from Core Releaes installed, who then enables Tainted release, will have trouble updating using mgaapplet, unless they have another package that requires libtwolame0 installed from Core Release, such as vlc, or audacity. I have both, so didn't notice the problem when I enabled tainted.
On second thought, Tainted Relase is not an update medium by default. I gather you either edited /etc/urpmi/urpmi.cfg directly or ran drakrpm-edit-media --expert, so you could change the update status. Correct?
(In reply to comment #10) > On second thought, Tainted Relase is not an update medium by default. > > I gather you either edited /etc/urpmi/urpmi.cfg directly or ran > drakrpm-edit-media --expert, so you could change the update status. > > Correct? did you see my rpmdrake source settings (joined attachemnt) ? tainted release is an update source. and becareful i speak about the >>x86_64<< mageiea 1 version
attach the file /etc/urpmi/urpmi.cfg it's better to see than an screenshot :)
For me this bug is an effect of bug #2317 but can happen only when the user adds Tainted Release as an update media (which is not the default). I wouldn't link any package from Tainted Release to Tainted Updates to workaround it, but rather try to get #2317 fixed.
CC: (none) => stormi
Created attachment 939 [details] urpmi.cfg
Attachment 939 mime type: application/octet-stream => text/plain
Depends on: (none) => 2317
(In reply to comment #13) > For me this bug is an effect of bug #2317 but can happen only when the user > adds Tainted Release as an update media (which is not the default). > > I wouldn't link any package from Tainted Release to Tainted Updates to > workaround it, but rather try to get #2317 fixed. So waiting :)
CC: (none) => marja11
bug 2317 was set to release blocker, so there is light at the end of the tunnel
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX