Small update: I've reproduced this myself. It seems to be
because of a difference in FIU from 0.14 to 0.90.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Indeed, the command line flags for fiu-ctrl have changed.
The old flags (-e and -d) are still accepted but sliently
ignored; instead of a proper error message, it simply
produced incorrect behavior.
I updated the tests that use FIU and now all tests pass
for me. You can see the change at
On Mon, Oct 8, 2012 at 12:15 AM, Keith Rarick k...@xph.us wrote:
You can see the change at
https://github.com/kr/beanstalkd/compare/fiu
Just to be really explicit, the only relevant change right
now is https://github.com/kr/beanstalkd/commit/3176e28.
That compare view also lists another patch
Hey, sorry, I didn't mean to imply that I wouldn't make a
fix. I said before I'm happy to maintain 1.4.x for several
years and that's still true.
As part of my responsibility maintaining 1.4.x, I was just
trying to start with the most expedient reasonable option,
which would have been to use
If libevent 1.4 is not an option, I'll get the 1.4.x series of beanstalkd
working with libevent 2 and make a bugfix release.
Should I do that?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
A number of people have reported problems using libevent 2.
I'd suggest sticking to libevent 1.4; that is the version that
beanstalkd was developed and tested with.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Tue, Sep 11, 2012 at 12:07 AM, Serafeim Zanikolas s...@debian.org wrote:
Thanks Keith. I've verified the fix on ppc, sparc mips. Please go ahead with
a release.
Done.
http://kr.github.com/beanstalkd/2012/09/11/1.7-release-notes.html
Thanks for all the help with this, and for your
On Thu, Aug 30, 2012 at 1:43 AM, Serafeim Zanikolas s...@debian.org wrote:
Going back to the subject of the bug report, please let me know when you have
a potential fix for the failing tests, and I'll test it on whatever arches you
don't have access to.
Ok, I believe this is fixed now in
On Thu, Aug 30, 2012 at 1:43 AM, Serafeim Zanikolas s...@debian.org wrote:
Going back to the subject of the bug report, please let me know when you have
a potential fix for the failing tests, and I'll test it on whatever arches you
don't have access to.
Will do.
--
To UNSUBSCRIBE, email to
On Tue, Aug 28, 2012 at 6:29 AM, Serafeim Zanikolas s...@debian.org wrote:
Since I haven't heard from you on a fix for 1.6, 1.5 tests never ran
successfully, and I do not wish to keep 1.4 in the next Debian stable release,
I'm going to request the removal of beanstalkd from the Debian archive.
On Sun, May 20, 2012 at 11:35 AM, Serafeim Zanikolas s...@debian.org wrote:
I've uploaded 1.6 but many tests fail with a timeout in powerpc s390(x)
Looks like it fails on all the big-endian architectures.
Debugging this would be much easier if I had access
to a big-endian machine. I'll work on
Awesome, thanks!
I made sure to keep all the existing tests that weren't
redundant or otherwise nonsensical. The binlog sizelimit
test is now a function in integ-test.c.
I'll make another release as soon as I can fix
https://github.com/kr/beanstalkd/issues/114
--
To UNSUBSCRIBE, email to
12 matches
Mail list logo
