similar to: 2.7.18 available for Solaris in CSW repo

Hello Timo, from the maintainer of the OpenCSW package I got the below answer. As the newly build package yields another different commit hash (which I cannot find on GitHub too), I would ask, if you are sure that the commit hash-output in 'doveconf -n' is generated correctly? The headline of 'doveconf -n' with the newly build package is # 2.2.25 (68082dc):

Folks, OpenCSW have released Facter 1.6.0 for Solaris - this includes a back port of the patch for issue 7038[1]. It''s been released to the current catalog, but for now you can pick it up at http://buildfarm.opencsw.org/experimental/html#markp Regards, --Mark [1] http://projects.puppetlabs.com/issues/7038 -- You received this message because you are subscribed to the Google Groups

In my experimental area at the moment - http://buildfarm.opencsw.org/experimental.html#markp It''s been submitted to the catalog though. --Mark -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to

Hi Jake, thanks for fixing this. I have installed now the newly built package on my production system and will report, if any more core dumps occur. Regards, Andreas Am 31.08.2016 um 20:19 schrieb Jake Goerzen: > Hi Andreas & Timo, > > > I've found out what is causing the incorrect hash in the built > packages. Our build system use here at OpenCSW has internal git

Puppet 3.2.4 is now available. 3.2.4 addresses two security vulnerabilties discovered in the 3.x series of Puppet. These vulnerabilities have been assigned Mitre CVE numbers CVE-2013-4956 and CVE-2013-4761. All users of Puppet 3.2.3 and earlier are strongly encouraged to upgrade to 3.2.4. For more information on these vulnerabilities, please visit http://puppetlabs.com/security/cve/cve-2013-4761

Hello, I maintain the dovecot package at opencsw.org. The latest release of dovecot verison 2.2.6 has some changes to lib-http which is breaking compiling on Solaris 10 sparc (though x86 builds successfully). Here is part of the compiler output while building: libtool: compile: /opt/SUNWspro/bin/cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-test

Hi all Reference: http://support.zresearch.com/community/documentation/index.php/Gluster_3.1:_Installing_GlusterFS_on_OpenSolaris I have found this guide to be too brief/terse, and have endeavoured to improve it via more of a recipie/howto approach - and possibly misunderstood the intent of the brief directions in the process. Please advise if there are any errors? Once the procedure is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, The migration is done and the new git repos are online. You can browse the repositories as well as find links to the documentation in the Samba wiki at http://gitweb.samba.org/ A few things, such as buildfarm integration, are still underway and will be completed in a few days. cheers, jerry - --

There are a few errors in the R manual about Solaris. 1) Firstly you may know that Sun is now owned by Oracle. 2) "(Recent Sun machines are Opterons (?amd64?) rather than ?x86?, but 32-bit ?x86? executables are the default.) " It's not true to say that recent machines are Opterons rather than x86. Many new Sun machines are based on 64-bit Intel CPUs (often called x64). The

Hi Pawel, > We can not let it die and I volunteer to keep the Sparc alive! > > My SPARCstation pizzaboxes can be ready for action in a day or two. there are three sparc buildbots which are hooked up to lab.llvm.org. They are currently idle because no builders have been scheduled to use them: # gcc54 36G 0.5 GHz TI UltraSparc IIe (Hummingbird) / 1.5 GB RAM / Sun Netra T1 200 /

Hi, dovecot 2.0.3 After closing the imap(s) connection dovecot crashes: imap-login: Info: Aborted login (no auth attempts): rip=... lip=... mpid=0 master: Error: service(imap-login): child 18636 killed with signal 11 (core not dumped - set service imap-login { drop_priv_before_exec=yes }) master: Warning: Killed with signal 15 (by pid=18643 uid=0 code=kill) It also happens if I only telnet

Chris, > FYI, I completely agree that we shouldn't remove the sparc target. However, it is currently unmaintained, and has some pretty glaring bugs. Is anyone interested in stepping up to maintain the target? > > -Chris We can not let it die and I volunteer to keep the Sparc alive! My SPARCstation pizzaboxes can be ready for action in a day or two. Pawel Wodnicki > On Oct

Hi! I am using mainly Samba 3.5 on CentOS, and I was very pleased with idmap_rid backend for SID-to-RID mappings. But on Solaris 10, I can only use 3.6 because OpenCSW ships only 3.6. Problem is, things are changed and are not working as expected... Here is my config on RHEL Samba 3.5: [global] workgroup = WINDOMAIN realm = WINDOMAIN.LOCAL server string = localserver

USING: rsync version 3.0.6 protocol version 30 on a Sun Solaris 10 x86. This is a precompiled version from opencsw. /opt/csw/bin/rsync -n -axzH -v --delete-after --log-file=$RSYNCOUTPUT/export_-${DAILYDT}X --rsync-path=/opt/csw/bin/rsync -e "ssh -i /root/.ssh/id_hertz" --max-delete=100 /export/.zfs/snapshot/$DAILYDT/ hertz3:/zvol/backup/gauss/export When I added the

Hello, We are using Samba 3.4.6 (packaged by opencsw.org) against Active Directory 2003 on our primary University filestore. The operating system is Solaris 10 Update 10. We have a number of domain controllers. For the past two days on our main filestore has been failing connections from a number of clients. When using smbclient (or indeed any client) connecting to the Samba server we see logs

Hi, We are experiencing a problem with Samba 3.6.4 on Solaris 10 update 10. This problem has only recently started since an upgrade to v3.6.3 and was still present after rebuilding to 3.6.4. We are using the version of samba packaged by OpenCSW. >From a client perspective, the issue is manifested as intermittent very poor performance or intermittent inability to save a file to the share at

On Tuesday 06 April 2010 14:47:37 Dustin Laurence wrote: > On 04/06/2010 12:38 PM, David Greene wrote: > > ...Either this or > > virtualization would work but both are complicated to set up, raising the > > bar to participate. > > Is it? I don't really know anything about it, but on a whim read just > enough to know the name of the user-space manager program I

There''s a problem installing puppet on Solaris 10 -- in this situation, we aren''t really doing anything with puppet there. The version we''re using is: ruby 1.8.7 (2011-02-18 patchlevel 334) [i386-solaris2.9] Here''s the first error: # gem update puppet > > Updating installed gems > > Updating puppet > > Building native extensions. This

Hello, can anyone comment on how well these ups work with NUT and which is the preferred driver? I haven't found much information in the mailing list, seems blazer_usb, nutdrv_qx etc work (sometimes)? Specifically I am looking at Powerwalker VI 1200 CSW and Powerwalker VI 1500 GXB models.

In our environ, there are several services that are deployed via an NFS mount, so that the executables and configs are consistent across the board. Is there any reason why this couldn''t be done with Puppet? For example, each individual system would contain its own /etc/puppet and rc.d and pid files -- but the primary deployment would come from NFS. For that matter, as Enterprise