Hide Forgot
Description of problem: I can't install evolution-spamassassin using gnome-packagekit, but 'yum install evolution-spamassassin' would do it without problems. Version-Release number of selected component (if applicable): gnome-packagekit-2.91.92-2.fc15.x86_64 How reproducible: 100% Steps to Reproduce: 1.Install evolution and spamassassin, but remove evolution-spamassassin if installed 2.Activities -> Applications -> Add/Remove Software 3.Perform a by-name search for evolution-spamassassin 4.Select that package for installation and click Apply. Actual results: A dialog appears: ==> Transaction error An unspecified transaction error has occurred. More information is available in the detailed report. More details Protected multilib versions: evolution-2.91.92-1.fc15.i686 ! = evolution-2.91.92-2.fc15.x86_64 <== Additional info: [root@worm ~]# yum install evolution-spamassassin Loaded plugins: langpacks, presto, refresh-packagekit Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package evolution-spamassassin.x86_64 0:2.91.92-2.fc15 will be installed --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: evolution-spamassassin x86_64 2.91.92-2.fc15 fedora 94 k Transaction Summary ================================================================================ Install 1 Package(s) Total download size: 94 k Installed size: 30 k Is this ok [y/N]: y Downloading Packages: Setting up and reading Presto delta metadata Processing delta metadata Package(s) data still to download: 94 k evolution-spamassassin-2.91.92-2.fc15.x86_64.rpm | 94 kB 00:00 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : evolution-spamassassin-2.91.92-2.fc15.x86_64 1/1 Installed: evolution-spamassassin.x86_64 0:2.91.92-2.fc15 Complete!
This normally happens when the repos are out of sync -- but i'm amazed it worked in yum. Can you reproduce this?
No, it works now.