Debian 7.0 ('Wheezy') Release Planned For 1st Weekend in May
An anonymous reader writes with this good news from the Debian developers who have been working hard to release the next version of the distro: "We now have a target date of the weekend of 4th/5th May for the release. We have checked with core teams, and this seems to be acceptable for everyone. This means we are able to begin the final preparations for a release of Debian 7.0 — 'Wheezy'. The intention is only to lift the date if something really critical pops up that is not possible to handle as an errata, or if we end up technically unable to release that weekend (e.g. a required machine crashes or d-i explodes in a giant ball of fire). Every other RC fix that does not make it in time will be r1 material. Please be sure to contact us about the RC fixes you would like included in the point release!" Of particular interest to casual users, from the list of changes in 7.0: "Debian wheezy comes with full-featured libav (formerly ffmpeg) libraries and frontends, including e.g. mplayer, mencoder, vlc and transcode. Additional codec support is provided e.g. through lame for MP3 audio encoding, xvidcore for MPEG-4 ASP video encoding, x264 for H.264/MPEG-4 AVC video encoding, vo-aacenc for AAC audio encoding and opencore-amr and vo-amrwbenc for Adaptive Multi-Rate Narrowband and Wideband encoding and decoding, respectively. For most use cases, installation of packages from third-party repositories should not be necessary anymore. The times of crippled multimedia support in Debian are finally over!"
xfce 4.8! finally!
Not any worse than "anthratic ocelot" or "diseased Dilbert" or any of the wonderful names canonical has come up with.
Python: 'And then suddenly you have a language which says "we're all stuck with whatever the whiniest coder wants".'
Clearly the marketing message being conveyed is "We don't have marketing here. We have engineers."
I hope they can fix http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368297 before they ship.
It seems horrible in this day and age that a Linux would exist that couldn't get basic functionality with ldap working.
Why would you want a wizard?
Just edit config files like a big boy.
Pick your smtp server and edit the files. Not like there is a lot to it.
Debian will run Linux kernel 3.2.39
Debian can also run on the FreeBSD kernel. It looks like Wheezy will support both 8.3 and 9.0 kernels.
Weezie Jefferson. Movin' on up, to the east side!
The Linux flavour will use Linux 3.2 with a couple of backported features.
http://womble.decadent.org.uk/blog/whats-in-the-linux-kernel-for-debian-70-wheezy-part-1.html
http://womble.decadent.org.uk/blog/whats-in-the-linux-kernel-for-debian-70-wheezy-part-2.html
http://womble.decadent.org.uk/blog/whats-in-the-linux-kernel-for-debian-70-wheezy-part-3.html
No, it is/was caused by long release cycles (2 years or longer between stable releases) and the Debian group's dedication to truly Free software. The finally found something they find to be morally acceptable, and it is in the next release after they found it.
Don't blame me, I voted for Kodos
This is true if you're using Debian on the desktop. As a production server, I want something that Just Works and Doesn't Change except for the occasional security fix.
Finding God in a Dog
What's new in Debian 7.0
2.2.3. Hardened security
Many Debian packages have now been built with gcc compiler hardening flags enabled. These flags enable various protections against security issues such as stack smashing, predictable locations of values in memory, etc. An effort has been made to ensure that as many packages as possible include these flags, especially focusing on those in the 'base'-installation, network-accessible daemons and packages which have had security issues in recent years.
Now there are no reasons for using Ubuntu anymore. I do not remember being so excited ever!
How about "Longhorn"? A grossly overweight beast who is destined for the slaughterhouse but will endeavour to leave massive piles of bullshit on your fields before it goes. There's a good code name for a product.
On the other hand, Windows XP Embedded had the code name of Mantis, which fit it nicely.
The product is officially known as "Debian 7.0". Wheezy is just a code name.
Oolite: Elite-like game. For Mac, Linux and Windows
If you would like to help out, check out the following link. Anything you donate will be matched by a generous donor. Note, this money goes towards DebConf13, the Debian developers conference (free admission to all). Lets get Jessie off to a good start! http://nylug.org/pipermail/nylug-announce/2013-April/001231.html
What, exactly, is wrong with
If I have been able to see further than others, it is because I bought a pair of binoculars.
Will we be getting a multiarch build (armhf+armel) of this one? I found some info that said there would be multiarch for x86 (64-bit+32-bit) but I can't find anything for arm.
Debian's been named this way since, well, forever.
You can't sue for use of first names, especially when they are common or adjectives.
For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
If you've been around any enterprises, then yes, you've seen it. It's one of the components of Active Directory (indeed, it's the "Directory" part of Active Directory.)
LDAP is used to centrally store and manage information about all the entities involved in a network - users, computers, etc. With users that includes everything from their email address to their network password - which brings us to the GP's point.
There are numerous implementations of LDAP out there. Unix systems have been administered using LDAP for decades. So it's a big thing if Debian still doesn't support it properly. It should. And actually, with SAMBA4 now out, we should be moving LDAP (and Kerberos and the other major network administration tools) out of "the enterprise" and start being able to use them in smaller networks, like at home. There's no reason why your D-Link router shouldn't have it built in.
You are not alone. This is not normal. None of this is normal.
It's 2013 and your finally advertising non broken media support. Even Gentoo has had working media support built in for years, I think if this is one of the selling points of Debian then it's time to move on, your trying to get me to take the Honda N360 off your hands instead of the race car.
I think you're laboring under the mistaken assumption that this reflects on the general state of Debian. The truth is that media support is a very specific issue, which, IIRC, was caused by intellectual property issues. For most other things, Debian has had a very complete and high-quality selection of packages. For proprietary media formats, they basically had none - although getting support for those was as simple as adding a repository that provided them (change one line and run a command, or do a couple of clicks - whichever you prefer).
In particular, the "broken" media support was not an issue with Debian generally being broken (it hasn't been) and it also wasn't an issue with Debian being behind other distros (Debian stable tends to have old software, but that is by design - if you want newer software, you can use backports, unstable, experimental, or third-party repositories).
This is one of the major reasons I could never stick with Debian, I need stuff to work, be up to date and ready to go out of the box, Debian is built off legacy packages in an attempt to claim stability, when in reality it's just outdated in it's release mode.
By all means use the distro that works best for you. For me, that's Debian stable, because I want to minimize the amount of time I spend on maintenance. There is a trade-off between having newer software and having more testing performed on that software, and a trade-off between minimizing system maintenance effort and running up-to-date software, and I'm happy with how Debian stable makes these trade-offs. Every other OS I've used has had a higher maintenance burden.
Please correct me if I got my facts wrong.
Which is exactly the kind of behavior you want from a stable distribution. The previous version included support for ext4 as well so that users could test it. It just wasn't the default.
Does anyone know what changed to allow Debian to add MP3 and other libs? There has never been a technical problem with including them, but Debian has always tried to avoid violating patents by distributing patented (or claimed-to-be-patented) software.
I'm glad they've been able to take this step, just wondering what happened.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
I run servers for people who pay me money. I run debian stable exclusively and watch the cash roll in.
"Piter, too, is dead."
Go cry about it somewhere else
Climate Progress - Hell and High Water
What, GNU Hurd won't make it to stable again?
By the way, I'm already migrating (I'm writting at /. while my server downloads packages). New asterisk and postgres. What's not to like?
Rethinking email
We rely on volunteers to add software to Debian. People who want avidemux in Debian (like yourself) haven't bothered to package avidemux yet. Perhaps you would like to help improve multimedia in Debian and join the multmedia team?
http://wiki.debian.org/Teams/Multimedia
Please report bugs about the issues you found:
http://www.debian.org/Bugs/Reporting
They do? Because when I walk over to http://debian.org/ and then click on either "Getting Debian" or "CD ISO Images" it says absolutely fuck all about "Wheezy", "Squeeze", "Etch", "Sarge" or anything. And when you download it, the iso is labeled with the version number 6.0.7.
Likewise, when I head over to Ubuntu.com, click "Download" in the upper right corner, and then Ubuntu Desktop, it says 12.10, no code name here either. Now, there are few places where the codename will appear, but it's not in extensive use. And it's not any worse than OS X recycled names(Mountain Lion is the same as Puma, which is the same as Cougar. Puma has already been used on 10.1).
-- Linux user #369862
Who in 2013 still doesn't "apt-get remove nano" first thing after a fresh Debian install?
sudo-ldap is kind of an out-lier; I've set up NSS LDAP I don't know how many times, against both OpenLDAP and Active Directory, and I've never bothered with sudo-ldap. I can see why people would but it is entirely possible (and IMHO just as easy) to not use it.
One thing that does bug me is that nslcd doesn't understand nested Groups in AD.
How do you authenticate to do sudo then?
The only think I can think is that you are authenticating locally instead of against ldap.