Hi I'm interesting on how and where you run these checks. I wrote my own a while ago (https://github.com/arunpersaud/dlp3-update) that I use to check for updates on dlp. Features that I added are: * check dlp vs pypi * ignore packages that have an existing SR * keep track of changelog locations for packages * branch packages for updates, print out changelog location, update the spec file to the new version, and add a template to the .changes file (I also have an .changes emacs mode to make formatting easier) * check build status of packages that I'm working on * create SR for packages once they are done * do some error checking on spec files * keep a whitelist of packages I'm interested in (including their dependencies), so I can focus on updates for those packages (dlp is too big;) * keep a blacklist of packages that I'm not interested in * hacked it to work with subprojects For me that makes creating SR relatively easy. Would be happy to integrate these features into some other project, if you have something in mind, but when I started submitting to dlp there was nothing available, so I wrote my own (which is somewhat organically grown and I could clean things up if needed, but it works for me ;)) Arun -- To unsubscribe, e-mail: opensuse-python+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-python+owner@opensuse.org