Slashdot Mirror


Debian Announces Sarge Will Include GNOME 2.8

El Cubano writes "A recent posting to the debian-devel-announce mailing list announces that Sarge will release with GNOME 2.8. From the announcement: 'After requests and a detailed proposal from the GNOME team, we accepted an upload of GNOME 2.8 into sid, and, via the usual mechanisms, into sarge. We should mention that the release team was running out of objections to GNOME 2.8 in unstable that the GNOME team hasn't satisfactorily addressed; this, and the fact that they have demonstrated good reaction times of late are the main reasons why we're approving it despite the timing.'"

51 of 276 comments (clear)

  1. Sarge Will Include GNOME 2.8 by gowen · · Score: 5, Funny

    And its scheduled for release at roughly the same time as Saddam Hussein

    --
    Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    1. Re:Sarge Will Include GNOME 2.8 by pretzelgod · · Score: 2, Informative

      You joke, but we'll be lucky to see sarge in 2006 if this is any indication.

  2. Is Armagaedon upon us? by AlanS2002 · · Score: 4, Funny

    Debian incorporating newly released software into stable in less than two years, who would of though.

    --
    Not all conservatives are stupid,
    but it is true that most stupid people are conservative.
    - Hume
    1. Re:Is Armagaedon upon us? by Antique+Geekmeister · · Score: 2, Interesting

      Maybe they ran out of people who bother to use "stable", since so many tools there are deprecated and a monster to maintain?

      The Debian "stable" vs. unstable seems to match the new RedHat "Enteprise" releases vs. the new "FEdora". Maybe Debian can shorten their transfer time and testing enough to use "stable" for production servers? I know a bunch of people who'd like that.

    2. Re:Is Armagaedon upon us? by arose · · Score: 5, Insightful

      Stable is for people who need an unchanging system (no, I'm not one of them), please leave it alone.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    3. Re:Is Armagaedon upon us? by vrt3 · · Score: 4, Insightful

      But AFAIK there isn't really an alternative for people who are willing to use a somewhat changing system. unstable changes too much; it's OK for a desktop, but not for a server. testing would be acceptable, but doesn't get security updates.

      So I run stable on my little home server, eagerly awaiting the release of Sarge.

      --
      This sig under construction. Please check back later.
    4. Re:Is Armagaedon upon us? by Zach+Garner · · Score: 3, Informative


      The Debian "stable" vs. unstable seems to match the new RedHat "Enteprise" releases vs. the new "FEdora". Maybe Debian can shorten their transfer time and testing enough to use "stable" for production servers? I know a bunch of people who'd like that.


      We [beware of the Marketing people's use of shockwave and flash] already do that. I'm sure many others do to. We count on stable being secure and reliable. We're ok with it being relatively slow moving, if that's what it takes. A few select applications, such as X11VNC are brought in from testing or unstable, or made into custom packages internally. It works great.

      We would like to see some newer software make it's way into stable, such as subversion. Right now I run a mixed testing/unstable at work, and a mixed unstable/experimental at home. I've never had a problem, though I do take time to understand what the effects of an update will be on the unstable and especially the experimental applications.

    5. Re:Is Armagaedon upon us? by vrt3 · · Score: 2, Insightful

      It happens regularly that something I'd like to be on my server is not yet in stable; I can't remember all of them, but things that I can remember are Python 2.3 (or even better, 2.4), MySQL 4, PHP 5.

      --
      This sig under construction. Please check back later.
  3. KDE by ultrabot · · Score: 3, Insightful

    How about KDE 3.3?

    Not that it really matters anymore - many of whom have been waiting for Sarge have got with the program and switched to Ubuntu.

    --
    Save your wrists today - switch to Dvorak
    1. Re:KDE by coekie · · Score: 5, Informative

      Actualy reading the announcement would have answered your question: "In the meantime, we were also asked why we decided to go with KDE 3.2, and if it would be possible to go with KDE 3.3 instead. The main reason is that KDE 3.3 in unstable started with some RC bugs, and there was no proposal from the KDE team how to proceed. The door is only closed, but not locked for KDE 3.3. We are still open for proposals how to sort the KDE 3.3 issues out, and there has been some productive discussion of late about that - but no final decision yet."

    2. Re:KDE by quinto2000 · · Score: 2, Insightful

      Did you run it on all 15 of the architectures that Debian supports? Lots of Linux software runs fine on some architectures but not on others. Debian is committed to only releasing software that runs on all of them. The user-friendly Debian-based distributions may be nice in other ways, but they usually only worry about one architecture - ia32 or sometimes ppc.

      --
      Ceci n'est pas un post
    3. Re:KDE by MsGeek · · Score: 4, Interesting

      KDE 3.3.1 is stable enough to where I'm relying on it on my ThinkPad. Sid is your friend. Gotta love the improved Konqui.

      Oh yeah, and KDE has none of these problems that people are reporting with GNOME. Snappy performance on a Pentium II Mobile 400MHz. I daresay even snappier than the install of Windows 2000 SP4 on the other partition.

      There is no reason why people running personal Debian desktop systems shouldn't liberally add Sid packages to their system. What Debian.Org calls "unstable" is actually ready for prime time on non-critical machines.

      If you run a critical server, go with Woody aka Stable. If you can live a little on the edge with your server, run Sarge/Testing/Release Candidate. If you are setting up a desktop for Grandma, use Sarge with no Sid packages. For everyone else, live on the edge, baby! ^_^

      --
      Knowledge is power. Knowledge shared is power multiplied.
  4. good for debian, good for users by feepcreature · · Score: 3, Informative
    Gnome 2.8 is stable enough in ubuntu, so it's good to see it being used back in debian.

    Also, this might help combat the "Debian [stable] never includes new stuff" meme. Another good thing.

    --
    Paul "Say no to feeping creaturism"
    1. Re:good for debian, good for users by Captain+Large+Face · · Score: 3, Insightful

      Also, this might help combat the "Debian [stable] never includes new stuff" meme. Another good thing.

      "New" is relative. After stable switches from Woody to Sarge, it is highly unlikely that you will get a new version of GNOME until Etch becomes stable. So no, Debian stable will never be the place to look for new stuff, except when the stable version changes, but then that is the whole idea.

    2. Re:good for debian, good for users by byolinux · · Score: 2, Interesting

      I have this weird little bug in GNOME under Ubuntu - when I log in, I get an XFree 'X' cursor in the middle of the screen, and it won't go away.

      Apart from that, it's all really quite nice. I'm looking forward to running UserLinux though.

  5. FYI by bionicyeti · · Score: 4, Funny

    Garden Gnome 1.0 is scheduled for release on my lawn this spring...

    1. Re:FYI by kaszeta · · Score: 5, Funny
      Garden Gnome 1.0 is scheduled for release on my lawn this spring...

      If it's a Debian Garden Gnome, you'll have to leave it in the back yard until it's weathered and outdated, and then move it to the front yard after it's demonstrated its stability for two years...

  6. applicable Star Wars quote by for_usenet · · Score: 5, Funny

    Luke: What is it Obi-Wan ?

    OWK: I felt a deep disturbance in the force. It was as if Debian decided to be more current with their packages.

  7. Re:I have been waiting for this by wild_berry · · Score: 3, Informative

    Are you sure this isn't a troll?

    I've never had that problem with Gnome. My system is as responsive with Gnome as my previous operating systems: Win98se and WinXP. Are you sure your system is okay?

  8. Almost time for regular users to run testing by martinde · · Score: 4, Insightful

    I've been running stable (woody) since it came out, and it has served me well. I started using Adrian Bunk's backports, and then selected things from backports.org... Then I upgraded to KDE from downloads.kde.org, and then openoffice from some other backport collection. Amazingly enough, this collection of software worked well enough for me.

    I recently took the plunge and converted a couple of machines to testing (soon to be sarge). First thing I will say is that even with all of the backports, the upgrade went very smoothly. And I'll also say that sarge is working well for me; so well that I've installed it on several other machines using the new debian-installer rc candidates, and that has worked flawlessly for me as well!

    As soon as security update support is up and running for testing, anyone remotely interested in sarge should consider upgrading and filing bug reports as appropriate. This is how you can help speed up the "real" release of sarge!

    And I do think that when sarge comes out, it's going to be an excellent platform. It is so much nicer about hardware autodetection, font handling, and about a million other things... Without losing any of the old things that you love about Debian.

    Lets hope that the next stable release doesn't take too long, although given Debian's nature, it's hard to see how it won't... Assuming the official compiler moves to gcc 3.4 (or the upcoming 4.0), then there is going to be another painful transition for all of those C++ applications. Hopefully someday g++ will have a stable C++ ABI and those transitions won't be an issue for projects shipping C++ libraries... (This was one of the major issues for getting KDE into unstable earlier this year.)

  9. Re:I have been waiting for this by oddbudman · · Score: 2, Informative

    I'm with you on this call dude. Gnome 2.6 and Gnome 2.8 seemed fine to me (responsive wise). It doesn't take a genius to have a poke at C lacking boundary checking. Last time I checked the kernel was written in C also- what a hack! Furthermore I thought that most Gnome's apps were written in python.

  10. Re:Anonymous coward is confused by Anonymous Coward · · Score: 5, Insightful
    So which is Sarge?

    Situation now:
    potato = obselete
    woody = stable
    sid = unstable
    sarge = testing

    Once sarge is declared stable,
    woody = obselete
    sid = unstable
    sarge = stable
    unknown = testing

    So, sid will remain unstable and a new name for the testing branch will have to be decided (unless I missed something and that's already happened).

  11. x.org by sewagemaster · · Score: 4, Interesting

    anyone know whether x.org will make it into sarge as well?

    1. Re:x.org by smoking2000 · · Score: 3, Informative

      No, x.org will not be in Sarge.

      See the news item "Future of Debian X11 Packages" in this issue of Debian Weekly News

    2. Re:x.org by Anonymous Coward · · Score: 5, Informative

      The Debian team will begin integrating X.Org into Unstable when Sarge is released. Except, they'll try and do it modularly, instead of monolithically...read more http://lists.debian.org/debian-x/2004/05/msg00431. html.

  12. How about these? by Anonymous Coward · · Score: 3, Insightful

    PostgreSQL 8,
    PHP 5,
    Tomcat 5.0.x (5.5 would probably be pushing it a little..),
    Sun jdk1.5?

    1. Re:How about these? by RAMMS+EIN · · Score: 3, Informative

      Definitely not Sun JDK. It's not DFSG compliant.

      PHP 5 probably still has some issues to be worked out, meaning it won't get into stable.

      I don't know about the others.

      --
      Please correct me if I got my facts wrong.
  13. I haven't been in the army... by Buchenskjoll · · Score: 4, Funny

    is Sarge Will someone I should know? I am familiar with General Failure, though.

    --
    -- Make America hate again!
  14. Re:Anonymous coward is confused by peterpi · · Score: 5, Informative
    The releases of Debian go through the following stages:

    • Unstable
    • Testing
    • Stable
    • Dead


    And for most users, at any one point in time the Unstable one offers the best tradeoff between features and stability. The current situation is that Sid is unstable, Sarge is testing and Woody is Stable.

    Real Soon Now, they'll all shuffle along one, Woody will die and Sarge will become stable. I run sarge on my home and work machines and it's completely rock solid.

  15. Re:E? by Shadestalker · · Score: 2, Informative

    Firefox 1.0 has been in sarge for a while now. Gimp 2.0.5 is in, though I'm not sure when it was released for sarge.

  16. Re: You like the cup, drink from the cup. by andersa · · Score: 2, Informative

    The X Strike Force

    To sum it up, Debian is maintaining it's own tree of Xfree86, without any material that has the new license, but with some x.org and other patches. This is what will be in Sarge.

  17. Release date by kbewley · · Score: 3, Funny

    Yah! A Debian insider is reported to have said that the Sarge release will form part of a bundle with Duke Nukem Forever.

    --
    -- These views are my own and do not represent those of my employer in any way.
  18. Re:E? by quamaretto · · Score: 2, Informative

    Sorry for the confusion - I was referring to 'stable'. I use unstable, mainly because it has all of that stuff. (Excpet E17 :)

    Seriously, I should put something about "inspect message for sarcasm before replying" in my sig.

    --
    *is run over by rotten tomatoes*
  19. buffer overruns by synthespian · · Score: 3, Insightful

    But isn't this due to a "cultural" problem? For instance, the fine OpenBSD guys have given us strncat and strncpy, and a patch has been applied to glibc in August 2000.

    http://sources.redhat.com/ml/libc-alpha/2000-08/ ms g00052.html

    GNU/Linux programmers have a bad track record on this issue. Not to mention safer languages. Consider the little attention a mainstream language like C# has gathered in the community (I won't even mention other languages that achieve C-like performance such as SML or Common Lisp). People use C for everything, not just systems programming. The result you get to read at CERT. And let's not even mention formal methods...

    --
    Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    1. Re:buffer overruns by Anonymous Coward · · Score: 2, Funny

      ...and let's not mention that saying that you're not mentioning something is, in fact, mentioning it.

    2. Re:buffer overruns by EsbenMoseHansen · · Score: 2, Informative

      While I agree with the sentinent, I cannot but hasten to warn that strncpy is evil, and it should almost never be used. Why? It doesn't zero-terminate, so it might turn a C-string into a non-C-String, with hilarious results.

      I assume several C-String libraries must have been designed and built over the years. But I none seems to have prevailed for whatever reason. Which is a bloody shame, because C's string (mis)-handling are a trategy, so messy and unclean in such a nice & clean language. I wonder why?

      (And yes, I'm perfectly aware why strncpy does what it does, I just wish they had called it fillrecord or something sensible instead.

      --
      Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.
    3. Re:buffer overruns by Type-R · · Score: 3, Informative

      They also gave out strlcpy(3) , but the glibc crew decided to go with the weaker more broken strncpy, making many people reimpliment it themselves. Unfortunatly egos won out over common sense.

  20. Now that's a first by __aahlyu4518 · · Score: 2, Funny

    Gnome 2.8 isn't older than 12 months and it is already included !! WOW

    Well... we'll still have to wait for Sarge to be released as STABLE. That could take another while... ;-)

  21. Re:Anonymous coward is confused by Todesmetall · · Score: 5, Informative
    So, sid will remain unstable and a new name for the testing branch will have to be decided (unless I missed something and that's already happened).
    The release after sarge will be called etch.
  22. Just run a chrooted Debian sid on stable by synthespian · · Score: 2, Interesting

    Here's what I do: on top of a stable Debian, I run a chrooted sid. Pronto! I get the best of both (ideally, I should be using testing instead of sid, since I'm not a Debian developer).
    My point being that you get the best of both worlds. It is ridiculously easy to set up a chroot jail in Debian. "Google and ye shall find."

    --
    Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
  23. Re:I have been waiting for this by Bigman · · Score: 2, Funny

    Yeah and I can't even get it to install on my Commodore PET.

    --
    *--BigMan--- Time flies like an arrow.. but personally I prefer a nice glass of wine!
  24. Re:Actually, they switch names... by Anonymous Coward · · Score: 4, Informative
    Uhmm... no. Sarge remains sarge, woody remains woody and sid remains sid. The new unstable gets a new name. I believe the pre-woody stables were called potato, slink, and hamm respectively

    unstable will always be called sid. i.e.:

    stable -> slink
    testing -> potato
    unstable -> sid

    stable ->potato
    testing -> woody
    unstable ->sid

    stable ->woody
    testing -> sarge
    unstable ->sid

    stable ->sarge
    testing -> etch
    unstable -> sid
    sid never changes.

  25. Re:I have been waiting for this by yermoungder · · Score: 2, Funny

    Well, there you go - I didn't have a spell-checker tool available to spot that bug! :-)

  26. As a Debian user myself... by Cyn · · Score: 2, Insightful

    I have to ask, who the hell runs stable on a desktop - and who would want to?

    If you want stability, testing provides plenty of it. If you don't want to update often - just don't update (often). If you really need rock solid core stability, but want newer desktop software - then run stable with apt-pining for testing or unstable, and only install what you know you want from testing/unstable.

    If you want a Debian desktop with frequent releases without all this crap, use Ubuntu :P

    Stable is supposed to be the rock solid hardware, and the only things that should change should be when there's a bugfix or security fix. The point of it is you can basically rest assured that when running updates, shit won't ever break. I don't mean just "PAM broke!" break, I mean config overwritten, changed options, etc. break. The system for all intents and purposes could be set to automatically grab updates and run for years.

    Disclaimer: I've never used Ubuntu, I'm a Debian man who suffers the trials of using apt-pining just like everyone else who wants this should have to!

    --
    cyn, free software and *nix operating systems enthusiast.
    1. Re:As a Debian user myself... by Technonotice_Dom · · Score: 2, Insightful

      I have to ask, who the hell runs stable on a desktop - and who would want to?

      If I was rolling out a set of desktops for corporate usage, stable is ideal. You don't want testing, which is prone to breaking dependancies (unless you're near freezing time), nor do you want unstable - you don't want to be troubleshooting brand new packages, you need them to just work.

      With stable, you have rock solid security support, very few if any changes, and all package upgrades are tested far more than any other repository before being uploaded. A corporate desktop wouldn't matter if it was still using Gnome 2.8 in two year's time, providing there aren't any huge revolutions...

  27. Re:I have been waiting for this by zemoo · · Score: 3, Informative

    From what I understand, this is due to the Kernel.

    In Windows, the application that is in the foreground (with the currently active window) actually gets a scheduler priority boost from the operating system.

    Under Linux, this is not the case.

    What does that mean? In Windows, interactive applications are snappier, but the background programs lag more. If you're running Windows, right-click on My Computer and hit Properties.
    Go to the Advanced tab and hit the Settings button under Performance. Go to the Advanced tab and the first option I believe controls this behaviour.

  28. Re:Actually, they switch names... by Xibby · · Score: 3, Informative

    unstable will always be called sid.

    Yes, go watch Toy Story...Sid is the unstable next door neighbor with a tendency to blow stuff up. Debian unstable is aptly named.

    --
    I'm going to go back in my box and will think within the limits of my box: MS Sucks Linux Good I read too much Slashdot.
  29. Re:You cannot prove the nonexistence of something by ssj_195 · · Score: 2, Funny
    It is mathematically impossible to prove the nonexistence of something. You can only prove the existence of something.
    I can prove that there are no integral solutions to x^n + y ^n = z ^ n for n > 2. Sadly, this post is too small to contain it...
  30. Re:I have been waiting for this by ssj_195 · · Score: 2, Informative
    Perhaps it is more a matter of application start-up time than overall responsiveness, I'm not sure
    I understand that most Linux GUI apps do indeed start up more slowly than their Windows counterparts, due to the fact that they must be dynamically linked(?). Pre-linking apparently speeds start-up time considerably. Gentoo is supposed to have excellent support for pre-linking apps (which must be fully recompiled whenever one of their compent libraries is updated, in contrast with the dynamic(?) linking model).
  31. Re:I have been waiting for this by Jason+Hood · · Score: 3, Interesting

    Its not a troll, its a valid complaint for those who choose to not ignore the current problems in gnome2.8.

    I like gnome2.8 and use it at home for the family. For that use, its unmatchable, even against windows. I use KDE3.3 at work for development.
    Here is what I have personally seen though in gnome2.8:

    When using the file chooser, it is possible for it to not use / as the root directory when browsing in some cases. It is also possible to click on your home directory on the left and completely lose access to the root filesystem. There is no back or up button so in that case the user must close the file chooser and reopen if they lose their spot.

    If I do an AltF2 in gnome 2.8 to run a program, it takes 4-5 seconds to get the second character. I know its trying to autocomplete but that is ridiculous. In KDE, is instantaneous.

    When I open firefox or even galeon, it takes 5-10 seconds to actually get a window. In KDE, konqueror loads in less than 2 seconds, everytime.

    If I want to add a base item to the main menu, I am SOL in gnome.

    There are three different screens configuring CD actions when CD/DVD is put in the drive. Each one does something different and only a specific combination of options across all of them will make gnome do what I want it to.

    If you are using an app that utilizes the gnome filechooser and want to load a file from the local network, you are SOL unless you have previously created a network device/mount. There is no location bar that can be used to manually type in an address (for me ssh:// and smb://) on the fly. Sure grandma doesnt need this, but developers and power users sure do. Its not even an option.

    Why does gnome still show http source when doing a http://www.cnn.com from nautilus? I would think that this would at least open up your default browser and give you the website. I dont know why an everyday user would want to see the source from a website instead of the rendered website. This is probably due tot he fact that gnome believes file browsers and webbrowsers are two separate applications I imagine.

    Gnome needs to show either OSS or alsa, but not both (but support both). Its hard to determine which sound bar to use to get the appropriate sound level. When your kernel loads both modules. Sure I can disable one, but why cant gnome just choose one on the fly to use and stick with it.

    --
    Are you intolerant of intolerant people?
  32. Comment removed by account_deleted · · Score: 2, Informative

    Comment removed based on user account deletion