Topic: yum update for SME 7.1.3

[deragen]

I am trying to run  yum update for a SME 7.1.3 box.
 
Everything goes fine, the download of the patches completes and it asked
 
"is it ok?"
 
I enter the y (yes)
 
and get the following - have not seen this before, has anybody run into the problem.
 
"warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID 217521f6
 

Public key for perl-Net-IPv4Addr-0.10-2.el4.noarch.rpm is not installed
================================================================
No new rpms were installed. No additional commands are required.
================================================================
[root@spamfilter ~]#"

[mmccarn]

If you have enabled any non-default repositories perhaps there is a problem with one of them.

Try this:

Code: [Select]

yum --disablerepo=* \
--enablerepo=base \
--enablerepo=updates \
--enablerepo=smeaddons \
--enablerepo=smeos \
--enablerepo=smeupdates \
update

If that doesn't work, try resetting your yum repositories to default settings as described here: http://wiki.contribs.org/SME_Server:Documentation:Technical_Manual:Chapter6#Restoring_Default_Yum_Repositories
(Read above this link in the tech manual for more Yum info...)

Note:
SME v7.0 enabled only the 3 SME repositories by default.  SME v7.1 enabled the 5 listed above, but upgrading from 7.0 to 7.1 does not change the disabled status on the 2 Centos repositories (base and updates).

I've added a note to the FAQ: http://wiki.contribs.org/SME_Server:Documentation:FAQ#Which_repositories_should_be_enabled

and to the SME 7.1.3 announcement: http://forums.contribs.org/index.php?topic=36322.msg168766#msg168766

[deragen]

Thanks worked like a charm.

Learned something new also.

[hamdodger]

I have the exact same issue but in my case, I get this same error message even after doing a 100% clean reinstall of SME Server 7.1.  No amount of yum db rebuilding/recreating/cleaning/etc. appears to be working.

Any ideas?

Again, I am having this same yum update problem from a completely clean install.

[guest22]

@hamdodger

Please consider a bug report. A clean install of 7.1 should work. Please attach any relevant logfiles.

guest