Shoot, sorry for the confusion. We are doing "yum -y update"... and it is still getting obsoletes. Our yum.conf does have the default config of obsoletes=1. My question though is this: is our "meta" package getting grabbed just because of its obsoletes? It isn't considered an update to any other package for any other reason. Perhaps I'm wrong, but I didn't think that obsoletes alone would be considered reason enough to grab something as an "update". Joshua On Mon, Jun 20, 2005 at 02:00:14PM -0400, seth vidal wrote: > On Mon, 2005-06-20 at 13:12 -0400, Joshua Jensen wrote: > > I have a package called "meta" in a package group in my repo. All it > > contains is an obsolete of package a". > > > > I have package "a" on my machine already. I didn't install the group > > that includes "meta", nor do I have an old version of the "meta" package > > installed. > > > > However, when I do a "yum upgrade" against said repo, I still get the > > meta package included in the yum update set. Why? Why does yum regard > > an obsolete to "a" to be an "upgrade"? Surely it shouldn't. > > read up on what 'yum upgrade' does. > > upgrade > Is the same as the update command with the --obsoletes > flag set. > See update for more details. > > > -sv > > > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxxxxx > https://lists.dulug.duke.edu/mailman/listinfo/yum -- Joshua Jensen joshua@xxxxxxxx "If God didn't want us to eat animals, why did he make them out of meat?"
