[23675] in Athena Bugs
Re: Delaying an update and keeping rpms
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Aug 19 16:26:25 2003
From: Greg Hudson <ghudson@MIT.EDU>
To: Tom Cavin <cavin@mit.edu>
Cc: Athena Bugs list <bugs@mit.edu>, SIPB Linux Help <linux-help@mit.edu>
In-Reply-To: <16194.32681.751172.232485@lap1-wccf.mit.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1061324782.16712.235.camel@error-messages.mit.edu>
Mime-Version: 1.0
Date: 19 Aug 2003 16:26:22 -0400
The safe updates feature (the -c option to rpmupdate) insists on making
its own fresh copies into the copy area, because otherwise it would have
to worry about corrupt or truncated stuff living in the copy area.
You may be able to do what you want by copying the new RPMs onto the
target machine ("update_ws -n" will list all the changes made by a
particular update without making any changes, but it won't give you
filenames, unfortunately), hacking the release list file to point to the
copied RPMs, and running rpmupdate on the hacked release list.
Totally unsupported, of course.
