search for: portinstall

Hi, I am running an environment with 15 FreeBSD servers on which I want to maintain ports, rc.conf settings, and assorted configuration in /usr/local/etc/. Looked around the existing Puppet docs, I got a puppetmaster and a test client to work and install a package as specified in the site manifest. This is very basic but awesome! I want to create a puppet FreeBSD HowTo that addresses a

...eeBSD base utilities (sed/grep) and handles uniquification of shell variables (handy for rc.conf*, periodic.conf, etc). Could someone post the "defacto" skeleton recipe for FreeBSD to the wiki that installs portupgrade if it''s not installed, and installs a few packages bia portinstall using the ports provider? I''ve got a "portinstall" macro that encompasses make, portinstall, and pkg_add... but am still grappling with but I''m getting hung up on how to write a ''postinstall'' script that executes a (set of)? command(s)?, but only...

...0000416e2c in main () I have confirmed that it's postgresql which makes apache core dump by commenting out pgsql.so in /usr/local/etc/php/extensions.ini. This - off-course - prevents me from connecting to my db. :-/ Apache is ver. 1.3.41 from ports with no changes to the default-values during portinstall. PHP is ver. 5.2.5_1. -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare

...be older than what you''re trying to install from the port (unless you''re maintaining your own package repository which is really what -P is geared towards). In short, I recommend changing the portupgrade invocation to: portupgrade --new --batch --yes or possibly even just: portinstall --batch --yes --batch and -M BATCH=yes are equivalent, but guess which one is more readable ;-). --yes for same reason as for having --batch. Unless anyone disagrees with me... did anyone have a particular reason for using the -p|-P switches? -- Russell A. Jackson <raj@csub.edu> Network...

hi, i''ve run into somewhat of a snag with my puppet instances: when i try to have puppet install a port via portupgrade, it seems to step up each version in ports to the latest, if there are multiple versions. i''ve run into this with two ports so far: vim and postfix. my package line is: package { postfix: ensure => latest } i am however able to specify the version

Hi again, From examples I have gleaned the following snippet for manifests/site.pp Package { provider => $operatingsystem ? { FreeBSD => freebsd, #FreeBSD => ports, debian => aptitude, redhat => up2date }} Are there providers documented somewhere? I''m not sure where to look, and I haven''t come across it in my

does anybody have the same problem as I have : (running CURRENT, but the problem occurs on STABLE too) latest portupgrade, ports cvsuped today. fully reproductible with any package... am i missing something ? i hope yes... portinstall -PP teTeX ---> Checking the availability of the latest package of 'print/teTeX' ---> Fetching the package(s) for 'teTeX-2.0.2_2' (print/teTeX) ---> Fetching teTeX-2.0.2_2 Receiving /var/tmp/teTeX-2.0.2_2.tbz (55422581 bytes): 100% (ETA 00:00) 55422581 bytes transferred i...

...e persisted. This problem occurs also when only / is mounted (no additional storage locations only the OS). Right now I am not sure if this is storage related anymore... but there are some remarks about ffs. Crash occurs after I start Xorg (Kde3 WM, all packages installed from binary packages with portinstall). Please let me know if you need additional information/tests :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Hi, I just installed dovecot. The installation went well and i configured dovecot to user ~/Maildir. When I tested imap via telnet the login work, but right after that the connection is cutted: Trying 192.168.0.14... Connected to op. Escape character is '^]'. * OK dovecot ready. . login jerik password . OK Logged in. Connection closed by foreign host. And the log says: dovecot:

The gnome2 port is broken? I updated the ports tree two time today, but the result is: rss@DaeMoN:/usr/ports/x11/gnome2> sudo make install clean ===> Installing for gnome2-2.4.0 ===> gnome2-2.4.0 depends on file: /usr/X11R6/libexec/cdplayer_applet2 - found ===> gnome2-2.4.0 depends on executable: gnome-cd - found ===> gnome2-2.4.0 depends on executable: gnome-dictionary -

...uppet::Type::Package::ProviderAix: file /usr/bin/lslpp does not exist debug: Puppet::Type::Package::ProviderUp2date: file /usr/sbin/up2date- nox does not exist debug: Puppet::Type::Package::ProviderGem: file gem does not exist debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/local/ sbin/portinstall does not exist debug: Puppet::Type::Package::ProviderZypper: file /usr/bin/zypper does not exist debug: Puppet::Type::Package::ProviderDpkg: file /usr/bin/dpkg does not exist debug: Puppet::Type::Package::ProviderAptrpm: file apt-get does not exist debug: Puppet::Type::Package::ProviderNim: file /u...

I too have been pushed into Puppet 3.0. Clients and PuppetMaster are now at 3.0.0. Not sure if this is a version change or syntax error that I am experiencing. We''ll use ''ntp'' as the example and the "build" host is a VM. The old way: class baseline::ntpd { package { "ntp": ensure => $virtual ? { physical => present,

Dear FreeBSD users and system administrators, While the FreeBSD Security Team has traditionally been very good at investigating and responding to security issues in FreeBSD, this only solves half of the security problem: Unless users and administrators of FreeBSD systems apply the security patches provided, the advisories issued accomplish little beyond alerting potential attackers to the

In http://www.freebsd.org/releases/7.0R/announce.html says Updating Existing Systems > An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes > a major version upgrade, so no matter which method you use to update > an older system you should reinstall any ports you have installed on > the machine. This will avoid binaries becoming linked to inconsistent > sets