Hi, Gerard. I just realized I need a newer build of Unison - 2.32 - to sync with a machine running a different distro. I see from the -devel archives that you currently don't have enough time to maintain your packages. I'd like to ask you to make me a co-maintainer so I can do this, but obviously with the way you have unison packaged there's something of a wrinkle :). What was the initial reason for the 2.18 / 2.27 packaging split? Is there any reason to continue to package multiple releases? Should we just go back to having a single, 2.32-versioned 'unison' package, or should we bump unison227 to be 2.32, or add a unison232 package? Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
