Feature changed by: Adrian Schröter (adrianSuSE) Feature #307916, revision 3 Title: osc plugin for writing patchinfos Buildservice: New Priority Requester: Mandatory Requested by: Dirk Mueller (dirkmueller) Description: We need an externally accessible way to write a patchinfo and submit it as part of an update to Update:Test The ideal implementation would be a osc plugin that provides functionality similar to the internally available tool edit_patchinfo. It should be able to use the date provided by the build service. in its first iteration, it should not support the patchinfo validation steps that the internal tool does. Ideally it should write a "_patchinfo" file that is added to the current osc package working copy and can be submitted as part of osc submitrequest for an update. Discussion: #2: Magnus Boman (mboman) (2009-10-07 23:43:13) Can we get the format of the patchinfo described here, together with where the information will come from (ie, what can be fetched automatically from the package and what requires user input). That way, people can start working on it... :-) + #3: Adrian Schröter (adriansuse) (2009-10-08 08:24:54) + We should put this tight together to the (submit)request handling IMHO. + In this way we can avoid that the users have to do two different steps + (submit sources and create release request), instead of just doing this + in a extended way of the current submit requests. -- openSUSE Feature: https://features.opensuse.org/307916

Feature changed by: Adrian Schröter (adrianSuSE) Feature #307916, revision 7 Title: osc plugin for writing patchinfos - Buildservice: New + Buildservice: Done Priority Requester: Mandatory + Projectmanager: Mandatory Requested by: Dirk Mueller (dirkmueller) Description: We need an externally accessible way to write a patchinfo and submit it as part of an update to Update:Test The ideal implementation would be a osc plugin that provides functionality similar to the internally available tool edit_patchinfo. It should be able to use the date provided by the build service. in its first iteration, it should not support the patchinfo validation steps that the internal tool does. Ideally it should write a "_patchinfo" file that is added to the current osc package working copy and can be submitted as part of osc submitrequest for an update. Discussion: #2: Magnus Boman (mboman) (2009-10-07 23:43:13) Can we get the format of the patchinfo described here, together with where the information will come from (ie, what can be fetched automatically from the package and what requires user input). That way, people can start working on it... :-) #3: Adrian Schröter (adriansuse) (2009-10-08 08:24:54) We should put this tight together to the (submit)request handling IMHO. In this way we can avoid that the users have to do two different steps (submit sources and create release request), instead of just doing this in a extended way of the current submit requests. #4: Adrian Schröter (adriansuse) (2009-10-08 08:31:47) (reply to #3) It would be nice of course, if OBS would understand the release process (also copying the sources and binaries from project X to Y on accept). We could also create propper update informations for the installers in the bs_publisher code than, reading its informations from the _patchinfo file (_updateinfo or _releaseinfo is maybe a more generic name). + #6: Adrian Schröter (adriansuse) (2010-01-22 15:57:42) + osc patchinfo and api call is implemented in 1.7 -- openSUSE Feature: https://features.opensuse.org/307916