Solaris / OpenSolaris package management
James Turnbull
Hash: SHA1
Hi all
I'm looking for Puppet users on Solaris - I've been setting up some
test EC2 instances and using the sun package provider to install
some OpenSolaris packages. I get the following error:
err: //git/Package[git]/ensure: change from absent to present
failed: Execution of '/usr/sbin/pkgadd -d
http://pkg.opensolaris.org/ -n SUNWgit' returned 1: pkgadd: ERROR:
Failure occurred with http(s) negotiation: <'Peername' doesn't match
'host' or no matching entry>
pkgadd: ERROR: unable to download package datastream from
<http://pkg.opensolaris.org/>.
My manifests looks like:
Package { source => "http://pkg.opensolaris.org/" }
package { "SUNWgit":
ensure => installed,
}
I've Google'd around a bit and can't seem to find an answer to this
error. I get the same error running pkgadd manually on the host too.
When I use the pkg tool (pkg install SUNWgit) it works fine.
Does anyone have any ideas?
On a related note is pkgadd the recommended way to manage packages?
Should a new/updated provider be developed that uses pkg?
Thanks
James Turnbull
- --
Author of:
* Pro Linux System Administration (http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet (http://tinyurl.com/pupbook)
* Pro Nagios 2.0 (http://tinyurl.com/pronagios)
* Hardening Linux (http://tinyurl.com/hardeninglinux)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEVAwUBS1LDQSFa/lDkFHAyAQKUngf+Kn6nBIUh+aNufwPCyACqMpFQmJSW5DiG
iUiHAxV54iQz+xmnIO1W8Z1j3wDTk9A9IGPXCzGYKBaHhlnQ/r8jtv4frfrvU14J
RPcVqxJmxkVAAoyZ6lKw5MrdXCA3WWB9mxU03HB/Imp7XiuC88t2NRAF7SRrZiHQ
KG/j0WymRdwuQzvG7k8XOcXAhg74UV/ctRS0ugoaCTGDxe92EFCesI4+56leaBOB
JsDGOGn8m+Ne9OPwg5yWL5F+cAkKHlx2qvkalJ7O+4ZhgledjxTou5aTxxMnBSe3
q7/RY5UbyEXxK8D/xijwkPAdoc6lh+rAZ0UIcke0wX+7O+RI4KlSnA==
=Snrd
-----END PGP SIGNATURE-----
Martin Englund
On Jan 17, 8:58 am, James Turnbull <ja...@lovedthanlost.net> wrote:
> err: //git/Package[git]/ensure: change from absent to present
> failed: Execution of '/usr/sbin/pkgadd -dhttp://pkg.opensolaris.org/-n SUNWgit' returned 1: pkgadd: ERROR:
> Failure occurred with http(s) negotiation: <'Peername' doesn't match
> 'host' or no matching entry>
> pkgadd: ERROR: unable to download package datastream from
> <http://pkg.opensolaris.org/>.
>
> My manifests looks like:
>
> Package { source => "http://pkg.opensolaris.org/" }
>
> package { "SUNWgit":
> ensure => installed,
>
> }
>
That package source is only valid for use with pkg.
> I've Google'd around a bit and can't seem to find an answer to this
> error. I get the same error running pkgadd manually on the host too.
>
You can use pkgadd on OpenSolaris, but it is there for backward
compatibility.
> When I use the pkg tool (pkg install SUNWgit) it works fine.
>
> Does anyone have any ideas?
>
I noticed that you found the pkg(5) package provider which hopefully
will work for you - it is my first shot at a package provider for
puppet :)
> On a related note is pkgadd the recommended way to manage packages?
> Should a new/updated provider be developed that uses pkg?
>
On OpenSolaris you should stick to pkg instead of pkgadd/pkgrm (unless
you only have a package which only is available in SVR4 format).
cheers,
/Martin
James Turnbull
Hash: SHA1
On 17/01/10 10:40 PM, Martin Englund wrote:
> I noticed that you found the pkg(5) package provider which hopefully
> will work for you - it is my first shot at a package provider for
> puppet :)
>
Yes - I added some basic (not sufficient) tests to your provider and
botched a send to the -dev list. :)
Hopefully that'll push it's inclusion along for Rowlf.
Thanks for producing it.
Regards
James Turnbull
- --
Author of:
* Pro Linux System Administration (http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet (http://tinyurl.com/pupbook)
* Pro Nagios 2.0 (http://tinyurl.com/pronagios)
* Hardening Linux (http://tinyurl.com/hardeninglinux)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEVAwUBS1L3/CFa/lDkFHAyAQKSjgf+OKC1+cRXS1bcJjlk02oz4QlZCtp6+GtY
wYS3yL/+lQz2Y8gXjVBfv9mpHTg7B1bNfuhZLfeW39dFQ9zUd0ItAIDXcw45ePiJ
BxWaaXP+gq0K/4MMSNQn2lZ1/rj9Nt037o2Hxk52OuMwLqE91W6QueBu89SL5Cfz
GAAYStyim0xnRCy1STgeazkZ89G25Dxt/pRqAYysi2wXkCa98n71qmYtcct+5zgG
Z83Fhev3lYRSiV5BzRUH4hUXT+pBxRdSuQmrFO96IBhL1hwNWLj7OcCCMBfml1Us
2NKKQknqag4GmDdQIEO7UpWjJxwGbBLzSER2soKyVWBs0yJl3+VUug==
=9tGM
-----END PGP SIGNATURE-----
Alan Barrett
> My manifests looks like:
>
> Package { source => "http://pkg.opensolaris.org/" }
>
> package { "SUNWgit":
> ensure => installed,
> }
The "sun" package provider needs the "source" parameter to be a a
filename or an URL to the individual package, not an URL to a collection
of many packages. I have been using the "blastwave" provider, with a
custom config file that points to a private package repository.
--apb (Alan Barrett)
deet
>
> I noticed that you found the pkg(5) package provider which hopefully
> will work for you - it is my first shot at a package provider for
> puppet :)
>
Martin.
Will your new provider show up as part of one of the upcoming puppet
releases? I've been noodling around with moving my Solaris boxes to
use the Solaris port of pkg (http://wikis.sun.com/display/
IpsBestPractices/Multi-platform+Packaging+for+Layered+Distros) for all
of our software that is not part of the Solaris release itself.
Knowing that the "pkg" provider would be coming down the road would
eliminate the biggest roadblock for moving to ips/pkg.
Thanks. Derek.
James Turnbull
> Will your new provider show up as part of one of the upcoming puppet
> releases? I've been noodling around with moving my Solaris boxes to
> use the Solaris port of pkg (http://wikis.sun.com/display/
> IpsBestPractices/Multi-platform+Packaging+for+Layered+Distros) for all
> of our software that is not part of the Solaris release itself.
> Knowing that the "pkg" provider would be coming down the road would
> eliminate the biggest roadblock for moving to ips/pkg.
Derek
It'll hopefully go into the next feature release - I've just pushed
the code and some initial tests to the -dev list. Additional tests
would help.
Regards
James Turnbull