Douglas A. Tutty wrote:
On Mon, Mar 16, 2009 at 05:10:43PM -0700, NFN Smith wrote:
Thus, since the upgrade we wanted wasn't essential, we decided to not
bother with it then. However, we're now to the point where we need to
get the machine upgraded to lenny, so we need to figure out a way around
the problem.
What exactly is the problem that you're trying to avoid, i.e. what is
preventing you from doing a simple upgrade per the release notes?
As noted in the original post, we have several applications where we've
done quite a bit of localized configuration, and for those, we'd rather
upgrade them individually, and make sure they're all behaving correctly,
before upgrading the entire system. The primary thing is avoiding
having to be debugging one or more applications simultaneously on a
production server.
I need to do some checking, but removal of libc6-dev (and possibly other
-dev packages) before attempting an upgrade seems to have merit.
For the sake of a hard drive, why not install Lenny to a new drive (e.g.
with debootstrap) while still running your old version.
Not a bad idea, although impractical for this particular situation. The
server in question is in a co-lo facility that's two time zones away,
and I don't have easy access to the hardware.
I'll work through the all the recommendations suggested in this thread,
with a co-worker, although it's likely to be a week or two before we can
go after this one (a couple of things that are higher priority, at the
moment). I'll post further questions if they come up.
Thanks to all who contributed responses to my question.
Smith
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
