yum error

Ivan Gyurdiev ivg2 at cornell.edu
Tue May 17 10:26:58 UTC 2005


On Tue, 2005-05-17 at 03:16 -0700, Aaron Kurtz wrote:
> On Tue, 2005-05-17 at 05:41 -0400, Ivan Gyurdiev wrote:
> > > This isn't yum's fault, this is just what happens when you use rawhide -
> > > some packages get pushed out before their dependecies are properly met.
> > > This has been mentioned over and over again, and should probably be part
> > > of the Release Notes or something for test releases.
> > 
> > What safeguards are there to ensure that this does not happen in
> > Fedora-Updates, and why can't the same approach be applied to rawhide?
> 
> Why should it be? The point of rawhide and test releases is development,
> so what justifies slowing down what's pushed to rawhide?

I disagree - the point of test releases is not development - it's
stabilization. The point of rawhide may be development, but broken
dependencies are unnecessary, and scare away the beta testers.
A package which introduces dependency damage will not be tested,
until the dependency damage is fixed - so why is it even released
until that point?

-- 
Ivan Gyurdiev <ivg2 at cornell.edu>
Cornell University




More information about the fedora-test-list mailing list