[Ubuntu Wiki] Update of "Bugs/Patches" by eapache

[Ubuntu Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The following page has been changed by eapache:
http://wiki.ubuntu.com/Bugs/Patches?action=diff&rev1=32&rev2=33

The comment on the change is:
Cleaned up the "Bugs with patches" sections a little.

------------------------------------------------------------------------------
  
  = Patches in Launchpad =
  
- Attachments that are patches can be flagged in the Launchpad bug tracker, which then makes them show up in search results and on other reports.  Attachments to bug reports appear in the attachments portlet on the right hand side of a bug report.
+ Attachments that are patches can be flagged in the Launchpad bug tracker, which then makes them show up in search results and on other reports.  Attachments to bug reports appear in the attachments portlet on the right hand side of a bug report. Attachments which are flagged as patches have a special icon of a pair of Band-Aids beside them.
- 
- {{attachment:attachment-portlet.png}}
- 
- The third attachment has a star by it, which indicates that this attachment is flagged as a patch.  However, these stars do not normally show up in Launchpad, they require the [[ http://bazaar.launchpad.net/~gm-dev-launchpad/launchpad-gm-scripts/master/files | lp_patches ]] Greasemonkey script.  You can install the script by clicking the green download arrow on the right hand side if you have greasemonkey installed.
  
  Notice the "edit" link next to each attachment, it will take you to the following page:
  
@@ -125, +121 @@

  Bug reports that have attachments should be examined to see whether or not any of those attachments are patches.  If an attachment qualifies as a patch it should be flagged as one.  When flagging attachments as patches comment on the bug indicating that the attachment was flagged as a patch and why this is important.  A possible reply:
  
  ||<tablestyle="background-color: #eee"> Looking at the attachments in this bug report, I noticed that an attachment was not flagged as a patch.  A patch contains changes to an Ubuntu package that will resolve a bug and this attachment is one!  Subsequently, I've checked the patch flag for it.  In the future when submitting patches please use the patch checkbox as there are some Launchpad searches that use this feature.  You can learn more about the patch workflow at https://wiki.ubuntu.com/Bugs/Patches. ||
-  
- Additionally, one could incorporate the patch into a debdiff for the package in the development release of Ubuntu or apply the patch to a bzr branch of the package and link the branch to the bug report.
  
- == Bugs with patches ==
+ == Bugs that already have patches ==
  
  Bug reports that have attachments flagged as patches should have the patches reviewed to ensure that they are in fact patches.  If an attachment is incorrectly flagged as a patch when it is not one, unflag the attachment and comment on the bug report indicating that the attachment is not a patch and why it is important for them to be identified properly.  A possible reply:
  
  ||<tablestyle="background-color: #eee"> Looking at the attachments in this bug report, I noticed that one was flagged as a patch incorrectly.  A patch contains changes to an Ubuntu package that will resolve a bug, since this was not one I've unchecked the patch flag for it.  In the future keep in mind the definition of a patch.  You can learn more about what qualifies as a patch at https://wiki.ubuntu.com/Bugs/Patches.  Thanks! ||
  
- In the event that it is not a debdiff one could incorporate the patch into a debdiff for the latest release of Ubuntu or apply the patch to a bzr branch of the package and link the branch to the bug report.
+ == Bugs with verified patches ==
  
+ As mentioned above, patches can come in several different forms. If the patch is not a debdiff one could incorporate the patch into a debdiff for the latest release of Ubuntu or apply the patch to a bzr branch of the package and link the branch to the bug report.
+ 
- If an attachment is a debdiff and applies to a recent version of the package the bug report needs to be [[ SponsorshipProcess | sponsored ]] to the appropriate archive.  This is done by subscribing (NOT assigning) the appropriate sponsorship team to the bug.     For packages in main and restricted the ubuntu-main-sponsors team should be subscribed.  For packages in the universe and multiverse repositories the ubuntu-universe-sponsors team should be subscribed.  You can view their queues at [[ https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-main-sponsors | main-sponsors ]] and [[ https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-universe-sponsors | universe-sponsors ]].
+ If a patch is a debdiff and applies to a recent version of the package the bug report needs to be [[ SponsorshipProcess | sponsored ]] to the appropriate archive.  This is done by subscribing (NOT assigning) the appropriate sponsorship team to the bug.     For packages in main and restricted the ubuntu-main-sponsors team should be subscribed.  For packages in the universe and multiverse repositories the ubuntu-universe-sponsors team should be subscribed.  You can view their queues at [[ https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-main-sponsors | main-sponsors ]] and [[ https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-universe-sponsors | universe-sponsors ]].
  
  Find out more:
   * How to [[Bugs/HowToFix|fix bugs]]
   * What [[UbuntuDevelopment/Patches|makes a good patch]]
+  * How to work with [[PackagingGuide/Complete#Patch%20Systems|patch systems]]
  
  = Resources =