Bug 391326 - When updating factory to factory, nscd fails: %post... scriptlet failed, exit status 1
Summary: When updating factory to factory, nscd fails: %post... scriptlet failed, exit...
Status: RESOLVED DUPLICATE of bug 384254
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Update Problems (show other bugs)
Version: Factory
Hardware: Other openSUSE 11.0
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-16 13:01 UTC by Carlos Robinson
Modified: 2008-05-16 13:24 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos Robinson 2008-05-16 13:01:57 UTC
Upgrading the weekly factory version, via "zypper dup", I get (for two..three weeks):

Downloading package nscd-2.8-11.i586, 62.0 K (123.0 K unpacked)
Installing: nscd-2.8-11 [error]
Installation of nscd-2.8-11 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: failed to stat /home/cer/.gvfs: Permission denied
insserv: Service boot.setclock has to be enabled for service nscd
insserv: exiting now!
error: %post(nscd-2.8-11.i586) scriptlet failed, exit status 1

Today:

minas-morgul:~ # chkconfig boot.setclock
boot.setclock  off
minas-morgul:~ # chkconfig boot.setclock on

minas-morgul:~ # zypper in -f nscd

Overall download size: 62.0 K. After the operation, 246.0 K will be freed.
Continue? [Y/n/p/?]: 
Downloading package nscd-2.8-11.i586, 62.0 K (123.0 K unpacked)
Installing: nscd-2.8-11 [done]


I have no idea why "boot.setclock" was off, but I doubt that installation of "nscd" should fail. When running "zypper -n dup" overnight it made zypper to abort the update. I think installation should continue even if the service wasn't enabled.
Comment 1 Andreas Jaeger 2008-05-16 13:24:23 UTC

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