Your message dated Sat, 17 May 2014 17:42:28 +0200
with message-id <[email protected]>
and subject line Re: [kgb-maintainers] Bug#748397: merging branches floods
channels
has caused the Debian Bug report #748397,
regarding merging branches floods channels
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
748397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748397
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: kgb-bot
Version: 1.31-1
Severity: normal
Suppose I am developing on branch A, pushing as I go, with kgb
mentioning each change on IRC. After a long time, I reach a point where
I merge A into branch B. When I push B, kgb will flood IRC with all the
commits, which it has already mentioned before when they were made on A.
I just had kgb want to flood a channel with 2 months worth of commits,
totaling 570 commits, when I updated a backport. I had to kill the bot
to avoid the channel being unusable for a long time.
I think the bot should either avoid mentioning commits that it's
mentioned before, even if they're on a new branch now, or it should
detect when it's been fed a lot of commits to the same branch and
display a shortened message like "commit foo and 569 more".
--
see shy jo
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1.29-1
(seems like 1.28 was never uploaded)
On Sat, 17 May 2014 11:23:05 -0400, Joey Hess wrote:
> gregor herrmann wrote:
> > This is already implemented since 1.28
[..]
> > Now the question is why the default didn't kick in in your case ...
> > Are you running an older version of the client?
> Yes, in fact I am, the server is on unstable but the client is on
> stable.
Ok, that explains.
> Any chance of a backport of the client?
Not totally easy; kgb-bot has a versioned build dependency on
libtest-compile-perl (>= 0.19) because the tests use
Test::Compile::Internal (which was introduced in 0.19).
So we'd either have to backport libtest-compile-perl as well (haven't
looked at it now), or revert the change from Test::Compile to
Test::Compile::Internal or skip the tests.
Dam, what do you think?
Joey, any chance you could just install 1.31-1 from testing? The
runtime dependencies shouldn't be a problem. (Or run the version
from git.)
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
`- NP: Little Richard: Let It Roll
signature.asc
Description: Digital Signature
--- End Message ---
