What the heck is all this?
Mark Eggers
mdeggers at gmail.com
Wed Aug 7 17:08:55 UTC 2013
On Wed, 07 Aug 2013 07:39:27 -0400, linuxnutster wrote:
> On 08/07/2013 07:26 AM, Tom Horsley wrote:
>> Just got this output from a yum update this morning:
>>
>> ...
>> Cleanup : glib2-2.36.3-2.fc19
>> 52/74 Cleanup : python-fedora-0.3.32.3-2.fc19.noarch
>> 53/74
>> /var/tmp/rpm-tmp.dtrblY: line 1: fg: no job control error:
>> %preun(kde-settings-kdm-19-23.fc19.noarch) scriptlet failed, exit
>> status 1 Error in PREUN scriptlet in rpm package
>> kde-settings-kdm-19-23.fc19.noarch
>> Cleanup : gstreamer1-plugins-base-1.0.8-1.fc19.x86_64
>> 54/74
>> error: kde-settings-kdm-19-23.fc19.noarch: erase failed
>> Cleanup : libvirt-daemon-driver-qemu-1.0.5.4-1.fc19.x86_64
>> 55/74 Cleanup :
>> libvirt-daemon-driver-lxc-1.0.5.4-1.fc19.x86_64 56/74
>> ...
>>
>> Failed:
>> kde-settings-kdm.noarch 0:19-23.fc19
>>
>> [root at tomh ~]# rpm -q kde-settings-kdm
>> kde-settings-kdm-19-23.fc19.noarch kde-settings-kdm-19-23.1.fc19.noarch
>>
>> So what is busted on my system? I have a feeling I shouldn't have two
>> different versions of the same rpm showing up as installed at the same
>> time.
>>
> I'm getting a lot of yum errors lately. I'm seeing --skip-broken in my
> sleep. Just now:
>
> Failed: kde-settings-kdm.noarch 0:19-23.fc19
Here's what I did to get around the issue. I don't know if it's correct,
your mileage may vary, offer void where prohibited, caveat emptor.
This is after I did a yum update, so I had both versions installed.
1. yum erase kde-settings-kdm-19-23.1.fc19.noarch
2. rpm -e --noscripts --nodeps kde-settings-kdm-19-23.fc19.noarch
3. yum install kde-settings-kdm
4. yum check
5. yum info kde-settings-kdm
Installed Packages
Name : kde-settings-kdm
Arch : noarch
Version : 19
Release : 23.1.fc19
Size : 32 k
Repo : installed
>From repo : updates
Summary : Configuration files for kdm
URL : http://fedorahosted.org/kde-settings
License : MIT
Description : Configuration files for kdm.
Step 3 will complain about missing dependencies, and the fact that
the RPM database was altered outside of yum.
I'll know if this cleaned everything up the next time I do
a yum update.
. . . . just my two cents
/mde/
More information about the users
mailing list