Bug 528131

Summary: Cannot update NetworkManager
Product: [Fedora] Fedora Reporter: Harald Hoyer <harald>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: dcbw
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-07 02:15:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Harald Hoyer 2009-10-09 10:02:41 UTC 
Have NetworkManager-gnome-0.7.1-4.git20090414.fc11.i586 installed..

# yum update ..
Running Transaction
I/O warning : failed to load external entity "/etc/gconf/schemas/nm-applet.schemas"
Failed to open `/etc/gconf/schemas/nm-applet.schemas': No such file or directory
Error in PREIN scriptlet in rpm package 1:NetworkManager-gnome-0.7.996-3.git20090928.fc12.i686
error: %pre(NetworkManager-gnome-1:0.7.996-3.git20090928.fc12.i686) scriptlet failed, exit status 1
error:   install: %pre scriptlet failed (2), skipping NetworkManager-gnome-1:0.7.996-3.git20090928.fc12
1:NetworkManager-gnome-0.7.1-4.git20090414.fc11.i586 was supposed to be removed but is not!

Failed:
  NetworkManager-gnome.i686 1:0.7.996-3.git20090928.fc12                                                                                                                                             

Complete!
Comment 1 Harald Hoyer 2009-10-13 13:29:17 UTC 
Old NetworkManager packages did not have /etc/gconf/schemas/nm-applet.schemas so the %pre script of the new packages fails.
Comment 2 Dan Williams 2009-10-13 18:41:51 UTC 
Grr.  So what should the scriptlet be to just ignore errors from the schemas command?

In -4 I added " || :" to the end of the gconftool-2 lines in perhaps a misguided attempt to just ignore the exit status of the command.  I guess I could do "|| exit 0" instead or something to ensure the shell thinks it always succeeds?
Comment 3 Harald Hoyer 2009-10-14 08:06:36 UTC 
IIRC, these pre/post-scripts exit on any failed command ("set -e")
Comment 4 Dan Williams 2009-11-07 02:15:02 UTC 

*** This bug has been marked as a duplicate of bug 526519 ***