Part of lp.soyuz.model
|Function||get_bug_ids_from_changes_file||Parse the changes file and return a list of bug IDs referenced by it.|
|Function||get_bug_ids_from_changelog_entry||Parse the changelog_entry in the sourcepackagerelease and return a|
|Function||can_close_bugs||Whether or not bugs should be closed in the given target.|
|Function||close_bugs_for_queue_item||Close bugs for a given queue item.|
|Function||close_bugs_for_sourcepublication||Close bugs for a given sourcepublication.|
|Function||close_bugs_for_sourcepackagerelease||Close bugs for a given source.|
|Class||ProcessAcceptedBugsJob||Base class for jobs to close bugs for accepted package uploads.|
The bugs is specified in the Launchpad-bugs-fixed header, and are separated by a space character. Nonexistent bug ids are ignored.
ISourcePackagePublishingHistory and IPackageUpload are the currently supported targets.
Source publications or package uploads targeted to pockets PROPOSED/BACKPORTS or any other archive purpose than PRIMARY will not automatically close bugs.
'queue_item' is an IPackageUpload instance and is given by the user.
'changesfile_object' is optional if not given this function will try to use the IPackageUpload.changesfile, which is only available after the upload is processed and committed.
In practice, 'changesfile_object' is only set when we are closing bugs in upload-time (see nascentupload-closing-bugs.txt).
Skip bug-closing if the upload is target to pocket PROPOSED or if the upload is for a PPA.
Set the package bugtask status to Fix Released and the changelog is added as a comment.
ISourcePackagePublishingHistory close bugs mentioned in
ISourcePackageRelease, and a
corresponding changesfile object, close bugs mentioned in the
changesfile in the context of the source.
If changesfile_object is None and since_version is supplied, close all the bugs in changelog entries made after that version and up to and including the source_release's version. It does this by parsing the changelog on the sourcepackagerelease. This could be extended in the future to deal with the changes file as well but there is no requirement to do so right now.