101–110 of 132 posts
"This release includes numerous updated software packages" ... software packages which are already outdated.
Funny how this is downvoted. Fact is that Debian has always been outdated. For some that is a strength, for most it is a frustration.
Earlier quoted context omitted.
If you're running Ubuntu Desktop and want to run modern game systems like Steam then I think you'd want to stay on Ubuntu.
https://github.com/GhostSquad57/Steam-Installer-for-Wheezy
Earlier quoted context omitted.
For the record, debian also packages up pip and you can install an up-to-date django using that. You essentially get the best of both worlds here.
Well, it also packages tar and I can untar and install any package from source.
Earlier quoted context omitted.
So then run ArchLinux on your servers, and godspeed? Debian is not aimed at having the latest and greatest, but its packages do tend to be more up-to-date than RHEL/CentOS, which is its main competition in the "stable server distro that doesn't get you fired" category.
So our options are either bleeding edge versions or prehistoric ones?
Earlier quoted context omitted.
Testing is sometimes problematic from a security POV. Since it's considered a staging area rather than a "proper" distribution, it isn't security-managed, and occasionally vulnerabilities can persist for an extended period of time. The most common case: v1 of a package is in Debian stable. v2 comes out, is uploaded to unstable, migrates to testing. Later, v3 comes out, is uploaded to unstable, but its migration to te…
Interesting scenario. I never heard it voiced before, and must be so rare it can safely be ignored as a non-issue.
Sorry for the misinformation!
Earlier quoted context omitted.
Use Debian testing for the desktop. Desktop users don't use stable, or at least use it with backports. And what's so unbearable for the server? As others pointed out, RHEL ships even an earlier version of the kernel.
Testing is sometimes problematic from a security POV. Since it's considered a staging area rather than a "proper" distribution, it isn't security-managed, and occasionally vulnerabilities can persist for an extended period of time. The most common case: v1 of a package is in Debian stable. v2 comes out, is uploaded to unstable, migrates to testing. Later, v3 comes out, is uploaded to unstable, but its migration to te…
http://www.debian.org/vote/2013/platforms/lucas
I hope they'll tackle this security issue.
Earlier quoted context omitted.
Interesting scenario. I never heard it voiced before, and must be so rare it can safely be ignored as a non-issue.
Doing a bit more research, it looks like my info is out of date. There used to be a warning about it on the Debian website (I think that's where I originally got the admonition that testing may have security gaps), but the current website actually says that it is security-managed, with security.debian.org uploads done in cases where migration from unstable is held up: http://www.debian.org/security/faq#testing Sorry…
I just found from your link that I had no security repo configured. Just added:
deb http://security.debian.org testing/updates main
UPDATE: Here is a more correct set of settings from http://secure-testing-master.debian.net/ :
deb http://security.debian.org testing/updates main contrib non-free
deb-src http://security.debian.org testing/updates main contrib non-free
Even though they claim that contrib and non-free have no security updates, they are listed for some reason.
My sources.list has the word "testing" all this while. Should I change it to "wheezy" now? I'm asking because I guess new packages (in large numbers!) will start trickling down to testing/jessie and the possibility of breakage is high. What is a reasonable time to expect this "rush" to slowdown or come back to the pace of "normal" testing? I can probably live with my existing "testing" for say 1-2 months, after which…
I'd say switch the sources.list to 'stable' or 'wheezy' for a few weeks. After that, switch back to 'testing' and run "apt-get dist-upgrade --assume-no" and see what Debian is going to upgrade. There is no real proper way to do this, other than testing in a VM, or a chroot.
Earlier quoted context omitted.
For anyone else wondering, RHEL 6.4 has the 2.6.32-358 kernel. Zenwalk 7.2 has the 3.2.5 kernel. What's the point of citing the kernel shipped with another distro here?
Shows how unbearably slow Debian's release cycle is. Wheezy ships with all the latest packages from 2 years ago.
Earlier quoted context omitted.
FWIW, I've been running Debian "testing" on my machine since 2001-ish and I've never done anything special near releases. Except maybe rejoice at all the old packages finally getting upgraded. :-)
Didn't you run into any breakage of packages? I mean there's this mad rush into testing right after a new release. I'm thinking of running wheezy for a couple of months until the storm calms down.