[3561] in SIPB_Linux_Development
Re: Updates to layered install
daemon@ATHENA.MIT.EDU (Angie Kelic)
Sun Sep 30 20:08:17 2001
Message-Id: <200110010006.UAA14414@tomcat.mit.edu>
To: Alex Coventry <alex_c@MIT.EDU>
cc: linux-dev@MIT.EDU
In-reply-to: Your message of "Sun, 30 Sep 2001 20:02:05 EDT."
<200110010002.UAA02297@nerd-xing.mit.edu>
Date: Sun, 30 Sep 2001 20:06:58 -0400
From: Angie Kelic <sly@MIT.EDU>
The way I've seen layered installs fail with redhat version
updates is that the stock RedHat install has rpms in it that
the athena release does not have. Athena expects only the rpms
listed in /etc/athena/release-rpms to be installed. These 'extra'
rpms will never get removed since the athena updates don't generate
a complete listing of rpms installed on the machine to compare to
the list of release-rpms. In many cases these rpms do not cause
conflicts with minor athena updates but can and do with release
version updates. If you do a comparison of rpm -qa and the control
list of rpms when the install runs and cledan up the rpms that are
'extra' from teh stock install, you shouldnt run into the update
issues that tpyical layered machines see.
--Angie
>
>Hi, everyone. I installed keesh using my layering script to Athena
>9.0.14, and it updated cleanly to 9.0.15. I've heard some concerns that
>a layered install might have trouble updating to an Athena version which
>is based on a different version of RedHat than the Athena version of the
>original layered install was based on (e.g., 8.4.26 -> 9.0.15).
>However, I had a brief look at the update_ws script, and I can't see
>anything pertaining to such a case. Is it likely that if my layering
>allows updates within the set of Athena versions based on a given RedHat
>version, then updates to Athena based on later versions will also work?
>
>Alex.
