urpmi --auto --keep --resume --noclean --downloader wget --wget-options -c --auto-select Some requested packages cannot be installed: kipi-plugins-acquireimages-3.0.0-0.beta1.1.mga3.x86_64 (due to unsatisfied libkipiplugins.so.3()(64bit)) kipi-plugins-advancedslideshow-3.0.0-0.beta1.1.mga3.x86_64 (due to unsatisfied libkipiplugins.so.3()(64bit)) kipi-plugins-batchprocess-3.0.0-0.beta1.1.mga3.x86_64 (due to unsatisfied libkipiplugins.so.3()(64bit)) kipi-plugins-calendar-3.0.0-0.beta1.1.mga3.x86_64 (due to unsatisfied libkipiplugins.so.3()(64bit)) WARNING: --keep option is in use. Some strange problems may happen installing lib64mesaegl1-9.0.0-1.mga3.tainted.x86_64.rpm lib64gbm1-9.0.0-1.mga3.tainted.x86_64.rpm lib64mesaegl1-devel-9.0.0-1.mga3.tainted.x86_64.rpm kipi-plugins-3.0.0-0.beta1.1.mga3.noarch.rpm lib64gbm1-devel-9.0.0-1.mga3.tainted.x86_64.rpm lib64mesaopenvg1-9.0.0-1.mga3.tainted.x86_64.rpm lib64iec61883_0-1.2.0-6.mga3.x86_64.rpm from /var/cache/urpmi/rpms Preparing... ############################################# Installation failed: file /usr/share/kde4/servicetypes/kipiplugin.desktop from install of kipi-plugins-1:3.0.0-0.beta1.1.mga3.noarch conflicts with file from package kipi-common-2:4.9.1-1.mga3.noarch While some packages may have been installed, there were failures. Some requested packages cannot be installed: kipi-plugins-acquireimages-3.0.0-0.beta1.1.mga3.x86_64 (due to unsatisfied libkipiplugins.so.3()(64bit)) kipi-plugins-advancedslideshow-3.0.0-0.beta1.1.mga3.x86_64 (due to unsatisfied libkipiplugins.so.3()(64bit)) kipi-plugins-batchprocess-3.0.0-0.beta1.1.mga3.x86_64 (due to unsatisfied libkipiplugins.so.3()(64bit)) kipi-plugins-calendar-3.0.0-0.beta1.1.mga3.x86_64 (due to unsatisfied libkipiplugins.so.3()(64bit)) [root@telaviv1 ~]# Please fix it, because it adds noise and clutter to the urpmi upgrade.
It is happening to me also
CC: (none) => fathom
Assignee: bugsquad => anaselli
Sorry I'm far from home in these two weeks, Please try asking mikala or neoclust. P.S. has nepomuk been enabled? https://bugs.mageia.org/show_bug.cgi?id=7015
For the file conflicts : This is an issue in digikam packaging (for the 3.0) & should be reported upstream. The kipiplugin.desktop is available in libkipi repository ( cf https://projects.kde.org/projects/kde/kdegraphics/libs/libkipi/repository ) so here upstream needs to make a choice to know where it should go. For the unsatisfied dependency : you should ask dlucio who did push (& no test locally according to the svn changelog) digikam 3.0 in testing.
(In reply to comment #3) > For the file conflicts : > > This is an issue in digikam packaging (for the 3.0) & should be reported > upstream. > The kipiplugin.desktop is available in libkipi repository ( cf > https://projects.kde.org/projects/kde/kdegraphics/libs/libkipi/repository ) > so here upstream needs to make a choice to know where it should go. > > For the unsatisfied dependency : > you should ask dlucio who did push (& no test locally according to the svn > changelog) digikam 3.0 in testing. Well, I don't understand what the problem is exactly, and how should I report it and get it fixed. John, can you file an issue in digikam and link to it here? Regards, -- Shlomi Fish
This problem still affects Cauldron and now after it was open again after the release of Alpha 2, it prevents me from seeing notices at the end of the installation, with prompts to reboot the machine. So it may be a security risk. I think I'm going to add the offending packages to /etc/urpmi/skip.list for the time being.
I can't understand why it has been uploaded since it was not ready, but i can't understand either is why you can't update cauldron when this package is in testing... that is not commonly used if not just for a test case. Anyway here someone has to decide if a) removing digikam 3.0.0 b) use digikam version of libkipi & co. instead of the one into kdegraphics otherwise we can't do anything for this problem. Cheers, Angelo
While those are not installable, is there any reason to store them in testing? Remove them and add when they are not causing such problem.
is this problem still valid?
Status: NEW => ASSIGNED
Keywords: (none) => NEEDINFO
No,the problem is solved.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED