Bernhard Rosenkraenzer wrote: > > On Tue, 26 Feb 2002, Levente Farkas wrote: > > > rpm -Fvh kernel-2*.i686.rpm glibc-2*.i686.rpm \ > > `ls kernel-*.rpm glibc-*.rpm|egrep -v "kernel-2|glibc-2"` > > rpm -Fvh *.rpm > > > > since it at least in the last few weeks, there is not any snapshot where > > this script run because of some dependenies. > > That's not a bug in rawhide, it's a bug in your script. If e.g. > kernel-2.4.17-0.19 requires modutils >= 2.4.10 (it does) and you don't > have it, the first command will fail... > > You may find this preferrable: > rpm -Fvh kernel*i6* glibc*i6* `ls *.rpm |egrep -v '^(kernel-2|glibc-2)'` you probably right, I'm just write the above script to demonstrate what I'd like to do, but as you understand what I wanna do, is a simple rpm -Fvh *.rpm of course before that we have to exclude the kernel and the glibc since it has more rpm with the same version number. > At the moment, you'll still get a couple of failed dependencies with this > one (mostly because the glib ABI keeps changing with every minor release). > rpm -e is sometimes a good solution. ;) rpm -e for what? the eg. currently glib abi is not compatible with a few packages and perl(MD5) <-> perl(Diggest::MD5) and ... > > IMHO it's not a too big request:-) and the qa department have to spend > > with it more than 5 minutes:-((( > > IMHO rebuild of depending applications should be automated when an > incompatible lib is built, but that's just me... that's your (rh) choise what to do, but if there is a binary rawhide than why don't you do so? or we have to always have to rebuild the whole rawhide? or try to select the depenendecy problems and just reuild those? that's much more time than you can rebuild the whole rawhide once! -- Levente "Si vis pacem para bellum!"
