<br /> Freeze Official – Debian Planet

Welcome to Debian Planet

News for Debian. Stuff that *really* matters


Debian Planet is hosted by Bluelinux Internet Services Ltd. Offering a special discounted rate for Free and Open Source software community members.

Buy your Debian merchandise at DebianShop.com.

These are important Debian sites one should not be without!

  • Official Debian site
  • Package search
  • Mailing list archives
  • Bug reports
  • Debian on CD
  • Debian Weekly News — excellent news source!
  • Unofficial APT sources

  • Developers’ Corner
  • Community
    Need help? You’re not alone on this planet.

  • Planet Debian
  • debianHELP
    (User support site)

  • Debian Administration
    (SysAdmin resources)

  • Debian International
  • DebianForum.de

  • DebianForum.dk

  • EsDebian

  • DebianWorld

  • Debian-Fr

  • MaximumDebian

  • DebianItalia
  • DebianUsers

  • Debian-BR

  • DebianHOWTO

  • Russian Debian (Русский)
  • Debian-JP
  • Debian Suisse
  • Contribute
    Got that latest or greatest scoop? Perhaps you have some important news for the Debian community? Submit a news item!

    Or perhaps you’ve written a rather ground breaking insight into some aspect of Debian and you feel compelled to share it with others? Knock up a longer editorial article and send it to the editors.

    General feedback should be sent to staff@debianplanet.org

    The place to get help on a Debian problem (after reading docs) or to just chat and chill is #debian on irc.oftc.net.

    Many of the Debian Planet staff live there so pop by and say hello.

    Debian Planet also has its own channel on the same network called #debianplanet.


    Freeze Official
    Submitted by robster on Tuesday, May 03, 2005 – 21:05
    FreezeThe sarge freeze is now official.

    The expected timeline for the release is as follows:

    3rd May (Today): Freeze time and security support now available for testing
    5-8th May: BSP to bring bug count down from ~85 to ~60/70
    15th May: Debian installer finalised
    27th May: Zarro RC boogs
    30th May: Release

    Now that there is official security support for testing you are very much encouraged to test the upgrade path between woody and sarge and report any issues to the BTS.

    Category: News

    Control panel

    Comment viewing options:

    Select your prefered way to display the comments and click ‘Update settings’ to activate your changes.

    Subject: We have Launch
    Author: dan.hunt
    Date: Tuesday, 2005/06/07 – 14:53
    Woo hoo! Long live the new stable, Sarge.
    [ Please login, or register ]


    Subject: No!
    Author: andresg
    Date: Tuesday, 2005/06/07 – 17:14
    No more than 1.5 years 😛
    [ Please login, or register ]

    Subject: We will do it in May
    Author: mekk@jabber.org
    Date: Wednesday, 2005/06/01 – 16:30
    A few years ago in my organization we planned some extensions to the large project we were developing to be implemented in May. As it occured they waited on ToDo list for two years and then were abandoned.

    Since then, whenever we say that something will be done in May, it means that we like the idea, but will never implement it due to the lack of time.

    Is Debian following?

    [ Please login, or register ]

    Subject: Updates
    Author: megaprogman
    Date: Tuesday, 2005/05/24 – 11:11
    When the freeze is over and the new stable comes out, does this mean that packages like xfce and other will be update to the latest in unstable or will i still need to use a different repository for things like that?
    [ Please login, or register ]


    Subject: Post freeze updates
    Author: glenalec
    Date: Thursday, 2005/05/26 – 12:17
    (Assuming I know what I am talking about – which I may not) if your apt sources is pointing at ‘sarge’ repositories, you will have to change them. If they are pointing at ‘testing’ repositories, they should carry on as per pre-freeze. One of ‘sarge’ or ‘testing’ is a symlink to the other (forget which) and it will be changed if/as appropriate in the repository to keep ‘testing’ as ‘testing’ (and ‘stable’ as ‘stable’, etc.) while the named releases roll on.

    I imagine you would usually point your sources at a named release if you didn’t want to roll over a stable installation immediately on a new stable release coming out. Otherwise point at stable/testing/unstable to keep up with the latest in your chosen category.

    I hope I got that right!

    Glenn Alexander – the man with no surname and a silly hat.

    [ Please login, or register ]

    Subject: Offtopic but critical
    Author: tilleyrw
    Date: Wednesday, 2005/05/11 – 20:02
    My Dell 2350 uses a Broadcom 440x NIC which is not detected by the Debian 3.0r5 install program. Reliance upon other (Knoppix, Kubuntu, etc.) Debian-based distros becomes necessary to enable network access.

    Who should I contact to ask about support for my NIC in Sarge?

    [ Please login, or register ]


    Subject: non-free
    Author: runderwo
    Date: Thursday, 2005/06/02 – 23:44
    Broadcom driver was removed due to binary-only and GPL-incompatible-licensed firmware. Nathanael Nerode hacked up the driver to work without the firmware on cards that don’t require it, and load it from userspace on those that do when the firmware is installed by the user. Unfortunately, this approach was rejected upstream. Recently, Broadcom began to cooperate and tentatively relicensed the firmware under a license which permits GPL compatibility but which disallows modification. AFAIK, a udeb was created and uploaded to non-free. I have no idea if it will make it into sarge or not. I also don’t know if the sarge installer will automatically use udebs from non-free. Steve Langasek should know.
    [ Please login, or register ]


    Subject: Re: non-free
    Author: Kamion
    Date: Saturday, 2005/06/04 – 10:26
    No, this udeb won’t be in sarge, and the sarge installer won’t use udebs from non-free. Sorry.

    Colin Watson

    [ Please login, or register ]


    Subject: Full driver support
    Author: eventhorizon_5
    Date: Wednesday, 2005/05/11 – 22:00
    One of the issues I had with Woody was the small kernels it came with. What I eventually did was first start a patch stream where I merged in multiple important features that I needed into the kernel, and then starting doing full-feature builds, where almost every single feature of the Linux kernel is enabled and modularized if possible (making the kernel highly modular). The Sarge kernels seem to be better, but I haven’t analyzed the installer kernels yet (I build my own currently). The main problem I had was trying to install Woody on multiple SCSI-based servers – the default kernels never had the right drivers or even filesystem support. The kernel build I created featured every possible SCSI driver in the initrd image and also every possible filesystem that would be used, to try to aim for 100% compatibility. Right now I’m waiting for Sarge to be released, and then I’ll start making my 2.6 patches and builds.

    My site for this is here on Tliquest

    There’s also an older CD image on there featuring my 2.4.22-pis5x kernel.


    [ Please login, or register ]

    Subject: Numbers of RC bugs
    Author: jazwiec
    Date: Monday, 2005/05/09 – 17:48
    Today is May the 9’th. Could anyone tell me why there is still 87 RC bugs? (I’m unable to help with bug squashing, just asking)
    [ Please login, or register ]


    Subject: why
    Author: wouter@jabber.org
    Date: Thursday, 2005/05/12 – 16:08
    Probably because of what you just told us, between the brackets. 🙂
    [ Please login, or register ]

    Subject: Great!
    Author: LukeyBoy
    Date: Thursday, 2005/05/05 – 14:56
    Good work everyone, I can’t wait to start using it!
    [ Please login, or register ]

    Subject: Lessons for the future…
    Author: hazelsct
    Date: Wednesday, 2005/05/04 – 19:45
    Not that it’s time for a retrospective just yet, with sarge not officially released. But given that D-P has a poll on how to release next time, it might be worth thinking about why sarge took such a long time to release.

    • Larger number of packages? I don’t think so. Growth from 9000+ (woody) to 15000+ should not have resulted in this slowdown.
    • More architectures? No. Woody has 11, sarge will release with 11.
    • Newer security buildd infrastructure? This was the reason given for the delays of the last few months.
    • New installer? This seems to have been the holdup for most of the time.

    The lesson: since testing was in good shape on most of the architectures for most of the time, splitting up the archive or dropping architectures really won’t speed things up. Now that we have D-I and a new security buildd infrastructure, there’s no reason future releases can’t come out in six or eight months, on all twelve architectures, right?

    For example, etch can have gcc 4.0, X.org, GNOME 2.12 and KDE3.5. We can stabilize all of this by the end of 2005 (~6 months after sarge), right?

    -Adam P.

    [ Please login, or register ]


    Subject: There’s been a lot of disc
    Author: tao
    Date: Saturday, 2005/05/21 – 19:41
    There’s been a lot of discussions on various Debian mailing-lists concerning reasonable intervals between releases for the future, and there seem to be a rough consensus that 12-18 months is ideal. Less than twelve scares away server users, more than 18 makes everything stale. Also, anything less than twelve makes bigger changes of important libraries tricky…
    [ Please login, or register ]


    Subject: Doesn’t need to be faster
    Author: supercheetah
    Date: Monday, 2005/05/09 – 18:03
    I don’t see any reason that it needs to be any faster. Sometimes slow releases like this are a good thing. Some machines don’t need to be upgraded so soon.
    [ Please login, or register ]


    Subject: faster
    Author: wouter@jabber.org
    Date: Thursday, 2005/05/12 – 16:04
    The installer doesn’t work with certain newer hardware — you just can’t get Debian installed in some cases. Modules for software such as zope, apache, xmms and so on, are hard to find and install because some will only have support for more recent versions of the software. The Debian package source is way off when comparing to current upstream releases, which makes patching or modifying code yourself harder. You can not find support on mailinglists anymore, because the author(s) will only help you with problems in current versions of software. Newer features are old before they make it into Debian stable; sometimes you need them so badly, you have to hack it yourself; or force the maintainer to backport fixes — long incorporated into recent upstream versions — into the Debian source.

    And so on.

    Remote servers don’t need to update often, but the current delay is quite ridiculously over the top.

    [ Please login, or register ]


    Subject: Yes it does
    Author: Psiren
    Date: Wednesday, 2005/05/11 – 21:27
    Some machines don’t need to be upgraded so soon.

    Some do. Some won’t even install with the old stable release without a lot of additional work. I respect your viewpoint, but I think you’re in the minority judging by the comments I’ve read over the last 6 months or so.

    [ Please login, or register ]


    Subject: Debian-Installer and architectures
    Author: lovelace
    Date: Friday, 2005/05/06 – 07:33
    I’ve been following the debian-boot mailing list somewhat, and I would say one reason the installer has taken this much time is that is has to support so many architectures, sub architectures and install methods. HP-PA and the plethoria of PowerPC sub architectures are some problematic architectures that comes to mind.

    Having said that, I am sure that the superb quality of the installer – and of Debian software overall – comes from this diversity of architectures. I have no clue how to combine this quality-enhancing diversity of architectures with speedy releases however.

    [ Please login, or register ]


    Subject: And now the work is done
    Author: hazelsct
    Date: Wednesday, 2005/05/11 – 18:04
    It makes sense that it’s been hard to make an eleven-platform installer function properly. But as with boot-floppies before this, now the work is done, so we can go on to do more frequent releases in the future without dropping (sub-)arches, right?

    [Well almost: for example, the nautilus sub-arch on Alpha has been dropped because nobody is helping to enable it. But that’s not the same as dropping arches from release based on numbers of users.]

    -Adam P.

    [ Please login, or register ]

    Subject: Etch to be released at the same time?
    Author: bugmenot2
    Date: Wednesday, 2005/05/04 – 03:12
    Will Etch be released at the same time that sarge will be released as stable? If not, when will the next testing come out?
    [ Please login, or register ]


    Subject: RE: Etch to be released at the same time?
    Author: IpalindromeI
    Date: Wednesday, 2005/05/04 – 14:30
    Take this answer with a grain of salt, as I don’t know the official policy. Anyway, I think in general it goes that soon after the official release, testing is renamed for the next candidate, and reopened to accept packages from unstable. Then there will be a literal flood of packages into testing that have been kept out by the freeze, and after a week or so things settle back down to normal for testing.

    One thing to note is that people tracking testing for their Debian systems, of which you are one I’m guessing, will not be getting package upgrades from now until the release, except for RC bug fixes.

    [ Please login, or register ]

    Subject: Fantastic news
    Author: skx
    Date: Tuesday, 2005/05/03 – 21:43
    This is fantastic news, and I’m very much looking forward to having Sarge released.

    It’s been a long road, but I’m optimistic that this time there will be few suprising last-minute delays.


    [ Please login, or register ]


    Subject: Fantastic News
    Author: meander
    Date: Wednesday, 2005/05/04 – 15:26
    Not really. I gather many folk run debian testing, with forays into unstable & outside packages for that extra needed stuff.

    testing is really up to date, mostly hassle free. apt-get is a big drawcard to debian, so almost everyone currently using the system is actually up date, on the cusp of a debian release, which they already have.

    The PR releases are for tyros/neophytes, everyone else is using their eclctic mix of stable/testing/unstable/outside epackages. Yes, it may drag in some outsiders, but doesnt seem to have any relevance to current updating users.

    Do we really need an aartifical release, or do we just continue to snaffle great packages which we really want, and upgrade the rest at a conservative rate?

    [ Please login, or register ]


    Subject: remote servers
    Author: wouter@jabber.org
    Date: Wednesday, 2005/05/11 – 05:19
    For admins that take care of servers in remote locations, a stable and more or less up to date release is important. As sysadmin, your job is on the line with every decision you make. There needs a balance between not too many updates — because they mean more work and risk for unexpected troubles — and still enough updates so you’re closer to the current source of the software and you’ve got some new features.

    Too old is annoying because some software has plugins or uses features that only work with newer versions of other software.

    [ Please login, or register ]


    Subject: “Do we really need an aartifical release”?
    Author: owen
    Date: Monday, 2005/05/09 – 09:55

    Stable has a security infrastructure and you know that if you install a machine in monday and a second machine on friday you will get the same behaviour from both machines… so yes a stable release is usefull.

    I also know that when I’ve installed and configured a Debian stable machine that I can leave it alone (except for security “apt-get upgrade”s) for months at a time.

    Testing may be usefull for desktop or home enthusiast use but stable has a place in the enterprise data centre. With Debian in the data centre you have people paid to lookafter debian machines and as the machines lookafter themselves (mostly) these people can work on improving debian and submitting fixes and features to the BTS.

    At least that’s how it works for me!

    Alex Owen

    PS: I’m also thinking of setting my mother up with a Debian machine… That would _not_ be a good candidate for testing… My mother would get frustrated is the programs kept changing their behaviour week to week… with stable the programs will be consistent till the next stable release.

    [ Please login, or register ]

    Search articles

    ·News (406)
    ·Features (5)
    ·Site News (16)
    ·HOWTOs (79)
    ·Tips (21)
    ·Opinion (29)
    ·Q & A (35)
    ·Sponsorship (1)
    ·Press Releases (5)

    Log in


    Remember me

    » Register
    » New password

    Debian Security Announcements
    DSA-943 perl
    DSA-942 albatross
    DSA-903 unzip
    DSA-941 tuxpaint
    DSA-940 gpdf
    DSA-939 fetchmail
    DSA-938 koffice
    DSA-937 tetex-bin
    DSA-936 libextractor
    DSA-935 libapache2-mod-auth-pgsql

    Planet Debian
    Wouter Verhelst: On flames.
    Joachim Breitner: Fixing my planet.debian.org subscription
    Steve Kemp: She has the blood of reptile just underneath her skin
    Pierre Habouzit: Married …
    Pierre Habouzit: whitelister 0.4 (SPF) and aaege ….
    Pierre Habouzit: kde 3.4.1 upload
    Holger Levsen: In case you are running OpenWRT
    Michael Janssen: Shiny roofs are good for the environment!
    Matthew Palmer: Work it out yourself, dammit!
    Axel Beckert: Tell me which music you like and I tell who you are

    Debian Administration
    How do I prevent rebuilt packages from being upgraded?
    Disabling the print-screen key inside X?
    Monitoring your bandwidth usage with vnstat
    Ruby on Rails on Debian
    Choice for Virtual Private Servers?
    Monitoring your hardware’s temperature
    Sending mail with Exim from ‘dialup’ IP
    How to recover GRUB Debian Sarge after reinstalling Windows
    Getting a GUI
    Spam filtering with Pyzor and SpamBayes

    Latest poll: Which release scheme should Debian follow?
    Continue this way (release when ready)
    Give up on releasing
    Split the release up
    Speed the release up
    Crank the workload up (see DebianWiki ReleaseProposals for details on these)

    Total votes: 372
    0 comments · older polls

    home · archives · news feeds · about · polls · search · sections · user account

    Powered by the amazing Drupal

    Debian Planet is not officially related to the Debian Project.
    Debian and the Debian logo are trademarks of Software in the Public Interest, Inc.