[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: system-config-network issue



On Sat, Dec 27, 2008 at 1:42 PM, Alain Roger <raf news gmail com> wrote:
>> Well first of all, just as a warning, if you don't know how to do
>> this, it probably means you shouldn't be doing this. Just a warning.
>> Here goes.
>>
>> You need to run the following command from the same directory where
>> you have both those rpms:
>> yum localinstall system-config-network-1.5.95-1.fc10.noarch.rpm
>> system-config-network-tui-1.5.95-1.fc10.noarch.rpm
>>
>> You may be able to do this from the GUI, but I rarely use it myself,
>> so I don't know how.
>
>
> so i get the same answer as i got before:
>
>> yum localinstall system-config-network-1.5.95-1.fc10.noarch.rpm
>> system-config-network-tui-1.5.95-1.fc10.noarch.rpm
>> Loaded plugins: refresh-packagekit
>> Setting up Local Package Process
>> Examining system-config-network-1.5.95-1.fc10.noarch.rpm:
>> system-config-network-1.5.95-1.fc10.noarch
>> Marking system-config-network-1.5.95-1.fc10.noarch.rpm as an update to
>> system-config-network-1.5.93-2.fc10.noarch
>> Examining system-config-network-tui-1.5.95-1.fc10.noarch.rpm:
>> system-config-network-tui-1.5.95-1.fc10.noarch
>> Marking system-config-network-tui-1.5.95-1.fc10.noarch.rpm as an update to
>> system-config-network-tui-1.5.93-2.fc10.noarch
>> Resolving Dependencies
>> --> Running transaction check
>> ---> Package system-config-network.noarch 0:1.5.95-1.fc10 set to be
>> updated
>> ---> Package system-config-network-tui.noarch 0:1.5.95-1.fc10 set to be
>> updated
>> --> Finished Dependency Resolution
>>
>> Dependencies Resolved
>>
>>
>> ==============================================================================================================================================================
>>  Package                                Arch
>> Version
>> Repository                                                       Size
>>
>> ==============================================================================================================================================================
>> Updating:
>>  system-config-network                  noarch
>> 1.5.95-1.fc10
>> system-config-network-1.5.95-1.fc10.noarch.rpm                  1.8 M
>>  system-config-network-tui              noarch
>> 1.5.95-1.fc10
>> system-config-network-tui-1.5.95-1.fc10.noarch.rpm              4.7 M
>>
>> Transaction Summary
>>
>> ==============================================================================================================================================================
>> Install      0 Package(s)
>> Update       2 Package(s)
>> Remove       0 Package(s)
>>
>> Total download size: 6.4 M
>> Is this ok [y/N]: y
>> Downloading Packages:
>> warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID
>> 0b86274e
>>
>>
>> Public key for system-config-network-tui-1.5.95-1.fc10.noarch.rpm is not
>> installed
>> [root fed1032 Download]#
>
> and internet works well in DHCP because i'm able to browse internet
> normally.
> :-(
> what am i doing wrong ?


Well, this 'answer' is entirely different. Fedora packages are
typically signed to prove that they come from approved Fedora sources.
yum check for that 'public key' to verify the package. Apparently, you
didn't get the package from an approved source, and so yum doesn't
want to install them -- basically it's trying to protect you.

If you are really sure that you want to do this:

yum --nogpgcheck localinstall
system-config-network-1.5.95-1.fc10.noarch.rpm
system-config-network-tui-1.5.95-1.fc10.noarch.rpm

-- 
Fedora 9 : sulphur is good for the skin
( www.pembo13.com )


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]