SUMMARY: pkgadd: ERROR: checkinstall script did not complete successfully

From: Dave Zwieback (zwieback_dave@timeplex.com)
Date: Wed Feb 18 1998 - 09:07:49 CST


Original question:

I have a 2.6 box, and I am trying to install some patches on it.
For some reason, I always get:

    pkgadd: ERROR: checkinstall script did not complete successfully

I even tried changing the ownership of the files to nobody:nogroup, and even
tried changing the mode to 777.

---

There were several suggestions. The one that worked was from Casper Dik. I will check the FAQ the next time. :) Here's the answer:

The path leading up to the patches should also be accessible to nobody. Try unpacking in /tmp

The solaris FAQ says:

5.53) Patch installation often fails with "checkinstall" errors.

When installing a patch, the Solaris 2.5+ patch installation procedure will execute the script "checkinstall" with uid nobody.

If any of the patch files cannot be read by nobody or if any part of the path leading up to the patch directory an error similar to the following will appear:

./installpatch . Generating list of files to be patched... Verifying sufficient filesystem capacity (exhaustive method) ... Installing patch packages... pkgadd: ERROR: checkinstall script did not complete successfully ....

You can workaround this in two ways, one is to make sure that nobody can read all patch files and execute a "pwd" in the patch directory or add an account "install" to /etc/passwd:

install:x:0:1:installpatch braindamage:/:/bin/true

Installpatch uses "nobody" as a fallback if it cannot find the "install" user.

--- end of excerpt from the FAQ

Questions marked with a * or + have been changed or added since the FAQ was last posted

The most recently posted version of the FAQ is available from <http://www.wins.uva.nl/pub/solaris/solaris2/>

---

Dave.




This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:31 CDT