[2987] in SIPB_Linux_Development
Re: install report
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Sep 18 08:12:11 2000
Message-Id: <200009181212.IAA05831@egyptian-gods.MIT.EDU>
To: Camilla R Fox <cfox@MIT.EDU>
Cc: linux-dev@MIT.EDU
In-Reply-To: Your message of "Mon, 18 Sep 2000 02:32:15 EDT."
<200009180632.CAA01371@HOTASS-1.MIT.EDU>
Date: Mon, 18 Sep 2000 08:12:05 -0400
From: Greg Hudson <ghudson@MIT.EDU>
> Does this really work with an empty /var/athena/release-rpms? I
> don't actually understand how the upgrade knows which kernel rpm to
> try to install.
Given an empty release-rpms file and a PUBLIC=false machine, rpmupdate
will upgrade RPMs but will not remove any. (This is more or less
unintentional; the "meaning" of an empty /var/athena/release-rpms file
is that every RPM was added to the release during the update, which
just isn't so. But it does happen to work.)
The update knows which kernel rpm to try to install because rpmupdate
is magic and will translate <stuff>.i686.rpm to
<stuff>.{i586,i386}.rpm as necessary.
