Kpackagekit can not install local RPM

[Tommy He]

On 10/05/10 20:25, Temlakos wrote:
> On 05/10/2010 03:19 PM, Rahul Sundaram wrote:
>> On 05/11/2010 12:43 AM, Tommy He wrote:
>>
>>> Hello,
>>>
>>> I am not sure whether KDE user experience would be a part of criteria
>>> for desktop release. Nevertheless, it still might be helpful to arise
>>> some attention to this issue since it was filed during Beta testing
>>> phase and still lies in new status now.
>>>
>>> Basically, kpackagekit was unable to install the RPM out of the repos.
>>> The attempt to install RPM from local hard drive will result an error
>>> message, which said "Untrusted package". Though these packages can
>>> still be installed via terminal way, it's not a good experience of
>>> non-technical users in KDE environment.
>>>
>>> This bug persists in F13 RC2 LiveCD KDE i686.
>>> The bug I filed is here:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=585681
>>>
>> It is not part of the release criteria and would not block a release.
>> Nevertheless it should be considered a high priority bug.
>>
>> Rahul
>>
>
> Actually, I've installed downloaded RPMs just by clicking on them.
>
> I have also created my very own local repo and configured "smart" to
> recognize it as another "channel" and to install it whenever I have
> built something new for it.
>
> Nevertheless, the ability to install any RPM package is one of the
> things that caused me to stay with KDE when I tried it out. (Of course,
> moving from a Pentium III to a Pentium Dual Core with 3 GB of RAM did help!)
>
> Temlakos


Here are exact steps what I did to reproduce this problem:

1. Booting F13 RC2 LiveCD KDE i686
2. Open Konqueror and navigate to either Adobe 
Flash/VirtualBox/RPMFusion websites.
3. Download the RPM and save it to Home folder.
4. Click the RPM to invoke the kpackagekit.
5. After refreshing the package list, the kpackagekit dialogue minimised 
to notification area and indicated an error.
6. Click the error icon and choose Show Error Message, it says "Unable 
to install unsigned package."

If it was in GNOME, PackageKit-gnome would ask the user to type root 
password TWICE and proceed to install the unsigned local package.

Regards,

Tommy He

-- 
Take a Deep Breath out of Windows