5 ms·

As a fellow day-job-using Ubuntu user, I'm with you. In fact, it's not just this release, I always wait a bit to upgrade, since the general consensus seems to b

As a fellow day-job-using Ubuntu user, I'm with you. In fact, it's not just this release, I always wait a bit to upgrade, since the general consensus seems to be that fresh Ubuntu's are often a bit touchy :)

regularfry 15y ago
Not only are fresh Ubuntus a bit touchy, but upgrading in-place has bitten me badly in the past. It's always a clean-slate install for me now.
- thenduks 15y ago
  Yea that too. I've heard bad things, but I've never even attempted it myself. Years of Windows has built up some serious negative reinforcement here :)
- kevindication 15y ago
  Apt is the only system I've ever felt fully comfortable with when doing upgrades. It was neither a problem under Debian nor Ubuntu. Do you have a tendency to make system changes that get in the way of the upgrades? (i.e., where has it gotten stuck for you before?)
  - regularfry 15y ago
    I've never had a problem with a Debian in-place upgrade; I've got servers that have been upgraded from woody through to squeeze without a hitch. Where I've had problems with Ubuntu, it's been around the desktop, and udev/hotplug integration. That being said, I've not given it a fair try for a few releases, so it's possible that in-place upgrades are better tested now, but I don't see the point of taking the risk. If it goes wrong, I'll end up reimaging anyway, so why waste the time?
  - mnutt 15y ago
    In the past I've found that if I installed packages that weren't in the main release I would sometimes run into gigantic dependency issues that I couldn't resolve without a clean reinstall.
  - nitrogen 15y ago
    I'm not the OP, but on my in-place upgrade to Natty today I had the nspluginwrapper installer die with a segfault. As a result, the update "failed" (only nspluginwrapper failed, really). I had to remove google-talkplugin to fix it (so really, the bug was in Google Talk, but apparently nobody at Canonical has Google Talk 64-bit installed to encounter this). So yes, seemingly-inconsequential system changes can interfere with upgrades.
- nolite 15y ago
  I have never NOT been bitten badly by an in-place upgrade
- thomas_codes 15y ago
  google-talkplugin is still broken on a virgin x86_64 squeeze.

regularfry 15y ago

Not only are fresh Ubuntus a bit touchy, but upgrading in-place has bitten me badly in the past. It's always a clean-slate install for me now.

thenduks 15y ago
Yea that too. I've heard bad things, but I've never even attempted it myself. Years of Windows has built up some serious negative reinforcement here :)
kevindication 15y ago
Apt is the only system I've ever felt fully comfortable with when doing upgrades. It was neither a problem under Debian nor Ubuntu. Do you have a tendency to make system changes that get in the way of the upgrades? (i.e., where has it gotten stuck for you before?)
- regularfry 15y ago
  I've never had a problem with a Debian in-place upgrade; I've got servers that have been upgraded from woody through to squeeze without a hitch. Where I've had problems with Ubuntu, it's been around the desktop, and udev/hotplug integration. That being said, I've not given it a fair try for a few releases, so it's possible that in-place upgrades are better tested now, but I don't see the point of taking the risk. If it goes wrong, I'll end up reimaging anyway, so why waste the time?
- mnutt 15y ago
  In the past I've found that if I installed packages that weren't in the main release I would sometimes run into gigantic dependency issues that I couldn't resolve without a clean reinstall.
- nitrogen 15y ago
  I'm not the OP, but on my in-place upgrade to Natty today I had the nspluginwrapper installer die with a segfault. As a result, the update "failed" (only nspluginwrapper failed, really). I had to remove google-talkplugin to fix it (so really, the bug was in Google Talk, but apparently nobody at Canonical has Google Talk 64-bit installed to encounter this). So yes, seemingly-inconsequential system changes can interfere with upgrades.
nolite 15y ago
I have never NOT been bitten badly by an in-place upgrade
thomas_codes 15y ago
google-talkplugin is still broken on a virgin x86_64 squeeze.