On Mon, 2004-11-15 at 09:15, Axel Thimm wrote: > On Mon, Nov 15, 2004 at 08:33:45AM -0500, seth vidal wrote: > > On Mon, 2004-11-15 at 13:09 +0100, Axel Thimm wrote: > > > if a package foo providing bar1, bar2, etc. splits off some subpackage > > > like foo-bar2 (and the bar2 provide moves to that package) yum seems > > > to be unable to upgrade foo and pull in foo-bar2 to resolve the > > > migrated dependency (if another package depended on the bar2 provides). > > > > > > I am seeing this on FC3/x86_64 and belive that yum 2.0.x on <= FC2 did > > > not have this behaviour. > > > > > > Is this a feature or a bug? Should this be files against yum's > > > bugzilla? > > > > Can you provide a test case for this one? I'm having trouble following > > what you're describing. > > A split of this kind happened for instance with rpm -> rpm, rpm-libs. > > (foo=rpm, bar2=librpm-4.3.so, foo-bar2=rpm-libs) > > The failing package would depend on librpm-4.3.so (like say synaptic). > > I haven't tested it with rpm/synaptic itself, the example above is > just for visualizing the setup. Well when I did upgrades from fc2->fc3 that split occurred and I didn't have any trouble. -sv
