Hi all, I am seeking some help here to solve a possible $subject. I have been trying to find a simple alternate solution, but I just can´t see it or it´s not obvious to me. This is the situation: srpm foo 1.0 ships 2 rpm´s bar and baz. bar has a daemon inside. due to upstream split: srpm foo 1.1 now ships only bar rpm without the daemon. srpm baz 1.1 now ships 2 rpm´s, baz (exactly as in version 1.0) and baz-something that contains the bar´s daemon from 1.0. In order to avoid upgrade issues, we need to make sure that bar 1.1 will pull in baz-something 1.1 (to retain functionality), at the same time baz-something requires bar 1.1 to operate at all. There is no requirement for a strictly versioned Requires: on both sides. baz-something Requires: bar >= 1.1, and bar Requires: baz-something (no version need since it´s a new rpm). >From local testing, the circular Requires works just fine, both in upgrades and clean install (tested with yum and manual rpm), but I don´t like it. Is there a better way to achieve this upgrade path? Thanks Fabio -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
