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.

58 of 207 comments (clear)

  1. Accepted/rejected packages list by Chocky2 · · Score: 4, Informative

    A comprehensive list of which packages were included and which were rejected is at http://people.debian.org/~joey/2.2r5/full.html

  2. Actually, it's not bugfixes by bconway · · Score: 4, Informative

    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?
    1. Re:Actually, it's not bugfixes by noahm · · Score: 2, Informative
      That's not true at all. For example, look at the changelog for bwbasic in 2.2r5:

      "* Recompile. Due to strange interactions with libc6, functions weren't interpreted, and the package was practically unusable. Closes: #108924."

      noah

  3. stable vs. unstable by dboyles · · Score: 5, Insightful

    I run Debian "unstable" on 3 out of the 5 boxes that I admin (personal use, not corporate). For the most part I prefer unstable because of the newer software that it allows access to. Some software isn't available in .deb form in the stable distribution ("gallery", for example, an online photo gallery system). Other software varies a lot between the stable and unstable distributions ("unstable" software being more advanced, usually). For the most part "unstable" is a misnomer.

    But... there are those times when something breaks. This is the reason you shouldn't use unstable on a production box. Earlier this week I worked out a KSpread spreadsheet that I needed for a meeting with an advisor. The day for my meeting came and KSpread wouldn't open up because of a conflict with the libpng version. To the best of my knowledge this hasn't been fixed yet. Others report similar problems. Needless to say I wasn't pleased, and I had to go to my meeting without the spreadsheet.

    Does that mean I'll stop using "unstable"? Nah. Should everybody use it? No way.

    --
    -- "Complacency is a far more dangerous attitude than outrage." -Naomi Littlebear
    1. Re:stable vs. unstable by reaper20 · · Score: 3, Informative

      check debianplanet.org for thee thread, i believe most of the libpng issues have been taken care of.

    2. Re:stable vs. unstable by mindstrm · · Score: 2

      This is what I don't understand.
      By what logic is using unstable for your email server bad?

      The only difference with unstable is that newer packages may break dependencies until they are fixed.. that's the only part of it that is 'unstable'
      For reliability, it's as stable as anything else.

      As for a mail server.. if you aren't securing things by hand, and configuring mail by hand in the first place, you are asking for it regardless of what distribution you are using.

    3. Re:stable vs. unstable by awptic · · Score: 3, Informative

      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
      To summarize what needs to be done though:

      rm -f /usr/lib/libpng.so.3
      ln -s /usr/lib/libpng.so.2.0.1.12 /usr/lib/libpng.so.3

      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.

    4. Re:stable vs. unstable by barawn · · Score: 3, Interesting

      Because in a cron job, you can shove "apt-get upgrade" (and some switch to get rid of the "Y/N") and all of the basic security stuff is done, good, kay, everything's great.

      You can't do that in a cron job for "unstable".

      Regarding the hand-securing thing, well, for the actual PURPOSE of the box, I agree with you - the mail should probably be configured by hand, etc., but not necessarily for EVERYTHING - especially for security holes, rather than stupid security issues. What if there's a security hole in wu-ftpd? (God, that never happens) In that case, "stable" is best, because "apt-get upgrade" will just fix that. Unstable you'd actually have to GO to each box, and make sure dependencies weren't screwed with.

    5. Re:stable vs. unstable by FlyingDragon · · Score: 5, Informative
      If you find stable a bit stoic and unstable a little wild, Debian has another distribution you may find just right: testing.

      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.

    6. Re:stable vs. unstable by dboyles · · Score: 2

      One example of another problem I had once with unstable (when Woody was unstable) was PHP breaking. I just have a little webpage for personal use, and the problem was fixed within a day or two, but it served to remind me why unstable shouldn't be used for critical apps.

      --
      -- "Complacency is a far more dangerous attitude than outrage." -Naomi Littlebear
    7. Re:stable vs. unstable by mindstrm · · Score: 2

      to each his own, but if I ever caught anyone in my company doing any automatic updates of servers from a cron script, I'd be mighty pissed off.

      I don't care *HOW* stable it is, you don't upgrade servers automatically. You upgrade them for reasons, knowingly.

      You should not rely on apt to fix your security problems.

    8. Re:stable vs. unstable by swillden · · Score: 2

      KSpread wouldn't open up because of a conflict with the libpng version. To the best of my knowledge this hasn't been fixed yet.

      You can fairly easily fix all of the problems caused by the libpng update just by recompiling the packages with problems. Luckily, this is very easy to do. Log on as root and run:

      apt-get -b source kspread && dpkg -i *.deb

      apt-get will download, unpack, configure and build the softare, producing .deb files. dpkg -i will install them.

      After downloading, dpkg-buildpackage may complain that you don't have some of the required development packages installed. Just look at the list, apt-get install them all and run the above commands again.

      Note that in this case it will take a while, because you're actually going to rebuild/reinstall all of koffice.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    9. Re:stable vs. unstable by Peaker · · Score: 2

      Last I checked, testing got none of the security fixes.

      Makes it a non-option for me.

      Fortunatly for me, I am very happy with unstable, and find almost all of unstable's problems trivial to fix, and if not, trivial to hack around.

  4. Woody by MoceanWorker · · Score: 3, Interesting

    why not just upgrade to Woody? even though it's classified unstable.. i've been running it and having no problems at all with it... there was a certain way to upgrade from 2.2 to 3 (i unfortunately forgot), but if you sign on to irc.openprojects.net, join #debian and message Apt.. it should give you a few simple steps on how to upgrade to Woody...

    --


    "The ones who dont do anything are always the ones who try to pull you down" -- Henry Rollins
    1. Re:Woody by barawn · · Score: 4, Informative

      Actually, isn't "unstable" 'Sid'? I think 'Woody' is the "testing" release.

    2. Re:Woody by barawn · · Score: 2

      Actually, don't you have to do apt-get dist-upgrade for Woody from Potato? Not that I'm sure what 'dist-upgrade' does over 'upgrade'...

    3. Re:Woody by nomadic · · Score: 2

      'Why' are "we" talking 'like' this?

    4. Re:Woody by Gannoc · · Score: 4, Informative
      it should give you a few simple steps on how to upgrade to Woody...

      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.

      ;)

    5. Re:Woody by nomadic · · Score: 3, Informative

      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.

    6. Re:Woody by nomadic · · Score: 2

      Well, I was being slashdot-specific. Maybe someone should suggest that they put in and ; the gods know we talk about commands enough...

    7. Re:Woody by nomadic · · Score: 2

      Errr, that should read "Maybe someone should suggest they put in and ".

    8. Re:Woody by barawn · · Score: 2

      Teletype would make a lot more sense, I agree, (or the kbd tag, as others have pointed out) but I don't enter Slashdot comments in HTML - I typically leave them in plain old text. It makes it feel more like email, I guess (and if anyone suggests HTML email, I will refer them to my secretary, /dev/null).

      I've never been able to figure out single/double quotation marks, because I have literally seen entire BOOKS where they used single quotation marks instead of double quotation marks and vice versa.

  5. ssh v1? 1:1.2.3-9.4? by Odinson · · Score: 2, Interesting
    Will stable debian use ssh version 2 yet?

    Or did they rig their package so protocol verion 1 doesn't allow your box to hacked?

    Or are they just ignoring the huge exploit problems with the ssh1 protocol?

    1. Re:ssh v1? 1:1.2.3-9.4? by Colm@TCD · · Score: 3, Informative
      The middle one. Although potato has ssh 1.2.3, it's been patched so as not to be vulnerable to the ssh1 exploit.

      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.

    2. Re:ssh v1? 1:1.2.3-9.4? by noahm · · Score: 3, Informative
      Read the changelog for the ssh package. /usr/share/doc/ssh/changelog.Debian.gz. It is still SSH protocol 1, but the ssh daemon is patched to address recent remote exploit vulnerabilities. There are no known vulnerabilities in the version of OpenSSH included with Debian 2.2r5.

      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

    3. Re:ssh v1? 1:1.2.3-9.4? by Odinson · · Score: 3, Interesting
      First, thank you both.

      I was planning on doing exactly that.

      Do Debian's rules explicitly disallow a major version upgrade? Even for security reasons? I believe that boxes are already being exploited. Even if there isn't example code, I'm sure there will be soon. Why wait?

      It seems to me that widespread use and critical funtion of this package might warrant a major version upgrade on a stable release.

      Please understand that I have infinate gratitude toward the Debian people, but I also have broadband Debian stable boxes.

      and a side note... Someone actually modded the top parent down. WTF? Even if I was wrong those are completely on topic questions. Someone metamod that guy.

  6. Re:Why dont you update the damm Kernel by reaper20 · · Score: 2, Troll

    You know, you can install 2.4 on any debian box. Sure, it's not as easy as installing an rpm, but I'd rather install a new kernel by hand than try to fix RPM Hell.

  7. Debian unstable by ShecoDu · · Score: 2, Informative

    For those of you who would want to use debian unstable, update your /etc/apt/sources.list to be like this, debian unstable is not really unstable after all, its just that the list might be broken some times:

    # See sources.list(5) for more information, especialy
    # Remember that you can only use http, ftp or file URIs
    # CDROMs are managed through the apt-cdrom tool.
    deb ftp://ftp.us.debian.org/debian unstable main contrib non-free
    deb ftp://non-us.debian.org/debian-non-US unstable/non-US main contrib non-free

  8. Debian is odd by bytor4232 · · Score: 2, Interesting
    This is the EXACT reason I stopped using Debian. They need to get a clue. Debian is a great distro, don't get me wrong, but they need to stop screwing around with Potato and get Woody released. Potato is NOT a new relese, instead its a rerelease of an old codebase that is getting tired. Potato is getting on several years old, Debian needs to let it go.

    Here is an example. I am not a KDE advocate or anything (Window Maker for me) but I noticed that all versions of KDE is still listed as "testing" or "unstable" while GNOME 1.0.55 is listed in the "Stable" package section? I'm sorry, but KDE 2.2.x is ALOT more stable that "October" GNOME which was released in 1999! Debian needs to get with it. Stability is one thing, but this is bordering on the rediculous. October GNOME was not all that stable, and KDE 2.2.2 is one of the most stable desktops out there.

    --
    -- 4 8 15 16 23 42
    1. Re:Debian is odd by mbanck · · Score: 2, Informative
      Debian is a great distro, don't get me wrong, but they need to stop screwing around with Potato and get Woody released.

      chill. Most Debian Developers are working for woody, alright? It's just that some of us do release security updates, if you don't mind. And then _one_ person (joey) does point-releases by getting all the security stuff and critical bugfixes together. No big deal. No Debian Developer is working on stable packages apart from security updates, OK?

      Here is an example. I am not a KDE advocate or anything but I noticed that all versions of KDE is still listed as "testing" or "unstable"

      That might be because QT was not released under the GPL before the release of potato, hmm?. And no, we won't let something as big as KDE into stable. The biggest thing that went in was Mozilla-M18 (the original version in potato was Mozilla-M12 or something, go figure)

      October GNOME was not all that stable, and KDE 2.2.2 is one of the most stable desktops out there.

      Of course, but october GNOME was all that was there by the time of the release. AFAIK, there are unofficial KDE-packages for potato available on the web, but if you want to run KDE, then you're better off with woody or sid anyway. I hope your concerns are adressed by now. We know that we release too infrequently, we got the stuff in place to do this more often by now, so hope for the future, sorry. This point release is necessary for everybody who needs to install _rock-solid_ software without security issues, not for the latest whistles. Besides, this is probably not worth mentioning on ./ anyway.

      Michael

    2. Re:Debian is odd by Glytch · · Score: 2

      Ah, yes, the "grab the binary package with apt-get, don't you dare compile from source!" open-source way?

  9. Re:Why dont you update the damm Kernel by nickjennings · · Score: 2, Informative

    you don't need to install the 2.4 kernel from source on a Debian system (stable). Use the 2.4 packages built for stable maintained by Adrian Bunk.

    Add the following line to your /etc/apt/sources.list

    deb http://people.debian.org/~bunk/debian potato main

    run dselect and update your package list, then make sure you select one of the 2.4 kernels, it will upgrade several base packages to support the new kernel, but it works absolutely perfect!

  10. Yes! Use the debian testing distribution. by brlewis · · Score: 3, Informative

    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.

  11. Debian Install Problems. by ImaLamer · · Score: 2

    I downloaded, and burned the last release onto CD.

    Now I'm having some install problems. The box I'm trying to install to has no floppy drive. The installation tries to find the 'rescue' disk and prompts me to put it into the floppy drive.

    This of course is before the installation of the base system. I've looked on the disc[from the prompt], and no image anywhere. So the install farts out and that's it.

    I've tried to find a work around on irc, newgroups and the like. No one else seems to have this problem. As I understand it the 'disk' is actually what the CD is booting from.

    Does this release fix this problem? Has anyone else had this problem? No one else seems to have this problem... that I've talked to.

    I hate to be offtopic here... and I don't mean to point out a problem, and this isn't a troll etc.

    I just hope the /. community has some insights.

    I really want to get this RPM'n piece of crap off my box. apt-get packagename is so much easier when the only interface with the box is my Doze machine.

    TIA

    1. Re:Debian Install Problems. by NetJunkie · · Score: 3, Insightful

      The only time it asks for the rescue disk is when installing the kernel and base setup. You need to tell it to get it elsewhere when it asks. I'm setting up Debian on a server RIGHT NOW and just installed it without the rescue disk. Set up networking first and then have it get it off the Debian site. Or you should be able to just point it at the CD.

    2. Re:Debian Install Problems. by Phexro · · Score: 2

      if you are talking about the kernel prompt, which is something along the lines of `Insert floppy to be used as root...', the cd you made is broken.

      the 1.44mb floppy images have seperate rescue/root disks. the cds should be booting from the 2.88mb images, which have a single rescue disk with the root ramdisk on it.

      fwiw, i've _never_ seen this on any debian installation from official media. i've been using debian since 1.3 was released.

    3. Re:Debian Install Problems. by ImaLamer · · Score: 3

      if you are talking about the kernel prompt, which is something along the lines of `Insert floppy to be used as root...', the cd you made is broken

      No, no... since you've installed and used debian so many times you would know I'm speaking of the step between partitioning and installing the base system.

      Simply, the CD boots, I can partition and all. But the install craps out when you are trying to install the base system. Basically I've got a CD worth nothing... coaster.

    4. Re:Debian Install Problems. by ImaLamer · · Score: 2

      Thank you... as much as I love debian and linux in general you've finally put me into that category of people who think the support problem in the linux world is arrogance.

      This [and the last post] is the only time I've gotten a bad attitude about this problem [or any other problems].

      Once again though, it's not the 'root' floppy it asks for, it's the rescue floppy it asks for. Just to check I've burned the CD again 3 times all 3 times a different way.

      But please, let's be fair. Your attempt wasn't honest enough as it comes no where close to my problem. I'm sorry that you didn't help and that I've offended you because I told you it didn't.

      No where though did I resort to name calling. You are the one who added the "why don't you try again after you've passed puberty?". This is civil conversation? And for what reason did you deduce I've not passed puberty?

      That's simply childish. I felt belittled by the fact that you acted as if you were supreme computer god [Nick Burns is that you?] because you've used debian since way back when, and I'm nothing because I haven't.

      Thanks.

    5. Re:Debian Install Problems. by ImaLamer · · Score: 2

      [not complaining]
      I got the CD from debian, no where else. Both times.
      [/not complaining]

      I'm simply a home user, who loses his linux install at least once every three months. My fault everytime. Sometimes I just go with something else.

      When I'm serious I plan to fully support linux financially. I've bought two [don't make fun] Mandrake sets, and even a RedHat box set a long time ago.

      It's not that I feel as if the software isn't worth the money, or I want to use it because it's free as in beer free. Simply: I don't have the money. [or any money]

      As I can/could tell the 'community' was also filled with some people who share my situation. I'm a hobbiest, and an advocate. Sorry I can't afford to put cash on the table.

  12. Re:does it still have that installer? by barawn · · Score: 2, Interesting

    Debian will use alien to convert RPMs into .debs for the LSB requirement.

    There's an old phrase regarding Debian - and that's that the installer is so bad because you only ever need to install once.

    That being said, the Potato installer is not maintained anymore - there's a brand new installer for Woody (Debian 3.0).

  13. Re:Potato by FatRatBastard · · Score: 2

    PRODUCTION SERVERS.

    My own workstation is testing/woody, as are most things at home. But test/production servers I leave a Potato because they're configured to do certain things, and I would rather not update stuff (beyond security updates... add that security line to your sources file) on a continous basis, and I want them to be rock solid.

    I'd argue that the VAST majority of home/workstation folks are on at least woody, but there are very good reasons/situations to keep boxen off the bleeding (or in woody's case scabbed over) edge.

  14. what about... by MSG · · Score: 2

    Conspicuously missing from the list of updates is glibc. Since Red Hat released a security update for the revision used in Potato, I'm assuming that Potato is also vulnerable to the heap corruption bug in glibc's glob() function. The fix is simple, so where's the update? AFAIK, the only major distributions that haven't addressed this problem are Debian and Slackware.

    1. Re:what about... by Glytch · · Score: 2

      Actually, Slackware *did* release an update. It was on their security mailing list a few days ago.

  15. Actually, it is bugfixes (and more) by hal9000 · · Score: 4, Informative

    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
  16. Re:And I just put 2.2r4 on yesterday.... by JWhitlock · · Score: 2
    That shouldn't happen. I love Debian so much that when I hear of someone with a problem like this, I somehow feel personally responsible.

    I'd offer you help, but if you don't have time to help yourself, you probably don't have time to get help from someone else (as that might take longer). I'm so sorry you're having problems with what I believe is the best Linux distro out there.

    I agree - it makes me a bit of a whiner to complain but not be able to do anything about it.

    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?

    Do these questions make it obvious that there is some newbie book or documentation that I should be reading?

    The biggest problem I have is that this is a P1-100 box, which takes about 3 hours to re-compile the kernel, AND it's my firewall/router, so I lose much of my ability to read net sources when it's down. The current bastardized system is ugly and doesn't do everything I want, but at least it works.

  17. Re:And I just put 2.2r4 on yesterday.... by ThorGod · · Score: 2, Informative

    You update /etc/apt/sources.list to whatever distribution you want to upgrade to, and run apt-get update ; apt-get upgrade.

    --
    PS: I don't reply to ACs.
  18. Re:Why dont you update the damm Kernel by reaper20 · · Score: 2

    Wow, that is awesome, thanks for pointing it out. Is there something like this for Woody?

  19. Re:Debian sucks nuts by barawn · · Score: 3, Informative

    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.

  20. Re:Why dont you update the damm Kernel by damiam · · Score: 2

    Ummmm... Woody already has kernel 2.4 in the base distribution.

    --
    It's hard to be religious when certain people are never incinerated by bolts of lightning.
  21. Bad joke time by Scoria · · Score: 2, Funny

    Perhaps you should use the "Viagra" beta boot disks. Much more efficient, I've heard.

    --
    Do you like German cars?
  22. Where is Woody? by RelliK · · Score: 3, Interesting

    The big question is why Woody still has not been released? I thought going to unstable/testing/stable model was supposed to speed up release cycles. Apparently not.

    --
    ___
    If you think big enough, you'll never have to do it.
    1. Re:Where is Woody? by bfree · · Score: 2

      It alway's seemed to me that the proposed changes aren't really for any release, they are changes which will evolve the way the project exists! Think of it this way, since testing has existed it has slowly filled up to reasonable proportions. Soon it will become a full new distro by going through a final freeze. Throughout the entire freeze process (less time than testing has existed) new packages will appear in unstable, and some will make it into testing. After woody is released, their will be three complete Debian distros. Stable will be the current woody (which will be a freeze length out of date). Testing will be those nearly bleeding edge packages which appear to be ok, and unstable will still be bang up to date. The key is that the testing process is about ensuring that a stable release from now on will be only a freeze length out of date, and that the freeze cycle can become a continuous process (instead of an arbitrary affair). After woody (the next stable release) new stable releases will form nearly instantly and be frozen out leading to a great development AND user environment for both guru's and grannies. Testing is about evolution, and I for one cannot wait to see how the Debian devlopment process will benefit from it (I think projects like DeMuDi will find it helps them to fork and freeze out trees for specific applications).

      --

      Never underestimate the dark side of the Source

  23. Re:is being fat okay? by Faceprint · · Score: 3, Informative

    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.

  24. Re:And I just put 2.2r4 on yesterday.... by steveha · · Score: 4, Informative

    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
  25. Re:Debian sucks nuts by steveha · · Score: 2

    Hey, maybe next time you can do your homework instead of complaining about things you don't understand.

    Debian "stable" is famous for being out-of-date. It is also famous for being stable. The two somewhat go together, since Debian doesn't have paid full-time people hammering together updates.

    Potato was frozen when the kernel was at 2.2 and Xfree86 was at 3.x. If you want to run Potato, you can get packages for Xfree86 4.1.x and kernel 2.4.x; if you want the latest cutting-edge stuff, all you have to do is update your system.

    To update your system:

    edit your sources.list to point to a mirror of "unstable", then run "apt-get update", then run the command "apt-get dist-upgrade" over and over until it reports that all packages were installed.

    I hope this helps, and maybe next time you won't shoot your mouth off so obnoxiously.

    For the love of god... upgrade stable.

    Oh gee, what a great idea. Debian wasn't planning to upgrade stable, but now that you suggested it, I'm sure they will get right on it.

    Sarcasm aside, if you had taken even a little while to read the debian.org web page, you might have found out that "Woody" is in the middle of a "freeze" process, which will take time... but when it is done, it will become the new "stable" branch.

    And apt... what a joke

    Actually, it's not a joke. It's one of the best things about Debian, and if you don't like it, maybe you should be running Red Hat. (Red Carpet does some of the same things as APT, but you may wind up having to pay money every month to use it. APT is always free.)

    If you want a menu front-end to APT, you have many choices. I like aptitude ("apt-get install aptitude" if you want to try it) but there is also gnome-apt and others.

    Your attitude sucks. You ought to work on that.

    steveha

    --
    lf(1): it's like ls(1) but sorts filenames by extension, tersely
  26. The problem with Debian... by aussersterne · · Score: 3, Interesting

    [Okay, I'm prepared to lose four karma points over this, offtopic, flamebait, troll, overrated, all the way to -1, just because there are so many damn Debian cheerleaders here and moderation is so damn broken]

    The problem with Debian is that it's too stable. What I mean by that is that though Debian does feel very stable, the current release also feels about 5 years behind other Linux operating systems in many ways, while not being all that much more stable than Red Hat, Caldera, or Slackware.

    I run Debian on a couple of PowerPC-based Web servers so it's not like I've never used it. I'd run Red Hat or Slackware on them if I could, though.

    And dselect has to go. Is there a new installer/package selector coming in the next major release, or will Debian still be the ugliest and clumsiest Linux to install on the face of the earth? Way back at Slackware 2.x, its installer was pretty, powerful, automatable, and easy to use.

    Red Hat installs a lot of crap, but it's got a decent record of keeping up on updates in a reasonable amount of time (i.e. no lurking glibc bug) and most of the software around the net will run on it.

    Aside from the multi-platform abilities of Debian, I really see no reason to use it, especially as .deb packaging moves farther toward the standardization fringes...

    --
    STOP . AMERICA . NOW
    1. Re:The problem with Debian... by Peaker · · Score: 2
      As people always respond to this bogus, false FUD:
      Debian is NEWER than Redhat, and I won't even compare with Slackware, which I wouldn't call a distribution, as an installer and a bunch of precompiled tarballs are not a distribution.

      Debian unstable is more stable than Redhat's current, and contains a lot newer packages from my experience, and everyone else who used both.
      Not to mention that Debian's much saner file system hierarchy standards, configuration defaults, alternatives system, package managers and packages' quality are much better.

      Yes, Debian's installer sucks, but if you're going to choose a distribution on the basis of its installation process, which occurs once, rather than the basis of use, which is what you do with it forever, then go ahead and use Redhat, Mandrake, or any of those nice installers.

      As for dselect, you're living in the past. Nobody uses dselect.
      Whenever I install Debian, I choose (6) and quit dselect immediately when its run. I don't see dselect ever again.

      There are MANY alternatives to dselect, you just weren't looking:

      apt-find

      aptitude

      kpackage

      gnome-apt

      and ofcourse, apt-get

      Aside from the multiplatform abilities, I see reasons to use Debian:

      Stable, good quality packages, that all come from a centralized source that makes sure they work well together, have a decent and secure default configuration, and just require no hassle to manage, install, and upgrade.

      A great bug tracking system to make sure all bugs are known by Debian, the authors, and anyone else involved

      Great package managers (See above list), and really amazingly smooth upgrade-ability

      The most stable distribution, assuming you use stable, and the newest assuming you use unstable

      And many more...

  27. Re:Debian on 68k Mac by saintlupus · · Score: 2

    I ran Debian briefly on a Mac Quadra 950 I had kicking around - it was all right, but being more of a BSD guy, I preferred NetBSD.

    I actually installed NetBSD on the very same machine you're asking about, a Q700. Go to my site (www.roadflares.org) and check in the "hardware" section for details.

    --saint