On Wed, Jul 21, 2010 at 02:53:32PM -0700, Dan Mick wrote: > On 07/21/10 02:47 PM, Jose wrote: > >On 07/21/10 02:37 PM, Mark J. Nelson wrote: > >>On 07/21/10 03:30 PM, Will Fiveash wrote: > >>>On Wed, Jul 21, 2010 at 02:53:53PM -0600, Mark J. Nelson wrote: > >>>>What does pkg publisher report? The ports in question (13005 and 13006) > >>>>look like maybe they were configured manually at some point in the > >>>>past? > >>>>The onu script, unless you tell it via command line or env variable, > >>>>will use 13001 and 13000. > >>> > >>>I'm confused. I still need to run pkg.depotd on my build system when > >>>using onu -d /net-path-to-nightly-depot? If that's the case then why > >>>have the -d flag? > >>> > >> > >>Because onu has not been updated to work directly with file-based > >>repositories. > >> > >>The -d option tells it where to find the repositories, but it still > >>needs to access those repositories by way of a pkg.depotd server. > > > >Okay I'm confused too now. I don't run pkg.depotd and I can onu. > > People should probably read onu once or twice. onu runs pkg.depotd.
Then why did it blow up when I first ran it with -d? Now I realize that a while back I had set the publishers to point to pkg.depotd running on non-default ports on my build system which I had forgotten about and where not running at the time I tried onu -d but is it wrong to expect onu to deal with this and update the pkg publishing so it points to pkg.depotd running locally on the system that onu is also running on? -- Will Fiveash Oracle Austin, TX, USA Internal Solaris Kerberos/GSS/SASL website: http://kerberos.sfbay.sun.com http://opensolaris.org/os/project/kerberos/ Note my new work e-mail address: will.five...@oracle.com _______________________________________________ on-discuss mailing list on-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/on-discuss