similar to: package installations on schedule or manual run

I have been looking at Puppet as a possible replacement for cfengine at our site. One difficulty I''ve had with cfengine that I''m wondering if Puppet can solve is that of dealing with laptop/mobile users. Since these laptops move around quite a bit, their IP/hostname is constantly changing. From playing with puppet a bit, I''ve found that it seems to generate the

Hi, I''m in the process of evaluating puppet and cfengine for a rollout on a mix of in-house servers and managed customer servers. I''ve always been a pro-cfengine man, and it''s already running on a small setup of 5 machines. But even though I have pretty clear idea of how I should proceed building the system, I''m intimidated by the vast amount of

Greetings, Shouldn''t puppetd -o --ignoreschedules ... imply that splay* options are ignored :-) If that''s not the intended behavior could we get a --run-now that ignores splay* and schedules? Cheers, Ryan

I have found a few issues with puppet and the up2date provider (version 0.22.4) that I''d like to run by those who use up2date (to see if others are experiencing the same issues). 1. Puppet doesn''t seem to find the latest updates of packages that are already installed. In looking at "/usr/lib/site_ruby/1.8/puppet/provider/package/up2date.rb", I found that

Hello all, I''m thinking about a configuration class that, amongst other things execs out to a ''dangerous'' configuration script. I''d like to make this a noop by default, so the operator has to try a bit harder to invoke it. So I thought about doing something like: class blah { exec { danger: noop => true, tag => hitme, command

Hi Luc, do you know if Ticket #743 will be solved in the next release ? it''s a trivial change of command line option in the provider from --show-available to --showall, --show-available does not list installed packages so you cannot upgrade a package ( if allready installed and a new version comes the provider will not see it rendering the ensure=> latest useless). It could be

Hi, I've seen that some packages use .packageName internally to infer their own name. Is that officially supported? I could not find it documented anywhere. There's utils::packageName(), which internally looks for .packageName. However, if the latter is not found, it may return NULL whereas an error would be more appropriate if a package name is expected. Using .packageName would give

Hi, i want to use Puppet to install all packages from a webserver (no repository) . Therefore I wrote following Script: class install_package { case "$operatingsystem" { SLES: { notify {"${operatingsystem} ${operatingsystemrelease} detected":} notify {"Installing $packagename now:":}

I was wondering how to configure the puppet clients to only listen, not to periodically pull configs down from the puppetmaster. I''d rather push the configs out from the puppetmaster with puppetrun... At a guess I need to set runinterval to 0 in /etc/puppet/puppet.conf? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post

Hi All, I am encountering the following error while performing check on the R package we built: R CMD check packagename_0.99.0.tar.gz During startup - Warning message: Setting LC_CTYPE failed, using "C" * using R Under development (unstable) (2013-05-14 r62742) * using platform: x86_64-unknown-linux-gnu (64-bit) * using session charset: ASCII * checking for file

R CMD check --use-valgrind <packagename> used to run valgrind on the tests in the tests directory of the package. But it seems to have stopped. R-2.9.1 doesn't -- at least on my box -- and neither does R-2.10.0 (devel). I am not sure when this stopped. I think 2.8.x did this. The only old R I have around is 2.6.0 and it certainly does. R CMD check --help for 2.9.1 says (among other

Dear R Core Team, I'm wondering whether it is useful that every package should allow for help(PackageName), giving some general information about the package (more/nicer than library(help=PackageName)). This man page may include some mathematical or statistical background, or contain a guideline for the package. Cheers, Martin -- Martin Schlather email:

Background: OS: Linux Mandrake 10.1 release: R 2.1.1 editor: GNU Emacs 21.3.2 front-end: ESS 5.2.3 Colleagues Since I upgraded to R 2.1.1, I am getting a an error message from R CMD INSTALL packagename that says R_HOME ('/usr/local/lib/R') not found. That's not too surprising, since R is now in /usr/lib/R, but what is confusing me is that R CMD INSTALL -l /path/to/library

Background: OS: Linux Mandrake 10.1 release: R 2.1.1 editor: GNU Emacs 21.3.2 front-end: ESS 5.2.3 --------------------------------- Colleagues The environment variables checked with Sys.getenv() all appeared to be in the right place. The easy fix was to copy /usr/lib/R into /usr/local/lib/R then run the R CMD INSTALL packagename then just copy the package subdirectory back to

> Am 16.12.2018 um 00:07 schrieb Gordon Messmer <gordon.messmer at gmail.com>: > > On 12/15/18 1:05 PM, Frank Cox wrote: >> Ultimately it would be very useful to have some kind of a tool that would generate a report from the rpms installed on a system and tell you exactly what depends on what else. Among other things you could use that report to remove stuff that's not

The function getAllMethods in the methods package uses the non-existent function packageName where I believe the function getPackageName was intended. For example: > getAllMethods("formula") Error in sprintf(gettext(fmt, domain = domain), ...) : could not find function "packageName" The patch to RMethodUtils.R is here: 238c238 <

Hi, in 'Writing R Extensions" of R v2.10.0, under Section 'Cross-references' (2009-09-07) it says: 1. "The markup \link{foo} (usually in the combination \code{\link{foo}}) produces a hyperlink to the help for foo. Here foo is a topic, that is the argument of \alias markup in another Rd file (possibly in another package)." 2. "You can specify a link to a different

Dear all, Is there an elegant way to add citations of packages when using Sweave? Ideally I'd like a function which creates a Bibtex-file with the packagenames as keys. The idea is to use \cite{packagename} or \cite{R} in LaTeX. I know you can get the Bibtex entry with toBibtex(citation("packagename")). But after updating R or a package one needs to update the bib-file too. When

> On 12/17/18 3:50 AM, Leon Fauster via CentOS wrote: >> >> or this one :-) >> rpm -ev --test PACKAGENAME >> will list all packages that require PACKAGENAME > > > True.? I considered that, and then decided that I could never recommend > using "rpm -e" as a test, even with the --test flag, due to the risk of > operator error.? Though if you put it

... and also all objects that actually live in the .GenericArgsEnv environment. > all( sapply( ls( .GenericArgsEnv ), function(.) is.null(environment(.)) ) ) [1] TRUE This has the consequence preventing argsAnywhere to get the args of seq.int. > argsAnywhere( seq.int ) Error in exists(".packageName", envir = envir, inherits = FALSE) : use of NULL environment is defunct