Description of problem: On my cauldron box, Mageia update always displays this error : Désolé, le paquetage suivant ne peut pas être sélectionné : - dbus-sharp-glib-0.6.0-1.mga6.noarch I have this version installed: rpm -qa|grep dbus-sharp-glib dbus-sharp-glib-0.5.0-6.mga6 (noarch) In terminal, if I try to update manually, I have no message: [yann@cauldron ~]$ LC_ALL=C sudo urpmi dbus-sharp-glib [yann@cauldron ~]$ With verbose output: LC_ALL=C sudo urpmi dbus-sharp-glib --v getting lock on urpmi examining synthesis file [/var/lib/urpmi/Core Release (distrib1)/synthesis.hdlist.cz] examining synthesis file [/var/lib/urpmi/Nonfree Release (distrib11)/synthesis.hdlist.cz] examining synthesis file [/var/lib/urpmi/Tainted Release (distrib21)/synthesis.hdlist.cz] examining synthesis file [/var/lib/urpmi/Core 32bit Release (distrib31)/synthesis.hdlist.cz] examining synthesis file [/var/lib/urpmi/Nonfree 32bit Release (distrib36)/synthesis.hdlist.cz] examining synthesis file [/var/lib/urpmi/Tainted 32bit Release (distrib41)/synthesis.hdlist.cz] getting exclusive lock on rpm found package(s): dbus-sharp-glib-0.6.0-1.mga6.noarch dbus-sharp-glib-0.6.0-1.mga6.noarch unlocking urpmi database unlocking rpm database
CC: (none) => mageia
Please don't paste big logs as they're unreadable as bugzilla wrap them. Next time, pleast put them in a text file and attach it. Can you try "urpmi --debug dbus-sharp-glib" eg attach the /tmp/debug.txt file resulting from running LC_ALL=C sudo urpmi --debug dbus-sharp-glib 2>&1|tee /tmp/debug.txt
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaud
Created attachment 7985 [details] urpmi debug log Ok Thierry, no problem. Sorry for the big message. Then there is the asked file. Regards Yann
You've dbus-sharp 1:0.7.0 installed (it has an epoch). You need to downgrade it in order to update it ( :-) ) Try urpmi --downgrade dbus-sharp
Source RPM: dbus-sharp-glib-0.5.0-6.mga6.src.rpm => dbus-sharp-glib-0.5.0-6.mga6.src.rpm, dbus-sharp1.0, dbus-sharp
It has worked! Thank you Thierry. I am not sure, but I think this bug can be closed.
Yes that was a temporary cauldron issue
Status: NEW => RESOLVEDResolution: (none) => WONTFIX