Re: Question re Debian versions

From: Travis Casey (efindel_at_earthlink.net)
Date: 03/19/04

  • Next message: Nitebirdz: "Re: crontab jobs not running?" 
    To: debian-user@lists.debian.org
Date: Thu, 18 Mar 2004 21:53:45 -0500

    On Thursday 18 March 2004 21:35, Paul Johnson wrote:
    > "Monique Y. Herman" <spam@bounceswoosh.org> writes:

    > > I'm not sure that "less stable" is the right term, but "less usable"
    > > almost certainly is.
    >
    > backports.org is your friend.

    Here's a question for the more experienced folks: is "downgrading" from
    unstable to stable as easy as upgrading is?

    Several months back, I decided to "move up" to unstable, because there were
    some things I was using from testing to get more recent versions, and that
    was causing problems as increasing numbers of dependencies were also coming
    from testing, and I'd heard about testing not getting security fixes
    quickly.

    At the time, I hadn't heard of backports.org... so I decided to upgrade my
    system to unstable.

    For the most part, it's worked okay, except for a couple of times when I'd
    upgrade things and something important would stop working... but I'm not
    sure any more that I'm really that comfortable on the "bleeding edge". I
    *can* fix things -- I'm a Unix sysadmin in my day job -- but honestly,
    after spending all day fixing *other* people's computer problems, I want a
    system that just works at home.

    I know that at worst, I could back up /home and reinstall Woody, but I'd
    rather not have to redo some of the custom configuration I've done. Thus
    my question.

    Alternatively, how soon is Sarge going to become stable? I suppose another
    way to do it would be to switch my sources.list to point to Sarge and see
    if that would work -- I'd think that that would be an easier "downgrade".
    Then when Sarge becomes stable, I could switch my sources.list to point to
    stable, and start using backports.org for things I decide I want a more
    recent version of...

    Thoughts? Suggestions? 

    --
       |\      _,,,---,,_     Travis S. Casey  <efindel@earthlink.net>
 ZZzz  /,`.-'`'    -.  ;-;;,_   No one agrees with me.  Not even me.
      |,4-  ) )-,_..;\ (  `'-' 
     '---''(_/--'  `-'\_) 
-- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Nitebirdz: "Re: crontab jobs not running?"

    Relevant Pages

    • Re: Downloading Debian CD: "stable" or "testing"?
      ... > In general, unless there are security problems with a package, it will NEVER ... > be upgraded in Stable (until there's a new version of the whole Debian ... I run sarge on my local server. ... When stable changed from woody to sarge, there were upgrade problems. ...
      (Debian-User)
    • Re: upgrading from Sarge to Etch on an old PC...
      ... I could just wipe Sarge and install Etch from scratch to get around this ... One of the issues that is tested during a release is the upgrade path ... one of the main X packages in Sarge was xserver-xfree86. ... transitional package for moving from XFree86 to X.Org ...
      (Debian-User)
    • Call for upgrade testing
      ... with security support in place for sarge we hoped to be sending ... sort out one particularly hairy bug that was known to affect upgrades. ... Now that it's fixed in testing and we can accept upgrade reports without ...
      (Debian-User)
    • Sarge to Etch upgrade report
      ... I had been annoyed that shells in a konsole did not ... I'm happy to report that after the upgrade to Etch this works ... In other aspects of the upgrade, all I had to do was to replace "sarge" ... to install in batches only what it can, ...
      (Debian-User)
    • Re: VB6 vs VB .Net
      ... Maybe change, but not "upgrade". ... VB6 has a limited future potential, ... dotnet sycophant magazines and forums have finally started publishing articles ... it doesn't any more, switch to anything else, *anything at all* other than VB.Net ...
      (microsoft.public.vb.general.discussion)