Changes in Mojolicious version 2.27 are causing a failure of the tests and causing a failure to install

2.27 2011-11-16

• Deprecated Mojo::IOLoop->connect in favor of Mojo::IOLoop->client.
• Deprecated Mojo::IOLoop->listen in favor of Mojo::IOLoop->server.

t/redis.t ............. 1/10 Can't locate object method "listen" via package "Mojo::IOLoop" at t/redis.t line 42.

Looks like you planned 10 tests but ran 2.

Test Summary Report

t/redis.t (Wstat: 7424 Tests: 2 Failed: 0)
Non-zero exit status: 29
Parse errors: Bad plan. You planned 10 tests but ran 2.
Files=5, Tests=2, 1 wallclock secs ( 0.11 usr 0.02 sys + 1.50 cusr 0.10 csys = 1.73 CPU)
Result: FAIL
Failed 1/5 test programs. 0/2 subtests failed.
make: *** [test_dynamic] Error 255
UNDEF/MojoX-Redis-0.83.tar.gz
/usr/bin/make test -- NOT OK

Due to Mojolicious changed it's API again, there are "DEPRECATED" warnings when trying to use MojoX::Redis.

Mojo::IOLoop->connect is DEPRECATED in favor of Mojo::IOLoop->client!
Mojo::IOLoop->connection_timeout is DEPRECATED in favor of
Mojo::IOLoop->timeout!
Mojo::IOLoop->write is DEPRECATED in favor of Mojo::IOLoop::Stream->write!

I had a quick check and tried to have a quick fix it, but new Mojolicious not only changed method name but also callback value/objects so it's not easy to have a "quick" fix.

The examples in the DOC are incomplete. as-is they will not work with mojolocious. I finally found the missing piece.

In you mojolicious application you have to replace the default MojoX ioloop instance with the Mojolicious instance.

my $redis = MojoX::Redis->new(server => '127.0.0.1:6379', ioloop => Mojo::IOLoop->new);

Support pub/sub commands

As per subject. Since 5.0 came out the cpantesters produced nearly only FAIL reports. Sample:

http://www.cpantesters.org/cpan/report/a500c654-e812-11e3-a86c-4e298806f0e4

HTH&&Thanks,
(Disclaimer: this was discovered by statistical analysis, I'm not speaking as a user)