-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Another question?
I noticed this on that web page: > Note that a content mirror serves only the file/0/ and filelist/0/ > operations to clients: the mirror doesn't know anything about the packages > (or repository) it is serving. The client still relies on the origin server > for metadata and remote search. I began this as a way to allow AI to install OpenSolaris on a fully isolated network (no internet connection.) It sounds from this quote that that isn't goint to work. Is there anything more I can do to create a mirror repo that can server everything, including the meta data? -Kyle On 7/12/2010 5:14 PM, Shawn Walker wrote: > On 07/12/10 02:06 PM, Kyle McDonald wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi all, >> >> I've read through the instructions here: >> >> http://hub.opensolaris.org/bin/view/Project+pkg/Mirroring >> >> But nothing seems to be working as described: >> >>> r...@keymaster:/export# pkgsend -s file:///export/pkg create-repository >>> pkgsend: create-repository: publisher.prefix is required. >>> Invalid repository configuration values were specified using >>> --set-property or required values are missing. Please provide the >>> correct and/or required values using the --set-property option. >>> r...@keymaster:/export# > > This should be: > > pkgsend -s file:///export/pkg create-repository \ > --set-property=publisher.prefix=opensolaris.org > >>> r...@keymaster:/export# /usr/bin/rsync -a >>> pkg-rsync.opensolaris.org::osol_dev_files /export/pkg/file >>> rsync: failed to connect to pkg-rsync.opensolaris.org: Connection >>> refused (146) >>> rsync error: error in socket IO (code 10) at clientserver.c(124) >>> [receiver=3.0.6] >>> r...@keymaster:/export# > > That shouldn't be happening; I'll notify the appropriate individuals. > >> I'm trying this on a machine installed using the b134 AI image so I >> ignored the parts of the instructions starting with "For earlier >> versions of the pkg(5) software..." >> >> Well actually I tried them too, but they didn't work the way the page >> said either. >> >> The page was updated on 06/21/10, so I don't think it's out of date. >> What am I doing wrong? > > Actually, it's out of date, but I've just fixed it. > > Cheers, > -Shawn -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (MingW32) iQEcBAEBAgAGBQJMO7j3AAoJEEADRM+bKN5wI44IALpz+HN8xHBX2QJgAVfE4VLo DkFD817BCjXLoIUAOBcHptCeUEkaU2KDboGiMmWO6jt947CZso+TqKC5dzEYU76E Zom4R1ahpPrNp5jMjER1DhCEl98Mk83qzUPAin7rgDIBuwp4h27kM/Yw6ru3hR8x Mkkm6rjdm11OmHTeqObiabIeCURS3eeBs8hcwJeN/REqIiIR2q/ORnOwCEYcZH6Y 2VgYD0aj913ZQpFx1kI+AeqVi3a9LhCNUJ+HkJsklJwVa/WnGFEgyso/Gz/63d9R ZRNB571zpv+vbkPY/A5TbMvapdiR7tVkYhxDDempQeCaEPGPkh3I5A+v3bnrUdA= =UWWo -----END PGP SIGNATURE----- _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
