Bug 389989

Summary: Subprocces fail during nscd upgrade
Product: [openSUSE] openSUSE 11.0 Reporter: Mark Stopka <mstopka>
Component: Update ProblemsAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Minor    
Priority: P5 - None    
Version: Factory   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Mark Stopka 2008-05-13 21:53:34 UTC
Hi. I have Factory on my box and i have a problem with zypper up -t package command because upgrade of nscd failing. This is related part of zypper output.

That upgraded and REMOVED parts are weird... (nscd is in both parts)

mantisha:/home/marek/data/Video/the-big-bang-theory # zypper up -t package
Reading installed packages...

The following packages are going to be upgraded:
  wxGTK virtualbox-ose-kmp-pae nscd kernel-syms kernel-source kernel-pae


The following package is going to be REMOVED:
  nscd


Overall download size: 79,3 M. After the operation, 82,0 K will be freed.
Continue? [YES/no]: yes
Downloading package wxGTK-2.8.7.1-16.i586, 3,5 M (12,3 M unpacked)
Downloading: wxGTK-2.8.7.1-16.i586.rpm [done (897,1 K/s)]
Installing: wxGTK-2.8.7.1-16 [done]
Downloading package nscd-2.8-11.i586, 62,0 K (123,0 K unpacked)
Downloading: nscd-2.8-11.i586.rpm [done]
Installing: nscd-2.8-11 [done]
Installation of nscd-2.8-11 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM selhalo: 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


Abort, retry, ignore? [A/r/i]: i
Downloading package kernel-source-2.6.25.3-2.i586, 53,0 M (262,5 M unpacked)
Downloading: kernel-source-2.6.25.3-2.i586.rpm [done (1,1 M/s)]
Installing: kernel-source-2.6.25.3-2 [100%]  


And question... Should i report this kind of problem in openSUSE Factory, or only in releases like 10.3 is?
Comment 1 Stephan Kulow 2008-05-14 07:19:33 UTC
you need to insserv boot.getclock and insserv boot.setclock

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