Topic: SME 8 Update Issue (Solved)

[ttech]

Hi
I went to update my system and I received the following dependency error...

e-smith-backup-2.2.0-88.el5.sme.noarch from smeupdates has depsolving problems
  -->missing dependency: nfs-utils is needed by package e-smith-backup-2.2.0-88.el5.sme.noarch ....
  You could try using --skip-broken to work around this problkem
  You could try running: package cleanup --problems
                                package cleanup --dupes
                                rpm -Va --nofiles --nodigest...
and so on.

A quick search brought me to several bugs, the closest being 8788 [comment 11], but none of these were quite the same issue as encountering this during a software update using server manager (I thought I had kept the server up to date).
I tried resetting the repo list per comment 13 in 8788 but the issue remains.
I did not run the suggested workarounds (above) as it appeared that this did not solve the problem in some of the other older bugs (I lost track somewhere following the 'mark as duplicate' chain of bug comments)

Have I missed something obvious or is this a new issue? (BTW - I'm not a guru...)
The system is online so I didn't want to update with this error w/o more information.
Thanks in advance for any help!

[Daniel B.]

Bugs and potential bugs should be reported to the bugtracker. Your issue seems to be that base and updates repo are disabled

[Daniel B.]

See this for how to reset repo to the default (working) set: http://wiki.contribs.org/Useful_Commands#Restoring_Default_Yum_Repositories

[ttech]

Almost completely done, but for a follow up question!

Thanks for your help Daniel!  The 'useful commands' link did the trick.  BUT it is what I did before (see comment 13 for bug 8788), and it didn't work that time.  This time I also added ...   

               signal-event yum-modify

I didn't do that the first time as it wasn't mentioned in the bug comment.  Is this the difference?

[janet]

ttech

..... BUT it is what I did before (see comment 13 for bug 8788), and it didn't work that time.  This time I also added ...   
signal-event yum-modify
I didn't do that the first time as it wasn't mentioned in the bug comment. 

Is this the difference?

Most probably.
The changes you made before will not take effect until you issue
signal-event yum-modify
or
alternatively (& especially if in doubt), you should always issue
signal-event post-upgrade
signal-event reboot

The latter commands will cover all possible changes you can make to the system with db commnds & custom templates etc, so they or a reduced command set, should always be issued after making changes.

[ttech]

Thanks Janet & Daniel.  I was just curious.  Marking as solved.