strange rpm behavior in attempt to circumvent up2date

[jurvis lasalle]

i'm kickstarting a lab with an installation tree on an nfs share.  
rather than use up2date, i thought i'd patch the installation tree by 
hand after using it on one machine and saving the rpms.  that failed 
due to dependency information, so i tried 'rpm -Uvh `cat 
/file/containing/list/of/patchrpms`' in a post-installation script.  
This should go through the 50 or so patches and install them to meet 
the dependencies (as recommended here 
http://www.rpm.org/hintskinks/requires/). Instead i'm getting errors 
saying that the patches are already installed:

<snip>
[EMAIL PROTECTED] ~]$ rpm -q bash
bash-2.05b-20
[EMAIL PROTECTED] patches]# rpm -Uvh `cat patches.list `
warning: package bash = 2.05b-20.1 was already added, replacing with 
bash <= 2.05b-20.1
...
</snip>

any clue why rpm seems to not like this yet does like this:

<snip>
[EMAIL PROTECTED] patches]# rpm -Uvh bash-2.05b-20.1.i386.rpm
warning: bash-2.05b-20.1.i386.rpm: V3 DSA signature: NOKEY, key ID 
db42a60e
Preparing...                ########################################### 
[100%]
   1:bash                   ########################################### 
[100%]
</snip>

perhaps there's a better way to do this entirely?  what's the best way 
to get my installation tree up2speed without requiring all those damn 
entitlements?  or maybe that's the point...

tia,
jurvis lasalle
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list