Re: [opensuse-python] Test run of update checker on dlpy
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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, We plan to run them by timer once a week and provide resuts here. Same like the non-integrated packages report is sent here. The code for the checker is now at [1] https://gitlab.com/mcepl/dlp_che ck_version_PyPI. The goal for this tool is only to do the monitoring rather than manage the updates in the OBS. That step could be done by other tools (ie, the one you are having), but for now what I tried to update those diffs are massive and it does not make much sense to automate stuff. Cheers Tom Arun Persaud píše v So 09. 03. 2019 v 08:54 -0800:
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 -----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEdm4bBIAGRMvy+dWx5KJGjI7uO+gFAlyE6oMACgkQ5KJGjI7u O+gNOg//YL4u+IvfKQM5jrwl2/134H6Wqq4pO3g+wKlM453ltDksTjkkqyz7fhFQ Gcybpd3Tkn7ZtrlLP8ra+aU/f/EBdqQkmnZ3tY+b69EYRipSdHKTNQ0IDyA8Z+U9 GjH3nJEnItoGBeamdhbADDJmIsZ3MUd05zGQ5NWQcFcpzVdMQHbSey6xcTiOE9W6 R4BRc86nCAWx3U+B06kuo/VAPBKGF5XtsVN3o3cF2bfBPdYXlVv03D1Yd5ISt/Bu I5qCfRK4kRdvvNCNEQWpHPs+kZmWNpo1ax7w6MVtZ6YZnX7W2jleNGQIIn+K2y+I teAbeJUteI7ipEdZUsXWBZs80MIf/dR+PMzNnvrFdkvTyowr5Rhr5PHo4mzlN7/N TXUUVy0CWxstF//6GJA12lbI6LDqSnoe2vNa6wuVP8P3aCqk8u7pNPA6jt5RnRSc +G1upYjQkisdw6y6UPrNrgM4OpaCh/xPg6X04gZdhnMHNXlEONb0Fjz10R9sf6gm di7tEbN7ADZnnxawUDegpFuGUolzZ5NrWSpweAK644+ISmb9Lbbm9ialJ2TtP3GC qZ+srlH9MeCFJjDRMrPmQNPHetSzaNnVKIRAoYrErrMpDaa64b0jHBvvRvif2AMX ps5Tzoce/AfCvwmARCZahhXpy2dyaQxjC/ncgdqNylQ/8HsWKV4= =8BEw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-python+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-python+owner@opensuse.org
participants (2)
-
Arun Persaud
-
Tomas Chvatal