summaryrefslogtreecommitdiffstats
path: root/debian/bug-presubj
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-15 05:55:35 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-15 05:55:35 +0000
commit0e05dd0e4d67d88ca51780dafe4029744269e6fa (patch)
treeb49073fa569d8d4fbcc7002cf4df72fa840780c1 /debian/bug-presubj
parentAdding upstream version 4:24.2.0. (diff)
downloadlibreoffice-0e05dd0e4d67d88ca51780dafe4029744269e6fa.tar.xz
libreoffice-0e05dd0e4d67d88ca51780dafe4029744269e6fa.zip
Adding debian version 4:24.2.0-1.debian/4%24.2.0-1
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'debian/bug-presubj')
-rw-r--r--debian/bug-presubj61
1 files changed, 61 insertions, 0 deletions
diff --git a/debian/bug-presubj b/debian/bug-presubj
new file mode 100644
index 0000000000..b0b6cfc7c2
--- /dev/null
+++ b/debian/bug-presubj
@@ -0,0 +1,61 @@
+Reporting a bug against LibreOffice
+--------------------------------------
+I) Make sure it's a LibreOffice bug after all: #398923 and its friends for
+ example are not.
+ Set the Version: header right. If you found a bug in a specific version,
+ set that as version:, even if you in the meanwhile upgraded. If you are on
+ an up-to-date version and tried old versions and they have the bug, too, set
+ the Version: header to the earliest version you found it in (of course, if
+ versions inbetween don't have the bug use the version in which it reappeared
+ and sustained to the current version)
+
+II) Check on the BTS (http://bugs.debian.org/src:libreoffice) whether the
+ bug already is reported. Do *NOT* report a new one then. For judging whether
+ it's already reported, read *ALL* the bugs, think, try and use common sense.
+
+III) If you have crashes with a document, try another one. If only that or
+ similar docs causes problems please attach THIS (or a similar type one
+ causing it). Otherwise, don't file a bug, we can't look at it anyway.
+
+IV) Please attach more info if possible (see
+ https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux).
+ Install libreoffice-*-dbgsym or libreoffice-dbg before doing this (and maybe
+ the packages it Recommends and/or -dbgsym/-dbg of the libraries LO depends
+ on).
+ Please note that those *-dbgsym packages are not in the main archive; you
+ need to add the debug archive for that.
+ See https://wiki.debian.org/AutomaticDebugPackages
+ Please also read /usr/share/doc/libreoffice-common/README.gz for common
+ problems ("Problems During Program Startup")
+ If you have NFS/Samba/... file locking problems (i.e. files opened
+ read-only when they should be read-write), also see the "File Locking"
+ section in above file.
+
+V) If the bug is also in the version you can get from www.libreoffice.org, file
+ it there (see https://wiki.documentfoundation.org/QA/BugReport) in the first
+ place. If you really think this also should be a bug in the Debian BTS
+ (because it's (release-)critical or otherwise important) please file a bug
+ there too *BUT* note the TDF bug number in the bug or mark it forwarded
+ yourself if you can. Especially this is for feature requests.
+ If you tested other LibreOffice packages and the bug is (not) in version
+ foo from bar, mention that, too.
+
+VI) Only report bugs on completely up-to-date systems. Don't file bugs on a
+ obsolete version and neither on sid/testing systems really old. Nor on
+ backports, see https://backports.debian.org/Instructions/#index6h2. If bugs
+ got fixed in sid, it doesn't make sense to file them anymore. (Exception
+ is security bugs or really critical bugs which should be get fixed in
+ stable.) When you think a dependency is missing/wrong/too lax please be
+ *sure* that this is the case before reporting it. Most times it isn't.
+ Use common sense and the bug severities for judging here. When you think
+ you have an up-to-date system, check whether you really have one.
+ (And do a dist-upgrade, try to reproduce the bug again).
+ Also don't report bugs on broken mix systems unless you are sure about the
+ dependencies/conflicts (see above).
+
+VII) Please give as much info as possible (installed LibreOffice packages, installed
+ extensions, "special" configs, additions, changes, whatever). Better too
+ much than too less. (See #396225 for example which was caused by an
+ unsupportable, non-free extension)
+
+Thanks.