rev 3770 - in trunk/packages: kdebase/debian kdenetwork/debian

[Christopher Martin]

Author: chrsmrtn
Date: 2006-05-15 15:02:42 +0000 (Mon, 15 May 2006)
New Revision: 3770

Modified:
   trunk/packages/kdebase/debian/changelog
   trunk/packages/kdebase/debian/konqueror.presubj
   trunk/packages/kdenetwork/debian/kopete.presubj
Log:
As per request, edit the new presubj files.


Modified: trunk/packages/kdebase/debian/changelog
===================================================================
--- trunk/packages/kdebase/debian/changelog	2006-05-15 02:06:35 UTC (rev 3769)
+++ trunk/packages/kdebase/debian/changelog	2006-05-15 15:02:42 UTC (rev 3770)
@@ -31,9 +31,9 @@
   * Add 'ru' debconf templates translation, thanks to Yuriy Talakan.
     (Closes: #367206)
 
-  * add konqueror.presubj (konqueror is responsible of 25% of the kdebase bug
-    reports) to ask for more precise bug reports, because missing the
-    primordial informations to make them of any use.
+  * Add konqueror.presubj (konqueror is responsible of 25% of the kdebase bug
+    reports) to ask for more precise bug reports, because often they lack the
+    fundamental information necessary to make them useful.
 
  -- Debian Qt/KDE Maintainers <debian-qt-kde at lists.debian.org>  Sun, 14 May 2006 08:49:25 -0400
 

Modified: trunk/packages/kdebase/debian/konqueror.presubj
===================================================================
--- trunk/packages/kdebase/debian/konqueror.presubj	2006-05-15 02:06:35 UTC (rev 3769)
+++ trunk/packages/kdebase/debian/konqueror.presubj	2006-05-15 15:02:42 UTC (rev 3770)
@@ -1,29 +1,30 @@
 Reporting a konqueror crash
 ---------------------------
 
-It is important when you report a konqueror crash to provide:
+When you report a konqueror crash, it is important to provide:
  * the exact steps to reproduce the crash (URL of the site, the exact
-   actions you performed, ...)
- * a useful backtrace of the crash.
+   actions you performed...)
+ * a useful backtrace of the crash
 
-To produce useful backtrace you must have kdelibs-dbg and kdebase-dbg
-installed. A backtrace full of "(no debugging symbols found)" is useless.
+To produce a useful backtrace, you must have qt-x11-free-dbg, kdelibs-dbg,
+and kdebase-dbg installed. A backtrace full of "(no debugging symbols
+found)" is useless.
 
-A bug that is not reproducible, or that lack the necessary backtrace, will
+A bug that is not reproducible, or that lacks the necessary backtrace, will
 be discarded.
 
 
 Reporting a rendering bug
 -------------------------
 
-Please provide the URL of the page that don't display correctly. explain
-clearly what you expect, and what you get.
+Please provide the URL of the page that doesn't display correctly. Explain
+clearly what you expect, and what you actually get.
 
 Small screenshots of the part that has a problem are of great help and can
 be attached to the bug report. Screenshots of the "correct" behaviour
 (taken on another graphical browser) may also help.
 
-Any bug that states "Site foo is not rendered correctly" with no more
-explanation will be discarded (even if at the report time the defect is
-obvious: it is too difficult to check if the defect is still there)
-
+Any bug that states "Site foo is not rendered correctly" with no further
+information will be discarded (even if at the time of the report the defect
+is obvious, with newer versions of KDE it can be hard to see if the defect
+is still present, since the error might have been subtle for all we know).

Modified: trunk/packages/kdenetwork/debian/kopete.presubj
===================================================================
--- trunk/packages/kdenetwork/debian/kopete.presubj	2006-05-15 02:06:35 UTC (rev 3769)
+++ trunk/packages/kdenetwork/debian/kopete.presubj	2006-05-15 15:02:42 UTC (rev 3770)
@@ -1,15 +1,14 @@
 Reporting a kopete crash
 ------------------------
 
-It is important when you report a kopete crash to provide:
- * the exact steps to reproduce the crash (Protocol used, the plugins you
-   have activated, the precises circumstances of the bug, ...)
- * a useful backtrace of the crash.
+When you report a kopete crash, it is important to provide:
+ * the exact steps to reproduce the crash (the protocol used, the plugins
+   you have activated, the precises circumstances of the bug...)
+ * a useful backtrace of the crash
 
-To produce useful backtrace you must have kdelibs-dbg and kdenetwork-dbg
-installed. kdebase-dbg may also be useful.  A backtrace full of
-"(no debugging symbols found)" is useless.
+To produce useful backtraces you must have qt-x11-free-dbg, kdelibs-dbg,
+and kdenetwork-dbg installed. kdebase-dbg may also be useful. A backtrace
+full of "(no debugging symbols found)" is useless.
 
-A bug that is not reproducible, or that lack the necessary backtrace, will
+A bug that is not reproducible, or that lacks the necessary backtrace, will
 be discarded.
-