similar to: Docker versus Vagrant for reproducability - was: The case for freezing CRAN

There is a central assertion to this argument that I don't follow: > At the end of the day most published results obtained with R just won't be reproducible. This is a very strong assertion. What is the evidence for it? I write a lot of Sweave/knitr in house as a way of documenting complex analyses, and a glm() based logistic regression looks the same yesterday as it will

On Fri, Mar 21, 2014 at 8:43 AM, Therneau, Terry M., Ph.D. < therneau@mayo.edu> wrote: [...] > > Gabor Csardi discussed the problems with maintaining a package with lots > of dependencies. > I maintain the survival package which currently has 246 reverse > dependencies and take a slightly different view, which could be described > as "the price of fame". I feel a

This has been a fascinating discussion. Carl Boettinger replied with a set of examples where the world is much more fragile than my examples. That was useful. It seems that people in my area (medical research and survival) are more careful with their packages (whew!). Gabor Csardi discussed the problems with maintaining a package with lots of dependencies. I maintain the survival package

We are pleased to announce the immediate availability for CentOS Linux 7 x86_64 images for Vagrant. This image represents a minimal install set, that lines up with the user expectation for our Cloud Images, our ISO based Minimal installer and the default minimal install profile from the in-distro install options. Images are released for the VirtualBox and LibVirt providers ( more providers

I am pleased to announce the immediate availability of Vagrant 1.7.4 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install sclo-vagrant1 $ scl enable

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Updated Vagrant box's are now available for CentOS Linux 7 and CentOS Linux 6 for x86_64. These are available, as in the past, for the Libvirt and the VirtualBox providers in Vagrant. We have also enabled the vmware providers, for anyone using Vmware's products for backing Vagrant on Linux, MacOS or Windows. ref:

Hi, At Vagrant Cloud there are "box" images for stream8 and stream9 [1]. At least they are supposed to be there. The download links on the detail pages, for example for stream9 20230727.1 [2] are redirected to cloud.centos.org, however they give an 404 error. Possibly the centos Vagrant Cloud page is not kept up to date with the actual box images that are now present on

I'm using libvirt on Debian/stretch (testing) with vagrant and the vagrant-libvirt plugin. When I import a vagrant box (jessie64.box), the resulting file permssions let anyone in the "kvm" group read the img. But when I build upon that box, only root can read it: -rw------- 1 root root 20198785024 Sep 19 18:19 buildserver_default.img -rwxr--r-- 1 libvirt-qemu kvm

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Updated Vagrant box's are now available for CentOS Linux 7 and CentOS Linux 6 for x86_64. These are available for the Libvirt and the VirtualBox providers in Vagrant. ref: https://atlas.hashicorp.com/centos/boxes/6 https://atlas.hashicorp.com/centos/boxes/7 Release Notes for these images are published at :

I took an hour this morning to document how I use Vagrant and Puppet together to provision development VMs as well as more production-like systems. This may be entirely elementary to folks who are more fluent with Puppet, but this is an example I thought was lacking. https://github.com/blalor/vagrant-puppet-example I welcome feedback and criticism of this setup. I''m looking to

Hi, At Vagrant Cloud there are "box" images for stream8 and stream9 [1]. At least they are supposed to be there. The download links on the detail pages, for example for stream9 20230727.1 [2] are redirected to cloud.centos.org, however they give an 404 error. Possibly the centos Vagrant Cloud page is not kept up to date with the actual box images that are now present on

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Updated Vagrant box's are now available for CentOS Linux 7/x86_64 and for the first time for CentOS Linux 6/x86_64; We are providing box's for Livbirt provider and the Virtual Box provider. ref: https://atlas.hashicorp.com/centos/boxes/6 https://atlas.hashicorp.com/centos/boxes/7 Release Notes for these images are published at :

Hi guys: I'd like to "scriptify" my virtual machine manager deployment. In particular id like to 1) Configure a 3 node cluster from an ISO 2) Assign static IPs at the vm level, and have those cascade into /etc/hosts 3) Add storage to each machine in the cluster . 4) Set the memory/CPU# for each machine. Is there a way i can automate this task using VMM, or maybe, using VMM in

Hi All, I am using Vagrant to provision a box (CentOS 6.x) with puppet provisioner. The box is built by using veewee, with ruby 1.8.7 and puppet 3.2 iinstalled, and the vagrant environment layout is, . ├── Gemfile ├── Gemfile.lock ├── Rakefile ├── Vagrantfile ├── definitions │ └── centos-6.3.minimal ├── hiera │ └── data ├── iso │ ├── CentOS-6.3-x86_64-minimal.iso │ └──

This came up again recently with an irreproducible paper. Below an attempt to make a case for extending the r-devel/r-release cycle to CRAN packages. These suggestions are not in any way intended as criticism on anyone or the status quo. The proposal described in [1] is to freeze a snapshot of CRAN along with every release of R. In this design, updates for contributed packages treated the same as

In the rgdal package, configure.ac has had : ${LDFLAGS=`"${RBIN}" CMD config LDFLAGS`} at least since 2012, so picking up LDFLAGS known to the R version installed. Very recently, users installing rgdal from source with R installed from RPM are seeing problems, such as those reported in this thread: https://stat.ethz.ch/pipermail/r-sig-geo/2020-June/028251.html The diagnosis by

On Mon, 29 Jun 2020 at 11:24, I?aki Ucar <iucar at fedoraproject.org> wrote: > > On Mon, 29 Jun 2020 at 10:21, Roger Bivand <Roger.Bivand at nhh.no> wrote: > > > > In the rgdal package, configure.ac has had : ${LDFLAGS=`"${RBIN}" CMD > > config LDFLAGS`} at least since 2012, so picking up LDFLAGS known to the R > > version installed. Very

Hello, I recently installed Ubuntu 24.04 on a MacBook Pro (Mid-2010) running a NVIDIA GeForce GT 330M adapter. Unfortunately the computer is constantly freezing. If I pass "nomodeset" to grub, the nouveau driver is not used and the computer does not freeze so it seems to be related to the nouveau driver. I am wanting to know if there are any parameters I can pass to nouveau to

Hello, I'm using *virt-sparsify* for compressing image file [ash2] jenkins@b-imagebuilder-worker-r13h17-prod:~/workspace/imagebuilder/packer/output$ virt-sparsify --compress /data/home/jenkins/workspace/imagebuilder/packer/output/packer-vm.qcow2 /data/home/jenkins/workspace/imagebuilder/packer/output/packer-vm.qcow2.sparsified Input disk virtual size = 41943040000 bytes (39.1G) Create

In my case, one of the brick( I use distributed replication) is gone in zombie status, The file system is just like freezing For ping test with bricks, it looks like it's up and running ( Using gluster brick status, it looks like connected ) But when I try to log into that brick thru sshd, it failed with time out. In that situation, Gluster is freezing. Every volume is going