Slashdot Mirror
Debian 2.2r5 Released
Debian potato has been updated to 2.2r5. See the press release for info on what has changed - mostly bugfixes, of course, since this is the stable distribution.
← Back to Stories (view on slashdot.org)
← Back to Stories (view on slashdot.org)
A comprehensive list of which packages were included and which were rejected is at http://people.debian.org/~joey/2.2r5/full.html
It's a release for security updates. This is very different from a bugfix release, which would generally be a much greater undertaking and require a lot more packages to be upgraded to newer versions. Think of it this way: a security update would be when Slash code allows users to gain the access levels of other users, including elevated privileges. A bugfix release would be an increment in the Slash code that fixes broken features that do not include security compromises. Makes sense? =)
Interested in open source engine management for your Subaru?
check debianplanet.org for thee thread, i believe most of the libpng issues have been taken care of.
Actually, isn't "unstable" 'Sid'? I think 'Woody' is the "testing" release.
I've run into this same problem with libpng on my system running debian unstable, I found an article discussing a fix at www.varlinux.org
/usr/lib/libpng.so.3
/usr/lib/libpng.so.2.0.1.12 /usr/lib/libpng.so.3
To summarize what needs to be done though:
rm -f
ln -s
I just did an apt-get upgrade a few minutes ago and it undid this, I haven't noticed any problems yet so maybe they've already fixed this issue.
Testing consists of packages from unstable that have gone a couple weeks without incident. The result is a very current system with the bleeding edge problems smoothed over. Most of our production boxes are now on it.
There are systematic weaknesses with version 1 of the ssh protocol, which this doesn't address, of course. However, as far as I'm aware, a successful exploit has yet to be mounted against these.
Still, though, version 2 of the SSH protocol is better, and building updated OpenSSH packages for potato is not difficult. The 'source' command in apt-get is very helpful here.
noah
Wow, you're going to get 32767 responses to this.
1. #vi /etc/apt/sources.list
2. Change all instances of "stable" or "potato" to "woody".
3. #apt-get dist-upgrade
(4.) #apt-get -f install ;apt-get dist-upgrade --yes , until it all works.
I used to run debian stable, but switched to testing several months ago. I think testing is the dist for most users. Too bad newbies get steered toward stable. The testing dist is stable enough for just about everybody.
In fact, here are the requirements for a package to make it into a Debian stable revision:
(from http://people.debian.org/~joey/2.2r5/)
[Joey Hess's] requirements for packages to go into stable:
1. The package fixes a security problem. An advisory by our own Security Team would be quite helpful.
2. The package fixes a critical bug which can lead into data loss, data corruption, or an overly broken system, or the package is broken or not usable (anymore).
3. The stable version of the package is not installable at all due to broken or unmet dependencies or broken installation scripts
4. The package gets all architectures in stable in sync.
5. All released architectures have to be in sync.
Look out honey, 'cause I'm using technology; Ain't got time to make no apology
Re: ISOs:
Limited bandwidth - that's all I have to say. Most people don't need the ISOs.
Re: what Potato comes with
If you had looked around on Usenet for about 2 seconds - I believe it's the second or third post in response to a search for "XFree86 4 potato" you'd find out how to upgrade Potato to Woody (testing) in about 5 minutes.
Edit sources.list, replace stable with Woody.
Apt-get update.
Apt-get dist-upgrade.
Wait, relax, enjoy.
Re: the kernel
Please. A 2.4 kernel isn't THAT necessary.
Actually I always thought the correct usage on slashdot would be to use the teletype font to denote a typed command. After a quick bit of research I discovered that single quotation marks (') should be used in place of regular quotation marks when the word or phrase you're enclosing is in another set of regular quotation marks (i.e. "His exact words were, 'I used apt-get to install that package'")
It can also be used when referring to words in an unusual context, so I guess if you don't use teletype the single quotation marks are the way to go.
Maybe we need a Slashdot Manual of Style.
actually, apt-get install cruft, and then run cruft. It will remove old programs and libraries that aren't needed that you don't want anymore. It cleaned up my system quite a bit.
Let me just ask a general question then - what's the best way to install a fresh Woody system? My current system is a bastardized Potato with some ugly Sid stuff thrown in to make it complicated. I want a Woody system, upgraded to a 2.4 kernel with ipfilter, and I'm willing to start from scratch.
Do I remove all non-Woody sources from the apt-get sources file? Do I manually remove all potato and unstable packages? Or is it best to format and start over?
First of all, if the only thing you really want is a 2.4.x kernel and ipfilter, you don't need to upgrade everything; you could just get kernel sources, build a 2.4.x kernel, and go from there.
But if you want to update your system, here is what to do:
Edit your sources.list file to point to a Debian mirror for the "unstable" packages. (Or "testing" if you want to try that, but I'm perfectly happy with unstable.)
Run "apt-get update", which fetches the list of new packages.
Run "apt-get dist-upgrade", which downloads the new packages and installs them.
The Debian APT system is really cool, but it isn't absolutely perfect. It will try to install packages like libc first, and then later on install packages that depend on the other packages; but sometimes it fails. Sometimes it will try to install a package, only to have the install fail because some needed package wasn't there. This especially happens when upgrading from Potato to unstable.
The solution is simple: you just keep running "apt-get dist-upgrade", over and over, until it reports that all packages installed. Each time more packages will install, as the dependencies get installed.
I've done this about twice, and that's what worked for me.
steveha
lf(1): it's like ls(1) but sorts filenames by extension, tersely