[Bug 384254] New: nscd: error in %post
https://bugzilla.novell.com/show_bug.cgi?id=384254 Summary: nscd: error in %post Product: openSUSE 11.0 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: pbaudis@novell.com ReportedBy: thoenig@novell.com QAContact: qa@suse.de Found By: --- Just saw that when updating my workstation: * Installing: nscd-2.8-8 Installation of nscd-2.8-8 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: insserv: Service boot.clock has to be enabled for service nscd insserv: exiting now! error: %post(nscd-2.8-8.x86_64) scriptlet failed, exit status 1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=384254
User andreas.hanke@gmx-topmail.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c1
Andreas Hanke
https://bugzilla.novell.com/show_bug.cgi?id=384254
User captain.magnus@opensuse.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c2
--- Comment #2 from Magnus Boman
https://bugzilla.novell.com/show_bug.cgi?id=384254
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c3
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c4
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c5
Stefan Hundhammer
https://bugzilla.novell.com/show_bug.cgi?id=384254
User captain.magnus@opensuse.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c6
Magnus Boman
https://bugzilla.novell.com/show_bug.cgi?id=384254
User andreas.hanke@gmx-topmail.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c7
Andreas Hanke
https://bugzilla.novell.com/show_bug.cgi?id=384254
User andreas.hanke@gmx-topmail.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c8
--- Comment #8 from Andreas Hanke
https://bugzilla.novell.com/show_bug.cgi?id=384254
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c9
--- Comment #9 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=384254
User andreas.hanke@gmx-topmail.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c10
Andreas Hanke
https://bugzilla.novell.com/show_bug.cgi?id=384254
User captain.magnus@opensuse.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c11
Magnus Boman
https://bugzilla.novell.com/show_bug.cgi?id=384254
User pczanik@genesi-usa.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c12
peter czanik
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c13
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User pczanik@genesi-usa.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c14
--- Comment #14 from peter czanik
https://bugzilla.novell.com/show_bug.cgi?id=384254
User captain.magnus@opensuse.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c15
Magnus Boman
https://bugzilla.novell.com/show_bug.cgi?id=384254
User captain.magnus@opensuse.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c16
Magnus Boman
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c17
--- Comment #17 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User jpr@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c18
--- Comment #18 from JP Rosevear
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c19
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c20
--- Comment #20 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c21
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User jpr@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c22
--- Comment #22 from JP Rosevear
You have not used YaST nor zypper otherwise the *new* insserv would cry but *never* exit. Beside this after installing the *new* insserv and after this installing the *new* aaa_base the script /etc/init.d/boot.setclock should be linked into the directory /etc/init.d/boot.d/ ...
I used zypper. jpr@gambit:~> sudo zypper install -f nscd Reading installed packages... The following package is going to be reinstalled: 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/?]: y Downloading package nscd-2.8-9.i586, 62.0 K (123.0 K unpacked) Downloading: nscd-2.8-9.i586.rpm [done] Installing: nscd-2.8-9 [done] Installation of nscd-2.8-9 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: failed to stat /var/lib/gdm/.gvfs: Permission denied insserv: Service boot.setclock has to be enabled for service nscd insserv: exiting now! error: %post(nscd-2.8-9.i586) scriptlet failed, exit status 1 Abort, retry, ignore? [A/r/i]: -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=384254
User jpr@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c23
JP Rosevear
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c24
--- Comment #24 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c25
--- Comment #25 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c26
--- Comment #26 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c27
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User mrueckert@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c28
--- Comment #28 from Marcus Rückert
https://bugzilla.novell.com/show_bug.cgi?id=384254
User jpr@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c29
--- Comment #29 from JP Rosevear
Question: which init/boot scripts had'nt been enabeld during the first update?
boot.setclock is not enabled jpr@gambit:/etc/init.d/boot.d> ls *clock* ls: cannot access *clock*: No such file or directory The aaa_base setup seems to rely on $YAST_IS_RUNNING to setup up everything correctly as well. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c30
--- Comment #30 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User jpr@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c31
JP Rosevear
That is not fully correct as *all* setup scripts rely on the variable YAST_IS_RUNNING as this variable is used for the insserv and fillup rpm macros, just do `grep -rs YAST_IS_RUNNING /usr/lib/rpm/' ... this will e.g. enforce the usage of the option -f for insserv to ignore errors. This straightened the dependcy problem of(currently) not existing and therefore not enabled boot/init scripts during a full update.
Otherwise all package must be installed in the order of the boot/init script dependcies ... nevertheless if on an update this order change you would also run into the same problem if an old but currently installed package violate a new dependcy found in a new package.
In this case, wouldn't a PreReq be the right way to go? Anyhow, poke me for access to my machine on IM or IRC -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=384254
User captain.magnus@opensuse.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c32
--- Comment #32 from Magnus Boman
https://bugzilla.novell.com/show_bug.cgi?id=384254
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c33
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c34
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c35
Ján Kupec
Do we run into trouble if we set YAST_IS_RUNNING to "instsys" for the
Yes:
`zypper dup' command? In other words does zypper execute the rpm setup scripts (%pre, %post, %preun, %postun, and any %trigger) as YasT does is on update case? Compare with the rpm macros found in
No, zypper does not do any of this nor does it any other additional work yast does when this variable is used. This is most probably not easily doable (but may be wanted in the future - a FATE request?) OTOH package scripts should be able to function also without such variable, see below.
On the other hand, does zypper and/or libzypper use own environment variables in case of `dup' which could be checked by insserv?
No, zypper/libzypp just calls rpm, it does not set any env variables. You can think of this situation like running the update with plain rpm (look at zypper.log to see how exactly was rpm invoked for each package) on a running system. If it fails like said in this report (it should), it should be fixed to work with plain rpm. Then it will work with zypper, too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=384254
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c36
Ján Kupec
This is getting boring :-/ Everytime I do a zypper dup I get this error And it keeps installing a new version of nscd instead of upgrading;
mblxsrv01:/home/mboman # rpm -q nscd nscd-2.8-6 nscd-2.8-8 nscd-2.8-9 nscd-2.8-11
Now this is something interesting :O) We've been wondering how this happens for some time now. Can you please create a new report, assign to zypp-maintainers and attach zypper.log + solver test case? Thanx. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=384254
User captain.magnus@opensuse.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c37
--- Comment #37 from Magnus Boman
https://bugzilla.novell.com/show_bug.cgi?id=384254
User captain.magnus@opensuse.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c38
Magnus Boman
https://bugzilla.novell.com/show_bug.cgi?id=384254
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c39
--- Comment #39 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=384254
User mls@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c40
Michael Schröder
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c41
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User jpr@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c42
--- Comment #42 from JP Rosevear
(In reply to comment #32 from Magnus Boman)
This is getting boring :-/ Everytime I do a zypper dup I get this error. And it keeps installing a new version of nscd instead of upgrading;
mblxsrv01:/home/mboman # rpm -q nscd nscd-2.8-6 nscd-2.8-8 nscd-2.8-9 nscd-2.8-11
Now this is something interesting :O) We've been wondering how this happens for some time now. Can you please create a new report, assign to zypp-maintainers and attach zypper.log + solver test case? Thanx.
I have this on my machine now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=384254
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c43
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=384254
User jpr@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c44
--- Comment #44 from JP Rosevear
https://bugzilla.novell.com/show_bug.cgi?id=384254
User jpr@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c45
--- Comment #45 from JP Rosevear
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c46
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User jpr@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c47
--- Comment #47 from JP Rosevear
https://bugzilla.novell.com/show_bug.cgi?id=384254
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c48
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c49
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User kkaempf@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c50
Klaus Kämpf
That is not fully correct as *all* setup scripts rely on the variable YAST_IS_RUNNING as this variable is used for the insserv and fillup rpm macros, just do `grep -rs YAST_IS_RUNNING /usr/lib/rpm/' ... this will e.g. enforce the usage of the option -f for insserv to ignore errors. This straightened the dependcy problem of(currently) not existing and therefore not enabled boot/init scripts during a full update.
Something to fix in the future.
Otherwise all package must be installed in the order of the boot/init script dependencies ... nevertheless if on an update this order change you would also run into the same problem if an old but currently installed package violate a new dependency found in a new package.
I'd strongly recommend to add proper PreRequires so the correct install/update order can be computed with RPM rules. Moving this request to FATE now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=384254
User kkaempf@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c51
--- Comment #51 from Klaus Kämpf
If not the variable YAST_IS_RUNNING should be set to "instsys" if zypper is used in dup mode. Otherwise we badly need an other environment variable, like INSSERVOPTS with the value "force".
Werner, how is this supposed to work when just RPM is used from the command line to install/update a package ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=384254
User kkaempf@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c52
--- Comment #52 from Klaus Kämpf
Even if `zypper dup' would install all packages in the order of the required boot/init script order this would not help if the order boot/init scripts of the current installed rpm packages will change during an update.
This sounds as if the current insserv dependency resolution cannot work with RPM.
This was *one* of the reasons *why* the variable YAST_IS_RUNNING enforce the option -f for insserv.
This environment is not available when just using RPM on the command line.
We have to find a way to enable insserv to know when it should ignore dependency error during (e.g. for `zypper dup' or `yast update').
What about "rpm -i" and "rpm -U" ?
It is a major feature for insserv to throw an error on a dependency error for a single rpm package (only).
IMHO, running insserv from within rpm (pre/post scripts) should only warn but not fail. Running insserv from the command line should error out in case of unfulfilled innserv dependency. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=384254
Klaus Kämpf
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c53
--- Comment #53 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User aj@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c54
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=384254
User holler@nefkom.info added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c55
Hans-Peter Holler
https://bugzilla.novell.com/show_bug.cgi?id=384254
Hans-Peter Holler
https://bugzilla.novell.com/show_bug.cgi?id=384254
User holler@nefkom.info added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c56
Hans-Peter Holler
https://bugzilla.novell.com/show_bug.cgi?id=384254
User holler@nefkom.info added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c57
Hans-Peter Holler
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c58
--- Comment #58 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User harbrink@bluewin.ch added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c59
--- Comment #59 from Eberhard Harbrink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c60
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c61
--- Comment #61 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c62
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c63
--- Comment #63 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=384254
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c64
--- Comment #64 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c65
--- Comment #65 from Dr. Werner Fink
From the log of aaa_base just submitted:
Mon May 19 17:52:34 CEST 2008 - Move udev from the Required to the PreRequired list (bnc#384254) - Rename boot.setclock to boot.clock but preserve boot.getclock this avoid to get temporary boot.clock provided twice during update (bnc#384254) just tested with command lines from comment #64 and it works flawless together with the new insserv including change from attachment #215606 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=384254
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c66
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=384254
User pbaudis@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c67
Petr Baudis
https://bugzilla.novell.com/show_bug.cgi?id=384254
User pbaudis@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c68
--- Comment #68 from Petr Baudis
https://bugzilla.novell.com/show_bug.cgi?id=384254
User pbaudis@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c69
Petr Baudis
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c70
--- Comment #70 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c71
--- Comment #71 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=384254
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c72
--- Comment #72 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=384254
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c73
--- Comment #73 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c74
--- Comment #74 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c75
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User ro@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c76
Ruediger Oertel
https://bugzilla.novell.com/show_bug.cgi?id=384254
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c77
--- Comment #77 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=384254
User ma@sernet.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c78
--- Comment #78 from Michael Adam
I still think Bug 393799 is a different issue
I think so, too. just reopened that bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=384254
User ma@sernet.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c79
--- Comment #79 from Michael Adam
If /etc/init.d/boot.clock or /etc/init.d/boot.setclock is missed then the bug is driver by the same behaviour of insserv: by default it does not igmore errors anymore. The current insserv from factory tries to determine if the script used for execution (the parent) is executed by rpm it ignores know errors (hopefully temorary errors). Next is that aaa_base from factory now uses /etc/init.d/boot.clock again, no /etc/init.d/boot.setclock, but /etc/init.d/boot.getclock. This should avoid that during an update there exists temporary two scripts providing both boot.clock in the LSB header. Nevertheless if the error once happened it can only be repaired with a) updating both insserv and aaa_base from factory *and* b) executing the command line
insserv boot.clock
by hand. This because the rpm post install script assumes that if the start link for boot.clock is missed the user had removed this link and therefore no new link is required.
These instructions were not enough for me to stop zypper from failing to install nscd: I had to uninstall nscd (all installed versions) and then re-install. That worked, though. Michael -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c80
--- Comment #80 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c81
--- Comment #81 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User ma@sernet.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c82
--- Comment #82 from Michael Adam
https://bugzilla.novell.com/show_bug.cgi?id=384254
User ma@sernet.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c83
--- Comment #83 from Michael Adam
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c84
--- Comment #84 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User stbinner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c85
Stephan Binner
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c86
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User pbaudis@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c87
--- Comment #87 from Petr Baudis
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c88
--- Comment #88 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c89
Dr. Werner Fink
participants (1)
-
bugzilla_noreply@novell.com