search for: jaqque

Hi Johannes, On 18 January 2015 at 20:47, Johannes Ranke wrote: | At the moment you are on your own with R 3.1.2 on jessie. The easiest safe bet in my opinion | would be to install from the Debian sources in unstable, i.e. add a deb-src entry for unstable | to your sources.list, do an apt-get build-dep r-base and then apt-get source --build r-base | and install the packages with dpkg. Ok. I

I''ve submitted the following to howtoforge.com for approval. My plan is to create similar docs for OpenBSD, RHEL and installing from source. I''d certainly appreciate comments on how to improve the document, and feedback on errors. http://nixnotes.org/puppet.html Kent -- "It may be true that the law cannot make a man love me, but it can stop him from lynching me, and I

...w us proper > | testing support via CRAN, which we can fold into your existing mirror > | structure. Plan? > > Or maybe we just stick with "testing" and set up "unstable" via apt pinning > for surgical per-package updates. One of many HOWTOs: > > http://jaqque.sbih.org/kplug/apt-pinning.html > > I've used this quite a bit in the past and it "Just Work (TM)". Using testing as my regular Debian, this is how I do it: apt pinning on stable/testing/unstable, with testing on 900, stable on 800, unstable on 90, and every priority package...

...and search for the 1.8.4 version of Ruby. Debian always prefers stability of package selection over cutting edge. If you always want the latest, I would suggest Fedora, but that way lies the infamous "rpm hell", and why I haven''t touched Red Hat since the late nineties. http://jaqque.sbih.org/kplug/apt-pinning.html has a way to keep stable, yet install packages from testing when you want to. ----------------------------------------------------------------------------------- SuSE is RPM based, but yast handles dependencies pretty well. For Suse the current stable version of 10.0...

Has anyone managed to find a nice and easy way of upgrading to Ruby 1.8.4 on Debian stable? I''m not too adverse to installing an extra repository, and would like to avoid compiling it myself. Stability isn''t a *major* issue; this machine won''t be in ''real'' production. There''s nothing particularly obvious when searching Google. I''m

...N, which we can fold into your existing > > | mirror structure. Plan? > > > > Or maybe we just stick with "testing" and set up "unstable" via apt > > pinning > > > > for surgical per-package updates. One of many HOWTOs: > > http://jaqque.sbih.org/kplug/apt-pinning.html > > > > I've used this quite a bit in the past and it "Just Work (TM)". > > Using testing as my regular Debian, this is how I do it: apt pinning on > stable/testing/unstable, with testing on 900, stable on 800, unstable on > 90...

...h the apt-cdrom tool. #----------------------------------------------------------------- # We definect the PIN which sets the prioratie of packages selects # see also the apt-howto # http://www.debian.org/doc/manuals/apt-howto/index.en.html # and a nice howto for apt-pinning for beginners. # http://jaqque.sbih.org/kplug/apt-pinning.html #----------------------------------------------------------------- #----------------------------------------------------------------- # Stable PIN 990 PRODUCTION TREE deb ftp://ftp.nl.debian.org/debian stable main contrib non-free deb-src ftp://ftp.nl.debian.org...