Re: [vox-tech] Upgrading Perl in Debian
Quoting Mike Simons ([EMAIL PROTECTED]): > Testing does have security... and should be used. Concur: It should be noted, however, that the Security Team doesn't promise anything at all about adequacy of this coverage. See: "Testing Security" on http://linuxmafia.com/kb/Debian/ > Using the name "sarge" should be safer for when the release happens. Pick your poison, of course, but some of my machines have happily followed the testing development track through both the potato -> woody and woody -> sarge transitions. I'll be letting them do likewise for sarge+1. -- Cheers, The cynics among us might say: "We laugh, Rick Moen monkeyboys -- Linux IS the mainstream UNIX now! [EMAIL PROTECTED] MuaHaHaHa!" but that would be rude. -- Jim Dennis ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Upgrading Perl in Debian
On Tue, Mar 02, 2004 at 09:23:28AM -0800, Matt Roper wrote: > On Tue, Mar 02, 2004 at 01:10:35AM -0500, Mike Simons wrote: > ... > > If you want to do this, edit the sources.list change all "stable" or > > "woody" words to "testing"... comment out security... you should get a > ... > > Why would you comment out security? Testing has a security repository > and you should definitely keep it enabled; unstable is the branch that > doesn't have one since packages with security fixes go directly into > unstable without a delay. > > Also, if you plan to keep your machine tracking 'sarge' after sarge > become stable, you might want to use "sarge" instead of "testing" in > your sources.list lines -- at the moment they both point to the same > thing, but when the big switch happens, this will keep you on sarge > instead of the new testing branch. Correct on both points. Testing does have security... and should be used. Using the name "sarge" should be safer for when the release happens. The machine I was using as a reference for the email was on testing had security commented out, now that I think about it it was done on that machine from that period when security was down, and I still wanted to get updates. ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Upgrading Perl in Debian
On Tue, Mar 02, 2004 at 01:10:35AM -0500, Mike Simons wrote: ... > If you want to do this, edit the sources.list change all "stable" or > "woody" words to "testing"... comment out security... you should get a ... Why would you comment out security? Testing has a security repository and you should definitely keep it enabled; unstable is the branch that doesn't have one since packages with security fixes go directly into unstable without a delay. Also, if you plan to keep your machine tracking 'sarge' after sarge become stable, you might want to use "sarge" instead of "testing" in your sources.list lines -- at the moment they both point to the same thing, but when the big switch happens, this will keep you on sarge instead of the new testing branch. Matt -- * * Matt Roper <[EMAIL PROTECTED]>* * http://www.mattrope.com * * PGP Key: http://www.mattrope.com/mattrope.asc * * ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Upgrading Perl in Debian
On Mon, Mar 01, 2004 at 08:07:43PM -0800, Richard S. Crawford wrote: > My Debian installation has Perl version 5.6; I'd like to upgrade to > 5.8. Is there a super-easy way to do that (apt-get doesn't seem to be > doing it)? Or a less than thoroughly painful way, at least? It depends on what your /etc/apt/sources.list says... you are probably using "stable" or "woody". At this point Debian testing is being frozen for the next stable release... most major changes are over with (X11 4.3 is still expected to land in testing before the final changes). So at this point I think it's getting safe for most people to switch to testing. If you want to do this, edit the sources.list change all "stable" or "woody" words to "testing"... comment out security... you should get a file that looks something like the following: === # deb file:///usr/src/apt/ ./ # deb http://security.debian.org/debian/ testing main contrib non-free deb http://http.us.debian.org/debian/ testing main contrib non-free deb http://non-us.debian.org/non-US/ testing/non-US main contrib non-free # deb-src http://http.us.debian.org/debian/ testing main contrib # non-free # deb-src http://non-us.debian.org/non-US/ testing/non-US main contrib # non-free === then run "apt-get update", "apt-get dist-upgrade". This process is medium-risk, you will get the new perl, but new everything else too. There are ways to just get the new perl and things it depends on from testing, or compile the perl in testing against the stable system... they are just more complex to explain and lower risk. If you don't feel upto using testing... as for one of these. Keep in mind if you mess up perl, there are quite alot of other things that will break. ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
