----- Original Message ----- > From: jpacner@xxxxxxxxxx > To: devel@xxxxxxxxxxxxxxxxxxxxxxx > Sent: Tuesday, July 1, 2014 5:41:45 PM > Subject: Re: Koschei - continuous rebuilds for packages > > Hi Michael, > > it sounds like a way how one could automatically handle library so-bumps > in rawhide. Idea discussed with hhorak, jzeleny, pingou and others was > to bump the library package, rebuild the dependency tree depending on > this library and if some of them fail, notify it's maintainer(s) and the > bumped library owner as well (email CC should be sufficient). If it > doesn't fail, we can automatically immediately rebuild it in non-scratch > environment. This'll save so much time and effort and also suppress the > need for finding maintainers of the library and notifying them about the > so-bump. > > So the question regarding Koschei is if one could schedule one-shot > build of a library package (preferably from CLI) and if one could get > the result of such run on CLI (allowing automation). The CLI tool would > be just thin wrapper around remote interface (JSONRPC/XMLRPC/...). Do > Koschei have such interface? I can consider it a a future feature, but I'm not sure whether I completely undestand the exact process. Detecting soname bumps and doing real rebuilds instead of scratch build should be possible. Koschei could automatically start rebuilding dependent packages AFTER you update the library in rawhide. But if you want to know what will break before you do the update then it will be more complicated, because Koschei will need to manage separate Koji tags and obviously first get permission to do so and I'm not sure whether relengs would be willing to make this happen. And for both solutions Koschei would need to get provenpackager-like priviledges to be able to bump the release. Regarding remote interface - there is none, but I can make it as soon as it's needed. I didn't have use case for it yet. > > Kind regards, > > -- Jan Pacner > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
