On 4/13/05, Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote: > but i thought that was the whole idea of a test release -- maximize > the stress, no? as long as you can handle the stress load. Watching someone snap like a steel beam under too much load..while educational.. isn't necessarily good for the person. The problems you are seeing with the postgresql packages.. is typical day-to-day rawhide issue. As packages lower in the stack get updated, packages that depend on them can go out of sync for a day or two, until those packages are rebuilt against the new dependancy. Its the nature of how rawhide updates are done.. there isn't a nightly rebuild attempt of everything..most night... and dependancies can become out of sync until more packages are rebuilt. This is probably the most common and most benign of all rawhide "features" I personally don't waste time filing this sort of thing or even searching in bugzilla for previous reports about this until this problem lingers for a couple of days... unless the is a immiment iso set release and then i hunt the developer down and poke them in the eye about it. Learning how to use yum's --exclude function as a workaround is a useful rawhide wrangling skill. -jef"as far as movies that you go to solely because your significant other wants to go see it aka date movies... feverpitch is exponentially more enjoyable than princess diaries 2.. so i'm told."spaleta