On Thu, Oct 27, 2016 at 06:42:43PM -0400, Jeffrey Walton wrote:
> > I'm closing this bug. Get your shit together....
>
> My shit is sprayed all over the place because you guys cannot seem to
> get your shit together.
>
> What a surprise yet another bug was closed without fixing it....
Here's what you should do:
1. Calm down
2. Write a respectful, non-insulting description of your issue. Explain
what you did, what happened, and what you expected to happen.
3. If it is related to an existing bug, explain how so.
4. Check if it happens with the latest version in unstable.
5. If it does not happen in unstable and testing, explain why you think
it is a release critical bug that deserves to be fixed in stable. Note
that port bugs are not release critical and won't be fixed in stable
(there are also no stable releases for ports architectures).
6. If it is architecture-specifc, CC the mailing list responsible for
the architecture, so they can provide input.
Opening a rude bug report against a version of apt that is not
supported anymore, that only consists of insults and does not
contain an actual problem description is not productive way
to communicate.
The bug you linked was fixed to the best of our knowledge, and
nobody has said anything different. If you believe that the bug
was not fixed, you should re-open it, explaining that you can
still reproduce the bug in unstable.
I will continue to close rude bug reports, especially those
without actual input and only accusations and insults.
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline'). Thank you.
