Ask Your Question
0

New Install, Distro Upgrade Failed

asked 2013-02-03 16:46:53 -0600

tonybrowning gravatar image

updated 2014-09-29 16:18:32 -0600

mether gravatar image

Keeps repeating this.

--> Processing Dependency: desktop-notification-daemon for package: notify-python-0.1.1-20.fc17.i686
--> Processing Dependency: desktop-notification-daemon for package: libnotify-0.7.5-1.fc17.i686
---> Package openssh-clients.i686 0:5.9p1-22.fc17 will be updated
---> Package openssh-clients.i686 0:5.9p1-28.fc17 will be an update
---> Package polkit.i686 0:0.104-6.fc17 will be erased
--> Processing Dependency: polkit for package: system-config-date-1.10.5-1.fc17.noarch
---> Package python-slip-gtk.noarch 0:0.2.20-2.fc17 will be updated
---> Package python-slip-gtk.noarch 0:0.2.24-1.fc17 will be an update
---> Package setuptool.i686 0:1.19.11-4.fc17 will be erased
---> Package system-config-date.noarch 0:1.10.5-1.fc17 will be an update
--> Processing Dependency: polkit for package: system-config-date-1.10.5-1.fc17.noarch
---> Package system-config-keyboard.i686 0:1.3.1-8.fc17 will be erased
---> Package systemd.i686 0:44-23.fc17 will be an update
--> Processing Dependency: authconfig for package: systemd-44-23.fc17.i686
---> Package telepathy-mission-control.i686 1:5.12.0-1.fc17 will be erased
--> Processing Dependency: telepathy-mission-control >= 5.5.0 for package: telepathy-gabble-0.16.0-1.fc17.i686
---> Package unique3.i686 0:3.0.2-3.fc17 will be erased
---> Package usermode-gtk.i686 0:1.109-1.fc17 will be erased
---> Package xdg-user-dirs-gtk.i686 0:0.9-1.fc17 will be erased
---> Package zenity.i686 0:3.4.0-1.fc17 will be erased
--> Running transaction check
---> Package PackageKit-device-rebind.i686 0:0.7.5-1.fc17 will be erased
---> Package gnome-keyring-pam.i686 0:3.4.1-4.fc17 will be erased
---> Package gnome-python2-gnomekeyring.i686 0:2.32.0-9.fc17 will be erased
---> Package gtk3.i686 0:3.4.4-1.fc17 will be erased
--> Processing Dependency: libgdk-3.so.0 for package: ibus-1.4.99.20121109-9.fc17.i686
--> Processing Dependency: libgdk-3.so.0 for package: ibus-gtk3-1.4.99.20121109-9.fc17.i686
--> Processing Dependency: libgtk-3.so.0 for package: ibus-1.4.99.20121109-9.fc17.i686
--> Processing Dependency: libgtk-3.so.0 for package: ibus-gtk3-1.4.99.20121109-9.fc17.i686
---> Package im-chooser.i686 0:1.5.2.2-1.fc17 will be erased
--> Processing Dependency: im-chooser for package: ibus-1.4.99.20121109-9.fc17.i686
---> Package libchamplain.i686 0:0.12.3-1.fc17 will be erased
---> Package libgnomekbd.i686 0:3.4.0.2-2.fc17 will be erased
--> Processing Dependency: libgnomekbd.so.7 for package: ibus-1.4.99.20121109-9.fc17.i686
--> Processing Dependency: libgnomekbdui.so.7 for package: ibus-1.4.99.20121109-9.fc17.i686
--> Processing Dependency: libgnomekbd for package: ibus-1.4.99.20121109-9.fc17.i686
---> Package libmash.i686 0:0.2.0-7.fc17 will be erased
---> Package libnotify.i686 0:0.7.5-1.fc17 will be erased
---> Package librsvg2.i686 0:2.36.1-1.fc17 will be erased
--> Processing Dependency: librsvg2 for package: ibus-1.4.99.20121109-9.fc17.i686
---> Package libsocialweb-keys.noarch 0:0.25.21-1.fc17 will be erased
---> Package metacity.i686 0:2.34.3-1.fc17 will be erased
---> Package notify-python.i686 0:0.1.1-20.fc17 will be erased
--> Processing Dependency: notify-python for package: ibus-1.4.99.20121109-9.fc17.i686
---> Package polkit.i686 0:0.104-6.fc17 will be erased
--> Processing Dependency: polkit for package ...
(more)
edit retag flag offensive close merge delete

Comments

1

Not really sure. Can you explain what happened and how this came about? If the power or something went out while yum was running, it may be irreversible. If you haven't set it up much, I'd recommend a fresh install.

FranciscoD_ gravatar imageFranciscoD_ ( 2013-02-22 08:34:05 -0600 )edit

As pointed out it might be easier to start over. If you back-up your home dir, personal setting will be there for you. System settings are better to use defaults and tune if necessary. In any case, take a back-up to an external drive so you can later recover any configuration files needed to restore your config.

Aleksandar Kostadinov gravatar imageAleksandar Kostadinov ( 2013-02-22 09:54:14 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
2

answered 2013-02-23 05:02:18 -0600

kynde gravatar image

I had a similar sudden power failure during upgrade (kids). Here are few things that may help you out:

  • try running package-cleanup to remove the possible dupes
  • remove offending packages (with yum remove), you can always install them back afterwards
  • you might want to reinstall the package (or packages) during which it shutdown, if you have an idea what they were
  • and then if you get it through, it'd still be a good idea to verify the packages

But if it's indeed a fresh new install that you're upgrading, I certainly recommend starting over.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2013-02-03 16:46:53 -0600

Seen: 468 times

Last updated: Feb 23 '13