search

oracle / solaris-userland

Open Source software in Solaris using gmake based build system to drive building various software components.
Other
157 stars 65 forks source link

setup for solaris-userland fails because host ipkg.us.oracle.com doesn't resolve #11

Open nbriggs opened 2 years ago

nbriggs commented 2 years ago

If you follow the instructions in the README.md, after git cloning the solaris-userland repository

user@hemlock:/scratch/clone/components$ gmake setup
Generating component list...
Generating component dependencies...
building tools...
/usr/gnu/bin/make -C ../tools clean
make[1]: Entering directory '/scratch/clone/tools'
make[1]: Leaving directory '/scratch/clone/tools'
/usr/gnu/bin/make -C ../tools setup
make[1]: Entering directory '/scratch/clone/tools'
make[1]: Leaving directory '/scratch/clone/tools'
Generating pkglint(1) cache from CANONICAL_REPO http://ipkg.us.oracle.com/solaris11/trunk...
pkglint(1) failed, please see /scratch/clone/sparc/logs/naughty-canonical-repo-actions
gmake: *** [Makefile:158: /scratch/clone/sparc/pkglint-cache] Error 2
user@hemlock:/scratch/clone/components$

and looking at the log file:

Lint engine setup...
Error: Unable to create reference image:   Framework error: code: E_COULDNT_RESOLVE_HOST (6) reason: Could not resolve host: ipkg.us.oracle.com
URL: 'http://ipkg.us.oracle.com/solaris11/trunk/versions/0/'

pkglint: Unable to create reference image:   Framework error: code: E_COULDNT_RESOLVE_HOST (6) reason: Could not resolve host: ipkg.us.oracle.com
URL: 'http://ipkg.us.oracle.com/solaris11/trunk/versions/0/'

real        1.8
user        1.3
sys         0.2
TARGET_EXIT_CODE 2

Presumably either the ipkg.us.oracle.com host should be resolvable (and reachable, and serving that content) or there should be instructions on what to change to remove this.

vlmarek commented 2 years ago

Hi, ipkg.us is indeed piece of our internal architecture. This is oversight on my part. I'm currently on vacation so just quick workaround should be

gmake setup CANONICAL_REPO=your_ips_repo

which can be either local path or http path.

Next week back in work I'll try to think how to make the experience smoother.

Thanks for reporting that

nbriggs commented 2 years ago

Thanks, that worked. It would be helpful if the README.md also mentioned what parts of setting up a new publisher are done already by the "gmake setup ..." and what else you should do to make the repo that it builds visible to the pkg system (e.g., set up a publisher name for a local repo and then install a package from there overriding an older Oracle/Solaris package) -- as you can tell, I don't work with Solaris packaging much (in fact not at all with the image packaging; the SYSV stream packages were what I used to build/install).

nbriggs commented 2 years ago

Any more thoughts on this?

nbriggs commented 2 years ago

This is still a problem. Just updated from the solaris-userland git repository and "gmake setup" fails with the same error, and the README.md has not been updated to include the CANONICAL_REPO=... information.