4

yum update errors. Why did it do what it did?

view full story
linux-howto

http://forums.fedoraforum.org – I just did 'yum update' on my system and got a number of errors such as this one: Code:   Updating      : xfce4-settings-4.6.1-4.fc11.i586                      87/184 Error unpacking rpm package xfce4-settings-4.6.1-4.fc11.i586 error: unpacking of archive failed on file /usr/share/locale/zh_CN/LC_MESSAGES/xfce4-settings.mo;4ad11889: cpio: open Sometimes instead of "cpio: open" it was "cpio: rename". There were a total of 18 such errors. These were listed as failures in the summary at the end. I then did another "yum update" and it redid 17 of the 18 successfully. It did not redo f-spot. Here's a snippet of the summary at the end of the first update: Code: Updated:   apr.i586 0:1.3.9-1.fc11                                                          b43-fwcutter.i586 0:012-2.fc11                                                  bluez.i586 0:4.42-6.fc11                                                        bluez-cups.i586 0:4.42-6.fc11                                                    bluez-libs.i586 0:4.42-6.fc11                                                    <snip>                                        yum-utils.noarch 0:1.1.23-1.fc11                                              Replaced:   f-spot.i586 0:0.6.0.0-1.fc11                                                  Failed:   exo.i586 0:0.3.101-4.fc11                                                        f-spot.i586 0:0.6.1.2-2.fc11                                                    gnome-settings-daemon.i586 0:2.26.1-11.fc11                                    <snip>                                            Complete! Note that f-spot was replaced but then failed. I checked to see what was installed: Code: []$ rpm -qa | grep f-spot f-spot-screensaver-0.6.1.2-2.fc11.i586 So I lost f-spot as a result of the failure. Why did it behave that way? Why was f-spot "replaced" rather than "updated". What's the difference? Recovery by 'yum install f-spot' was easy enough, but still. Thanks Jim (HowTos)