Attachment 35647 Details for Bug 28102 – Yum output about the broken packages situation

Yum output about the broken packages situation

yum_output.txt (text/plain), 3.48 KB, created by Markku Korkeala on 2010-05-14 01:49:17 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Markku Korkeala

Created: 2010-05-14 01:49:17 UTC

Size: 3.48 KB

patch

obsolete

># yum install contacts dates xguest
>Loaded plugins: auto-update-debuginfo, presto, refresh-packagekit
>Found 23 installed debuginfo package(s)
>Enabling livna-debuginfo: rpm.livna.org for 13 - i386 - Debug
>Reading repository metadata in from local files
>livna-debuginfo                                                                                     | 1.0 kB     00:00     
>Enabling rpmfusion-free-updates-debuginfo: RPM Fusion for Fedora 13 - Free - Updates Debug
>Reading repository metadata in from local files
>rpmfusion-free-updates-debuginfo                                                                    | 2.3 kB     00:00     
>Enabling rpmfusion-free-debuginfo: RPM Fusion for Fedora 13 - Free - Debug
>Reading repository metadata in from local files
>Enabling updates-debuginfo: Fedora 13 - i386 - Updates - Debug
>Reading repository metadata in from local files
>updates-debuginfo/metalink                                                                          |  14 kB     00:00     
>updates-debuginfo                                                                                   | 3.1 kB     00:08     
>updates-debuginfo/primary_db                                                                        |  35 kB     00:00     
>Setting up Install Process
>Resolving Dependencies
>--> Running transaction check
>---> Package contacts.i686 0:0.9-5.fc13 set to be updated
>---> Package dates.i686 0:0.4.11-3.fc13 set to be updated
>---> Package xguest.noarch 0:1.0.8-6.fc13 set to be updated
>--> Processing Dependency: sabayon-apply for package: xguest-1.0.8-6.fc13.noarch
>--> Processing Dependency: policycoreutils-sandbox for package: xguest-1.0.8-6.fc13.noarch
>--> Running transaction check
>---> Package policycoreutils-sandbox.i686 0:2.0.82-13.fc13 set to be updated
>--> Processing Dependency: policycoreutils-python = 2.0.82-13.fc13 for package: policycoreutils-sandbox-2.0.82-13.fc13.i686
>--> Processing Dependency: matchbox-window-manager for package: policycoreutils-sandbox-2.0.82-13.fc13.i686
>--> Processing Dependency: xorg-x11-server-Xephyr for package: policycoreutils-sandbox-2.0.82-13.fc13.i686
>---> Package sabayon-apply.i686 0:2.29.92-1.fc13 set to be updated
>--> Processing Dependency: python-ldap for package: sabayon-apply-2.29.92-1.fc13.i686
>--> Running transaction check
>---> Package matchbox-window-manager.i686 0:1.2-6.20070628svn.fc12 set to be updated
>--> Processing Dependency: libmb.so.1 for package: matchbox-window-manager-1.2-6.20070628svn.fc12.i686
>---> Package policycoreutils-sandbox.i686 0:2.0.82-13.fc13 set to be updated
>--> Processing Dependency: policycoreutils-python = 2.0.82-13.fc13 for package: policycoreutils-sandbox-2.0.82-13.fc13.i686
>---> Package python-ldap.i686 0:2.3.10-1.fc13 set to be updated
>---> Package xorg-x11-server-Xephyr.i686 0:1.8.0-12.fc13 set to be updated
>--> Running transaction check
>---> Package libmatchbox.i686 0:1.9-7.fc13 set to be updated
>---> Package policycoreutils-sandbox.i686 0:2.0.82-13.fc13 set to be updated
>--> Processing Dependency: policycoreutils-python = 2.0.82-13.fc13 for package: policycoreutils-sandbox-2.0.82-13.fc13.i686
>--> Finished Dependency Resolution
>Error: Package: policycoreutils-sandbox-2.0.82-13.fc13.i686 (fedora)
>           Requires: policycoreutils-python = 2.0.82-13.fc13
>           Installed: policycoreutils-python-2.0.82-17.fc13.i686 (@updates-testing)
>           Available: policycoreutils-python-2.0.82-13.fc13.i686 (fedora)
> You could try using --skip-broken to work around the problem
> You could try running: rpm -Va --nofiles --nodigest
>#
>

Actions: View

Attachments on bug 28102: 35647

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.