https://bugzilla.redhat.com/show_bug.cgi?id=1025095 --- Comment #2 from Ken Dreyer <ktdreyer@xxxxxxxxxxxx> --- As I understand it: 1) The alexandria application requires the goocanvas and gtk2 gems. 2) The upstream goocanvas gem has moved on to GTK3. 3) goocanvas 1.2.x is the last goocanvas version that supported gtk2. 4) alexandria cannot work with GTK3. 5) goocanvas has an active upstream, and alexandria does not. Do I have that right? Assuming the above statements are true, I'm wondering if we should have a "rubygem-goocanvas12" package instead? That would satisfy alexandria's dependency, while still allowing you to continue to package the latest versions of goocanvas in the main rubygem-goocanvas package. Otherwise, the roles are reversed: rubygem-goocanvas will be the "old" one, while rubygem-goocanvas2 will be the "new" one, and it could get even weirder when upstream releases version 3. What do you think? -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review