[bug-notifications] [syslog_ng 0003869]: syslog_ng package can no longer be installed on Solaris 8 or 9

[Mantis Bug Tracker]

The following issue has been CLOSED 
====================================================================== 
http://www.opencsw.org/bugtrack/view.php?id=3869 
====================================================================== 
Reported By:                tim
Assigned To:                maciej
====================================================================== 
Project:                    syslog_ng
Issue ID:                   3869
Category:                   packaging
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-08-25 11:39 CEST
Last Modified:              2009-10-11 09:24 CEST
====================================================================== 
Summary:                    syslog_ng package can no longer be installed on
Solaris 8 or 9
Description: 
I was able to install the CSWsyslogng package on Solaris 8 or 9 machines
just recently. However the latest package that's on the mirrors requires
svcadm to install, therefore restricting it to Solaris 10 only:


Do you want to continue with the installation of <CSWsyslogng> [y,n,?] y

Installing syslog_ng - A powerful syslogd replacement as <CSWsyslogng>

## Executing preinstall script.
Disabling svc:/system/system-log:default
/var/sadm/pkg/CSWsyslogng/install/preinstall: svcadm: not found
pkgadd: ERROR: preinstall script did not complete successfully

Installation of <CSWsyslogng> failed.
ERROR: could not add CSWsyslogng.

====================================================================== 

---------------------------------------------------------------------- 
 (0006826) maciej (manager) - 2009-10-11 09:24
 http://www.opencsw.org/bugtrack/view.php?id=3869#c6826 
---------------------------------------------------------------------- 
This issue has been fixed (in 3.0.4,REV=2009.08.30) and released. Closing
this issue.