On Tue, 2005-08-23 at 12:22 -0700, Peter C. Norton wrote: > On Tue, Aug 23, 2005 at 03:16:45PM -0400, seth vidal wrote: > > On Tue, 2005-08-23 at 12:11 -0700, Peter C. Norton wrote: > > > In 2.3.4, when I have an already-installed package that satisfies a > > > dependancy, and I try to upgrade packages, I'm getting a missing > > > dependancy. Specifically this is a file dependancy on > > > /opt/perl/5.8.0/bin/perl (I've got an outdated package that depends on > > > a perl in this path, and I've got a dummy package that satisfies this > > > dependancy by installing a wrapper. > > > > > > Has this behaviour been seen before? If more information is required > > > please let me know. > > > > you wouldn't happen to be using that through the yum shell in 2.3.4, > > would you? > > No, > > # yum groupupdate <GROUP> > > fails, while > > # yum groupremove <GROUP> > # yum groupupdate <GROUP> > > works. > > I'm having some trouble narrowing down exactly what's going on now, > though. > > If this is fixed in 2.4.0, or you suspect it is, I will upgrade. > Can you do two things: 1. run a yum -d5 groupupdate <GROUP> and save the output to a file then post a link to that file to this list OR file a bug and put the data in a bug report 2. run a yum -d5 groupremove <GROUP>; yum -d5 groupupdate <GROUP> where it works and save that output. thanks, -sv
