On 2012-01-13 01:23, Gerfried Fuchs wrote:
| No, you didn't. What you did is pulling the issue that you reported in
| 654189 and got handled through that by upstream already into this very
| bugreport as a duplicate
654189
The gitolite installation contains commands that are not used by
gitolite itself, but that are useful for administration by root.
653993
"Unsuccessful stat on filename containing newline at
/usr/share/gitolite/sshkeys-lint line 142, <> line 29. file not
found:"
| ...and it is tracked in 654189 already, which upstream has a fix for
| already.
I take it you're referring to 653994. It doesn't fix this current
problem.
| The fix is for 654189 which was handled by upstream already. If you
| consider that incomplete, please continue there and do not sidetrack
| other bugreports, even if they were filed by yourself.
Rerouting from 654189; as you probably refer to 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.
The patch, that you may have forgot to look at, fixes this.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
