On Thu, 12 Jan 2012, jaalto wrote: > If you mean that this bug should be merged to 653994, perhaps that > is the correct action. I'm not sure why the bug should stay closed > for reported error: > > "Unsuccessful stat on filename containing newline at > /usr/share/gitolite/sshkeys-lint line 142, <> line 29. file not > found:"
If a maintainer closes a bug, and after a single round of explanation, still does not agree with reopening the bug, the bug should stay closed. If you disagree with the maintainer, then your choices are to either attempt to: 1) convince the maintainer that your viewpoint is correct, preferably by submitting a patch which fixes the perceived problem, along with rationale as to why the patch is correct. 2) attempt to convince the technical committee that the maintainer is incorrect, and should be overridden. This necessitates a patch as required for #1. In neither case should you reopen bugs that a maintainer has closed.[1] Continuing to do so will result in restricting your use of cont...@bugs.debian.org. Don Armstrong 1: It is of course acceptable to reopen a bug in cases when the maintainer is likely to agree with you, but that is clearly not the case here. -- life's not a paragraph And death i think is no parenthesis -- e.e. cummings "Four VII" _is 5_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
