On Mon, 11 Oct 2010, Kevin wrote:

Matt Keenan was kind enough to describe his procedure for adding new packages
http://blogs.sun.com/mattman/entry/iso_creation_with_distro_constructor

I followed this guide and tried to create a osol 148 image for sparc platform, 
but
hit a few problems.

1. If I tried to create an AI sparc image with version osol 148, what OS 
version should I adopt for the build server? because I sometimes found the pkg 
command
version is conflict with exception 'pkg.client.api_errors.VersionException', so
I manually changed CLIENT_API_VERSION in /usr/bin/pkg, but I know this is
not a better way.

Ideally your build machine should match the version of the
image you're creating. So, if you're trying to create a
build 148 image, you'd want your build machine to be running
148.

2  For Step 4 'Create your own slim install packages', is it necessary for 
sparc platform?

Yes, you'd need to build the slim install packages on a sparc
machine. That is assuming that you are infact making changes
to the caiman code. See more on this below ..

3. For step 5 'Import packages to local repo', I need modify 
~/gate/src/util/distro-import/Makefile, right?
   but what's the correct value for the following variables in Makefile.

   WOS_PKGS: the default value specified an non-existed directory for BUILDID 
148
   NONWOS_PKGS: where should I point it to?
   TEST_PKGS: If I changed 2 packages, how to set it.

   I have set the REPO variable with default value of port 10000, but when I 
issue '$ make 121/redist_import',
   the console message indicated to me that port 20000, 20001, 20002, 20003 can 
not be visited, should I
   use /usr/lib/pkg.depotd to invoke respective service listeners for them? If 
so, what's the command line I should
   run?

   REPO=http://localhost:10000
   ON_REPO=http://localhost:20000
   INSTALL_REPO=http://localhost:20001
   X_REPO=http://localhost:20002
   IPS_REPO=http://localhost:20003
   VPANELS_REPO=http://localhost:20004

   Even though I have run '/usr/lib/pkg.depotd -d /export/ips/repo -p 20000' 
.... and '/usr/lib/pkg.depotd -d /export/ips/repo -p 20004', I still hit the 
following error message, do you know how to resolve it?

======================================
Third pass: dependency id, resolution and publication 2010-09-30 21:26:53.528764
..........
.......
.....
Package 'consolidation/cacao/cacao-incorporation'
Package 'consolidation/ub_javavm/ub_javavm-incorporation'
Package 'consolidation/solaris_re/solaris_re-incorporation'
Package 'entire'
Traceback (most recent call last):
 File "./importer.py", line 1894, in <module>
   main_func()
 File "./importer.py", line 1863, in main_func
   publish_pkg(_p, g_proto_area)
 File "./importer.py", line 579, in publish_pkg
   transaction_id = t.open()
 File 
"/export/home/ips_gate/proto/root_sparc/usr/lib/python2.6/vendor-packages/pkg/publish/transaction.py",
 line 337, in open
   pkg_name=self.pkg_name)
 File 
"/export/home/ips_gate/proto/root_sparc/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py",
 line 399, in wrapper
   return f(instance, *fargs, **f_kwargs)
 File 
"/export/home/ips_gate/proto/root_sparc/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py",
 line 2253, in publish_open
   single_repository=True, operation="open", versions=[0]):
 File 
"/export/home/ips_gate/proto/root_sparc/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py",
 line 1863, in __gen_repo
   "%s/%d" % (operation, versions[-1]))
pkg.client.api_errors.UnsupportedRepositoryOperation: Publisher 'localhost' has 
no repositories that support the 'open/0' operation.
*** Error code 1
make: Fatal error: Command failed for target `redist_import'
Current working directory /export/home/ips_gate/src/util/distro-import
*** Error code 1
make: Fatal error: Command failed for target `148/redist_import'
====================================================================

These questions are probably better directed at pkg-discuss.

4. I noticed that the guide is written on Sep 04, 2009, is there any other 
newer update for it? such as for osol 148, but at least after osol 144.

A more recent copy of the official Distribution Constructor guide
is at:

http://dlc.sun.com/osol/docs/content/dev/DistroConst/distro_const.html

5. What is wos packages and nonwos packages? My nightly build is based on 148 
source code.
   /net/fogbroom.prc/bjroot/users/kevin/mpxio/6969682/ws_148
   the package information is quite different than before ( I mean compared 
with Nevada')

So many questions, but your quick response is much appreciated, I was stuck 
here for a few days and can not address the issue.

It appears to me that you are trying to build an AI sparc
media in order to test some of your ON changes. Is that
correct?

If so, you're better off, at a high level, with:

a) Standing up an IPS repo just with your ON changes

b) Specifying that repo as an additional publisher
   in your AI DC manifest

c) If you're also making changes to slim_source, you'd
   need to have the slim install package in an IPS repo
   as well.

Alok
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

Reply via email to