[bug-notifications] [openssh 0004670]: installation error

[Mantis Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4670 
====================================================================== 
Reported By:                pfelecan
Assigned To:                yann
====================================================================== 
Project:                    openssh
Issue ID:                   4670
Category:                   packaging
Reproducibility:            have not tried
Severity:                   major
Priority:                   normal
Status:                     feedback
====================================================================== 
Date Submitted:             2011-01-17 13:36 CET
Last Modified:              2011-02-03 21:49 CET
====================================================================== 
Summary:                    installation error
Description: 
Durring an upgrade of a quite ancient system (SPARC) Solaris 10 the
installation fails with the following messages:

=> Installing CSWossh-5.4p1,REV=2010.03.25 (178/238) ...
Please see /opt/csw/share/doc/openssh/license for license information.
Restoring /etc/opt/csw/preserve/CSWossh/moduli
Restoring /etc/opt/csw/preserve/CSWossh/sshd_config

Installing class <cswinitsmf> ...
cp: cannot create /etc/opt/csw/init.d/cswopenssh: No such file or
directory
pkgadd: ERROR: class action script did not complete successfully
ERROR: attribute verification of </etc/opt/csw/init.d/cswopenssh> failed
    pathname does not exist

Installation of <CSWossh> partially failed.

The previous ossh version was 5.3p1,REV=2009.12.16
====================================================================== 

---------------------------------------------------------------------- 
 (0008776) yann (manager) - 2011-02-03 21:49
 https://www.opencsw.org/mantis/view.php?id=4670#c8776 
---------------------------------------------------------------------- 
Can you reproduce this bug with trace mode enabled and post the output ?

You can do this with "pkgadd -v" or "pkgutil --trace".