Bug 393475

Summary: zypper fails to install nscd but yast2 does not
Product: [openSUSE] openSUSE 11.0 Reporter: Dave Plater <davejplater>
Component: libzyppAssignee: E-mail List <zypp-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Factory   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: zypper.log

Description Dave Plater 2008-05-22 09:25:21 UTC
Arbuthnot:/home/davepl/Documents # zypper in nscd
Reading installed packages...

The following package is going to be upgraded:
  nscd


The following package is going to be REMOVED:
  nscd


Overall download size: 62.0 K. After the operation, 123.0 K will be freed.
Continue? [Y/n/p/?]:
Downloading package nscd-2.8-12.i586, 62.0 K (123.0 K unpacked)
Downloading: nscd-2.8-12.i586.rpm [done (8.8 K/s)]
Installing: nscd-2.8-12 [error]
Installation of nscd-2.8-12 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: insserv: Service boot.setclock has to be enabled for service nscd
insserv: exiting now!
error: %post(nscd-2.8-12.i586) scriptlet failed, exit status 1


Abort, retry, ignore? [A/r/i]: r
Installing: nscd-2.8-12 [error]
Installation of nscd-2.8-12 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: insserv: Service boot.setclock has to be enabled for service nscd
insserv: exiting now!
error: %post(nscd-2.8-12.i586) scriptlet failed, exit status 1


Abort, retry, ignore? [A/r/i]: i
I have tried with two versions of nscd, after I enabled boot.setclock with runlevel editor zypper says that nscd is up to date. Yast2 software management does not have any problem and doesn't enable boot.setclock either. I have disabled boot.setclock again as I have had enough ntp problems to date.
Comment 1 Dave Plater 2008-05-22 09:36:34 UTC
Created attachment 217479 [details]
zypper.log
Comment 2 Stephan Kulow 2008-05-22 09:49:17 UTC

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