[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120404104212.GB19597@openwall.com>
Date: Wed, 4 Apr 2012 14:42:12 +0400
From: Solar Designer <solar@...nwall.com>
To: owl-users@...ts.openwall.com
Subject: Re: Upgrading to current gives dependency problem after kernel upgrade and boot
On Tue, Apr 03, 2012 at 11:26:52PM -1000, cpb@....log2.net wrote:
> You can't generally upgrade from one branch of Owl to another in-place with
> installworld.
Why, as long as you're not trying to jump over an Owl release, this is
supposed to work. For example, upgrades of Owl 3.0 to Owl-current, as
well as from Owl 3.0-stable to Owl-current, are supposed to work (with
"make installworld"). Moreover, even upgrades from older releases of
Owl should work as long as you upgrade to each intermediate release
first (e.g., 2.0 to 3.0 then to -current, not 2.0 to -current right away).
Of course, there may be issues with customized systems (including
systems that merely have additional RPMs installed, where an upgrade
might break those third-party RPMs' dependencies), but for clean
installs this should just work.
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
