On second thought: gem2rpm *can* generate conflicts in this very situation.
Stephan On 30. April 2014 07:04:44 MESZ, Stephan Kulow <[email protected]> wrote: >Am 30.04.2014 00:49, schrieb Adam Spiers: >> Adam Spiers ([email protected]) wrote: >>> This looks like a fundamental limitation of rpm's version >requirement >>> system, and I can't think of a good workaround right now :-/ >> >> Well, s/workaround/solution/ - installing rubygem-net-ssh-2.6.6 from >> systemsmanagement:chef:10 is a valid workaround in this particular >> case. But I'm looking for something which applies generally to this >> problem class. >> >If you had this problem while writing a spec file, you would write: >Requires: foo >= 2.6.0 >Conflicts: foo >= 2.8 > >Unfortunately we can't generate conflicts. > >Greetings, Stephan > >-- >Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die >ganze Welt an Arsch offen hat, oder grad deswegn. >-- >To unsubscribe, e-mail: [email protected] >To contact the owner, e-mail: [email protected] -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
