[Ubuntu Wiki] Update of "LibreOfficeBugWrangling" by penalvch

Ubuntu Wiki noreply at ubuntu.com
Thu Nov 22 17:44:41 UTC 2012


Dear Wiki user,

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

The "LibreOfficeBugWrangling" page has been changed by penalvch:
http://wiki.ubuntu.com/LibreOfficeBugWrangling?action=diff&rev1=18&rev2=19

Comment:
Adding request in Bug Reporting Template for apt-show-versions -r libreoffice* . Please see ## wiki comments for justification due to character limit in "Comment:" field.

+ ## 20121122 https://launchpad.net/~penalvch When one files a bug via apport against libreoffice via ubuntu-bug libreoffice and did not install the libreoffice meta package, the filed bug report tends not to provide enough information to triage appropriately. Ex. https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1080509 one has no idea what specific LO packages they actually have installed. Hence, asking for apt-show-versions -r libreoffice* in the bug reporting template section is an extremely helpful way an original reporter can provide information for triagers to work on the problem without asking for follow up information, and waiting for the response. However, not all packages in https://launchpad.net/ubuntu/+source/libreoffice have libreoffice in the name, so some will be missed (ex. ure, python-uno, etc.). If a more comprehensive command exists to provide all the installed packages for libreoffice with versions compactly, that does not contain the word libreoffice in the package name, please replace. I just have not come across a more relevant one. Thank you for your understanding.
+ 
  Available languages: [[https://wiki.ubuntu.com/LibreOfficeBugWrangling_it| Italiano]]
  
  <<Include(Debugging/Header)>>
@@ -14, +16 @@

  
  == Bug Reporting Template ==
  
- ||<tablestyle="background-color: #eee"> 1) lsb_release -rd <<BR>> <<BR>> 2) apt-cache policy libreoffice-writer <<BR>> <<BR>> 3) What is expected to happen in Writer is <PRECISE, STEP-BY-STEP INSTRUCTIONS>. <<BR>> <<BR>> 4) What happened instead is... <<BR>> <<BR>> I have the following extensions installed: lo-menubar, libreoffice-nlpsolver, ... <<BR>> <<BR>> WORKAROUND: Perform the following steps:...||
+ ||<tablestyle="background-color: #eee"> 1) lsb_release -rd <<BR>> <<BR>> 2) apt-cache policy <PACKAGE> <<BR>> <<BR>> apt-show-versions -r libreoffice* <<BR>> <<BR>> 3) What is expected to happen in Writer is <PRECISE, STEP-BY-STEP INSTRUCTIONS>. <<BR>> <<BR>> 4) What happened instead is... <<BR>> <<BR>> I have the following extensions installed: lo-menubar... <<BR>> <<BR>> WORKAROUND: Perform the following steps:...||
+ /!\ Please note the above 1) and 2) are terminal commands to execute, and post the results of when initially filing your bug report. Failure to follow this format will delay in your bug getting addressed as soon as possible. As well, you may need to install the package [[https://launchpad.net/ubuntu/+source/apt-show-versions|apt-show-versions]].
   * Please do not stack multiple issues into one bug.
   * Please do not complain about how long it takes to fix a bug, the severity of your bug is high so it should be fixed immediately, "I cannot believe it's not fixed...", etc. Especially, if you have not completed the relevant, below mentioned debugging procedures, let alone contributed code upstream. This type of behavior is unconstructive, irritating to others who read your E-Mail, and spammy. We all want to see every bug fixed as soon as possible! Naturally, bugs being fixed is limited to reproducibility and clarity of the bug report, the actual impact the bug has on the community, and available developer resources.
  



More information about the Ubuntu-bugsquad mailing list