Copying and Creating Package Repositories in Oracle® Solaris 11.2

Exit Print View

Updated: September 2014

Troubleshooting Local Package Repositories

The following methods can prevent problems or help find the cause of problems you might encounter:

  • Verify repository source files. If you use .zip files to create your repository, confirm that the files on your system are correct by using the checksums as described in How to Copy a Repository From a zip File.

  • Verify the installed repository. Use the pkgrepo verify command to check your installed repository.

    The following permissions problems are reported by pkgrepo verify:

    • File permissions. To avoid problems with directory and file permissions for file system based repositories, ensure that the pkg5srv user has permission to read the repository.

    • Directory permissions. Ensure that all directories in the repository have execute permission.

    If the pkgrepo verify command reports other types of errors, try using the pkgrepo fix command to fix the errors. See the pkgrepo (1) man page for more information.

  • Check your publisher origin. Make sure you set the origin for each publisher appropriately in each image. To update installed packages, install packages that depend on installed packages, or install a non-global zone, the repository that you set as the publisher origin must contain at least the same software that is installed in the image where you are setting the publisher. See Step 3 in How to Enable Users to Retrieve Packages Using a File Interface. See Adding and Updating Software in Oracle Solaris 11.2 for information about setting publishers and troubleshooting package installation problems.

  • Check web server configuration. If you configure an Apache web server to access your repository, configure the web server to not decode encoded forward slashes. See the instructions in Required Apache Configuration Setting. Decoding encoded forward slashes can result in “package not found” errors.

  • Do not create a repository that is only accessible from a non-global zone. All locations of publishers configured in non-global zones must be accessible from the global zone even if that publisher is not configured in the global zone.