| 1 |
Please DO NOT report UPSTREAM bugs in this Amarok version to the |
| 2 |
Debian Bug Tracking System |
| 3 |
|
| 4 |
The experimental version of Amarok you have installed is either alpha, beta, |
| 5 |
release-candidate (RC), a snapshot of upstream development tree or other |
| 6 |
type of pre-release. Hence crashes, missing or partially working features |
| 7 |
and other types of bugs ranging from minor to grave are expected depending |
| 8 |
on the current development stage. Therefore it would be overwhelming for me, |
| 9 |
Debian maintainer of the Amarok package, to provide support for Amarok |
| 10 |
upstream bugs (i.e. problems with Amarok itself) at this stage. So UNLESS: |
| 11 |
|
| 12 |
1) you are sure that you've found a problem with Debian packaging or just |
| 13 |
want to suggest a packaging related improvement |
| 14 |
-- OR -- |
| 15 |
2) the bug is grave (e.g. like Amarok does not start) so Amarok is |
| 16 |
completely unusable or Amarok completely breaks unrelated software or |
| 17 |
eats unrelated data (i.e. it might be dangerous for other users systems |
| 18 |
or data), |
| 19 |
|
| 20 |
DO NOT report it to the Debian Bug Tracking System. You should report |
| 21 |
problems with pre-release versions directly to Amarok developers by choosing |
| 22 |
"Report Bug..." from the "Help" menu in the main Amarok window (recommended) |
| 23 |
or visiting http://bugs.kde.org/ (in this case, if this Debian Amarok package |
| 24 |
is a snapshot, do not forget to include svn revision number which is encoded |
| 25 |
in the Debian version of the package). If you're about to report a crash, |
| 26 |
make sure the backtrace was generated with the amarok-dbg package and |
| 27 |
preferably its recommends installed on your system. This way the most |
| 28 |
accurate information will be provided to the Amarok developers. |