Mantis - texinfo
Viewing Issue Advanced Details
4085 packaging minor sometimes 2009-12-17 13:36 2010-01-13 15:54
maciej  
dam  
normal  
closed  
fixed  
none    
none  
0004085: pkginstall: ERROR: postinstall script did not complete successfully
=> Installing CSWtexinfo-4.13a,REV=2009.11.05
Please see /opt/csw/share/doc/texinfo/license for license information.
Registering existing texinfo-files...

Installation of <CSWtexinfo> was successful.
Registering existing texinfo-files...
pkginstall: ERROR: postinstall script did not complete successfully

I checked inside /var/sadm/pkg/CSWtexinfo/install/ but there is no postinstall script there.

Looking at the source:

#!/bin/sh

BASE=${PKG_INSTALL_ROOT}/opt/csw

echo "Registering existing texinfo-files..."

FILES=`ls $BASE/share/info/*.info $BASE/share/info/*.info-*`

for i in $FILES; do
        /opt/csw/bin/install-info $i $BASE/share/info/dir 2> /dev/null
done

Seems like it assumes it can write to /opt/csw.
Issue History
2009-12-17 13:36 maciej New Issue
2009-12-28 14:20 dam Status new => assigned
2009-12-28 14:20 dam Assigned To => dam
2009-12-28 14:21 dam Note Added: 0007152
2009-12-28 14:27 maciej Note Added: 0007153
2009-12-28 15:19 dam Note Added: 0007154
2009-12-28 15:19 dam Status assigned => feedback
2010-01-13 15:54 dam Note Added: 0007218
2010-01-13 15:54 dam Status feedback => closed
2010-01-13 15:54 dam Resolution open => fixed

Notes
(0007152)
dam   
2009-12-28 14:21   
Yes, it is mandatory to be able to write info/dir. This is the same issue as running "catman -w" which also needs write access. Would you consider this a bug? If yes under what environment?
(0007153)
maciej   
2009-12-28 14:27   
It's a bug in the typical case: a non-global sparse zone which inherits /opt/csw from the global zone. In this case, the script which writes to /opt/csw needs to be run only in the global zone, and all other zones inherit the filesystem.
(0007154)
dam   
2009-12-28 15:19   
New release 4.13a,REV=2009.12.28 in testing/, please verify.
(0007218)
dam   
2010-01-13 15:54   
This error is most certainly fixed, please open another bug if more errors exist.