similar to: R-1.6.2 is released

I've rolled up R-1.6.1.tgz a short while ago. This is a minor upgrade, fixing an assortment of minor bugs, and one major one: 1.6.0 introduced a memory leak in deparsing, causing much trouble for people running simulations. You can get it from the developer site at http://cvs.r-project.org/pub/CRAN/src/base/R-1.6.1.tgz or wait for it to be mirrored at a CRAN site near you. Binaries for

I've rolled up R-1.6.1.tgz a short while ago. This is a minor upgrade, fixing an assortment of minor bugs, and one major one: 1.6.0 introduced a memory leak in deparsing, causing much trouble for people running simulations. You can get it from the developer site at http://cvs.r-project.org/pub/CRAN/src/base/R-1.6.1.tgz or wait for it to be mirrored at a CRAN site near you. Binaries for

I use linux debian testing for which the latest debianized version of R is 1.8.1. Therefore I installed: r-base-core_1.8.1-0.cran.1_i386.deb r-base-dev_1.8.1-0.cran.1_all.deb r-base-html_1.8.1-0.cran.1_all.deb r-base-latex_1.8.1-0.cran.1_all.deb r-base_1.8.1-0.cran.1_all.deb r-doc-html_1.8.1-0.cran.1_all.deb r-doc-info_1.8.1-0.cran.1_all.deb

I've rolled up R-1.4.1.tgz a short while ago. This is a patch upgrade, fixing the most important bugs that cropped up after the 1.4.0 release. A set of recommended packages which have been tested with R-1.4.1 has been bundled up. Binary distributions are expected to include these packages. You can get the files from the developer site ftp://cvs.r-project.org/pub/CRAN/src/base/R-1.4.1.tgz

I've rolled up R-1.4.1.tgz a short while ago. This is a patch upgrade, fixing the most important bugs that cropped up after the 1.4.0 release. A set of recommended packages which have been tested with R-1.4.1 has been bundled up. Binary distributions are expected to include these packages. You can get the files from the developer site ftp://cvs.r-project.org/pub/CRAN/src/base/R-1.4.1.tgz

(please note that this mail is crossposted to 3 lists. No need to CC me to answers, I read the 3 of them...) Some users (including me with my professionnal hat) want to use 3.5 versions of samba on production servers running Debian. Of course, most of the time, these production servers are running Debian lenny (the stable version of the distribution). Debian lenny ships with samba 3.2.5, so

xen-3.0_3.0.1+hg8762-1_i386.changes uploaded successfully to localhost along with the files: xen-3.0_3.0.1+hg8762-1.dsc xen-3.0_3.0.1+hg8762.orig.tar.gz xen-3.0_3.0.1+hg8762-1.diff.gz xen-docs-3.0_3.0.1+hg8762-1_all.deb xen-hypervisor-3.0-i386_3.0.1+hg8762-1_i386.deb xen-hypervisor-3.0-i386-pae_3.0.1+hg8762-1_i386.deb xen-utils-3.0_3.0.1+hg8762-1_i386.deb Greetings, Your Debian

Howdy, I just did an "apt-get dist-upgrade" on my Debian unstable box, and noticed that the Asterisk version appears to be 1.0-1 in the unstable tree. I KNOW that 1.0 hasn't been released yet, so I am wondering who is responsible for the Debian packages? This will be VERY VERY confusing for people and it should be corrected ASAP. -rw-rw-r-- 1 1176 1176 1189696 Jun 7

If they are useful, then one should note where they can be found and how to extract them for anyone not using a Debian-based distro. Saying just that they are in the Debian Testing repo, doesn't mean much to a non-Debian-er... On Thu, Nov 14, 2019 at 09:50:40PM +0000, Ady Ady via Syslinux wrote: > > Do note that not everyone is running a Debian based system, > > so "the

This came up before when debian upgrade wanted to remove these because of their being the previous version. Now all the version numbers are consistant. Deborphan lists them as orphans--no longer used! So ... are all these provided in the "main" wine library and these packages actually orphans? If so, why are they still around? If not, what is going on? Packages are from the

Howdy. I feel like I am missing something really simply with regards to the way that Puppet works and I am wondering if someone can point me in the write direction. I have written a class that downloads, uncompresses, compiles, and installs Python from source. So far so good. The problem is that it only needs to do this once, when Python is not already in place (or some other custom

I needed to upgrade to R 2.4.1 from debian stable maintained at http://cran.r-project.org/bin/linux/debian/. and tried to upgrade with apt-get install r-base. It installed R 2.4.1 successfully, but ran into errors while also upgrading r-recommended packages. I was able to fix that using apt-get install -f euclid:~# aptitude install r-base Reading Package Lists... Done Building Dependency

I can make a few suggestions to help you hunt for the issue. This kind of error is often caused by conflicting packages from proposed, backports, ppas, or other 3rd party repos. If for some reason you have a dependency installed from one of those sources that is newer than what R on cran was built against (stock ubuntu 14.04) then you will hit a conflict. Simply removing backports from your repos

Possibly off the wall and a long shot, but is pre-installed Linux perhaps 32 bit, while the R attempt is 64? JN On 16-03-23 02:22 PM, Barnet Wagman wrote: > Synaptic can show the origin of packages. > > The only thing I see from a backport is > > libcmanager0 > > I don't think this is relevant to R. Or is it. > > The only thing I've got installed from

I am unable to install R on an up to date (i.e. apt upgraded) Ubuntu 14.04 system. According to https://cran.r-project.org/bin/linux/ubuntu/README (and many other sources), R is available for this version of Ubuntu (which is a stable version). I currently have deb https://cran.cnr.berkeley.edu/bin/linux/ubuntu trusty/ in sources.list. I've tried this with and without deb

I tried to install the ''mongrel'' gem tonight via puppet in an attempt to migrate from webrick to mongrel as described on the puppet site[1]. I added the following to my manifest: package { "rubygems": ensure => installed; "mongrel": ensure => installed, provider => gem, require => Package["rubygems"]; }

Hi ive been using shorewall for a while now , and since i was busy i stick along the 1.4.X , but now im on vacation so i decided to move to 2.0.X . My system is a debian but im installing from tgz. Latest shorewall was 1.4.9 and now im at 2.0.7. So i upgrade the version, minor prob, it ask me for then file /etc/default/shorewall. It seem its for user using .deb but anyway i create it ,change

Hello all, I downloaded the linux-2.6.16.16.tar.bz2 (www.kernel.org) and xen-3.0.2-src.tgz. I tried on Debian: # tar -xvzf xen-3.0.2-src.tgz # tar -xvjf linux-2.6.16.16.tar.bz2 # cd xen-3.0.2-2 # mkbuildtree ../../linux-2.6.16.16 # cd ../../linux-2.6.16.16 # make menuconfig (I made a basic configuration) # make-kpkg --append-to-version=-686-xen --revision=1.0 -us -uc kernel_image However

That could do it http://packages.ubuntu.com/trusty-backports/libcgmanager0 Seems to be libc related, which is a pretty core library to much of the whole system. Hmm, which model Dell? We just got a Dell 5000 series with Ubuntu, I have not checked with my boss if there was R installation issues. Thanks, Alex On 03/23/2016 11:22 AM, Barnet Wagman wrote: > Synaptic can show the origin of

I am attempting to rsync data from a rsync server and set the permissions to a different gid on the client: my servers name is "rserver01" my clients name is "rclient01" here is the rysync.conf contained on rserver01: # log file log file = /var/adm/rsync_log # global options for all modules dont compress = *.gz *.tgz *.zip *.z *.rpm *.deb *.iso *.bz2 *.tbz uid = nobody