On 2012-01-13 10:21, Gerfried Fuchs wrote:
| Then please state it THERE, not HERE where the bugreport was about your
| confusion with not reading the documentation and wanting to have the
| intended way it works changed.  

In 653993 the bug was closed with reasoning that with the suggested
change, by adding a check and warning, it would deny other uses of
program. By closing the bug, it unfortunately left the reported error
unhandled.

| > 653994:
| > 
| >       "This should be considered my fault, in that v2.2 had a bug in
| >       gl-setup, (wouldn't deal well with blank lines in
| >       ~/.ssh/authorized_keys), I fixed it a few commits late"
| > 
| > The latest code in upstream Git with the above fix, doesn't solve the
| > reported problem. See diff in upstream Git.
| 
| So for the last time, note that there, because this very bugreport is
| about a completely different issue.

You probably mean the subject of the bug message. It appears that I
was referring to the body (the error debug log), so there might have
been miscommunication.

Indeed, perhaps 653993 and 653994 should be merged, because the error
is the same in both cases.

| > The patch, ... fixes this.
| 
| It is no patch for this issue, so I fail to see what it is doing here.
| Rhonda

To clarify: the patch fixes the error exhibited in both 653993 (body,
the error message) and possibly 653994. The bug is not fixed by the
upstream change expressed in 653994 (see quote above).

The patch is in:

    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653993#63

Jari



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to