Yeah, I've never used pixieplus before but if I remember correctly it's
from the same guy that wrote the beloved Liquid KDE style engine, Mosfet. 
It's a small app and nothing should need it to run.

Trevor

Jarrod Major said:
> Okay, it is installed. I am in the process of removing it. It appears to
> cause no further conflicts, nothing is dependant upon it.
>
> I'll get back to you all when I get home...
>
> Jarrod
>
> ----- Original Message -----
> From: "Trevor Lauder" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, January 28, 2003 4:49 PM
> Subject: Re: (clug-talk) KDE 3.1
>
>
>> Err sorry, do you have pixieplus installed?  An "rpm -qa | grep -i
>> pixieplus" will tell you if there is a package installed with that
>> name in it.  If you don't use pixieplus and it's installed then you
>> can try removing it and then doing the upgrade.
>>
>> Trevor
>>
>> Jarrod Major said:
>> > There is no pixieplus RPM in that directory
>> >
>> > Jarrod
>> >
>> > ----- Original Message -----
>> > From: "Trevor Lauder" <[EMAIL PROTECTED]>
>> > To: <[EMAIL PROTECTED]>
>> > Sent: Tuesday, January 28, 2003 4:39 PM
>> > Subject: Re: (clug-talk) KDE 3.1
>> >
>> >
>> >> Have you tried moving that pixieplus rpm out of the download
>> directory and running the rpm -Fvh *.rpm without it?
>> >>
>> >> Jarrod Major said:
>> >> > Alrighty, so I got all 83 RPM's. I rebooted and went to runlevel
>> 3.
>> >> logged in as root. I did as the readme file suggested and issued
>> rpm -Uvh libart_lgpl*rpm from the download directory, those two
>> files went in okay. Then when I issued the command rpm -Fvh *rpm it
>> chugged along nicely and spit out the following error:
>> >> >
>> >> > file /opt/kde3/share/mimelnk/image/x-pcx.desktop from install of
>> >> kdelibs3-3.1-46 conflicts with file from package
>> >> pixieplus-kde-0.3-254
>> >> >
>> >> > I'm stumped. Google tells me that Pixie Plus os a fast image file
>> >> viewer. Beyond that nothing else. What do I do to resolve this
>> conflict? I'm assuming that because it hit this it did not continue
>> with the update.
>> >> >
>> >> > FYI, I have rebooted and can still get in to a KDE 3.0 desktop.
>> >> >
>> >> > Any assistance would be wonderful.
>> >> >
>> >> > Jarrod


Reply via email to