Bug 528131 - Cannot update NetworkManager
Summary: Cannot update NetworkManager
Keywords:
Status: CLOSED DUPLICATE of bug 526519
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-09 10:02 UTC by Harald Hoyer
Modified: 2009-11-07 02:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-07 02:15:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.