quit
(I believe that lets the BTS system not react to this email but just record it)
On Sat, Jan 7, 2012 at 7:52 AM, Sitaram Chamarty wrote:
> I will do that (tag it v2.2.1) and push this weekend.
fixed, tested, and pushed.
Until this makes it into your systems, the workaround is to delete
bla
Rhonda,
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 later, but -- and
this is the part that is my fault -- did not tag it so maintainers
could get it.
I will do that (tag it v2.2.
tag 653994 - pending
severity 653994 minor
thanks
Dear Jari,
it would be nice if you could read the BTS documentation on what the
tag pending means and what the severity serious stands for.
Thanks,
Rhonda
--
Fühlst du dich mutlos, fass endlich Mut, los |
Fühlst du dich hilflos, geh
tags 653994 + pending fixed-upstream
thanks
2012-01-04 02:44 Sitaram Chamarty :
| This was fixed by this commit:
>
| ab9d0d2 7 weeks ago a couple of very minor oopsies
>
| (It's caused by not parsing a blank line in the authkeys file properly)
>
| Jari: I do not know what debian's standards are
Package: gitolite
Version: 2.2-1
Severity: serious
gl-setup calls Perl script /usr/share/gitolite/sshkeys-lint which
aborts with cryptic error:
Unsuccessful stat on filename containing newline at
/usr/share/gitolite/sshkeys-lint line 142, <> line29.
file not found:
The last steps in gl-
5 matches
Mail list logo
