Control: tag -1 - unreproducible + confirmed
Control: retitle -1 FTBFS when only Moose is installed

On 25.Aug.2013, at 15:31 , gregor herrmann <gre...@debian.org> wrote:
> On Sat, 24 Aug 2013 13:23:16 +0100, Dominic Hargreaves wrote:
>> TOPDIR=/build/dom-aptitude-robot_1.2.14-1-i386-p0IDb0/aptitude-robot-1.2.14 
>> prove -I/build/dom-aptitude-robot
>> _1.2.14-1-i386-p0IDb0/aptitude-robot-1.2.14 
>> /build/dom-aptitude-robot_1.2.14-1-i386-p0IDb0/aptitude-robot-1.2
>> .14/t
>> /build/dom-aptitude-robot_1.2.14-1-i386-p0IDb0/aptitude-robot-1.2.14/t/001_help-option.t
>>  ............. ok
>> Use of uninitialized value in concatenation (.) or string at 
>> /build/dom-aptitude-robot_1.2.14-1-i386-p0IDb0/a
>> ptitude-robot-1.2.14/aptitude-robot line 99.
>> Use of uninitialized value in concatenation (.) or string at 
>> /build/dom-aptitude-robot_1.2.14-1-i386-p0IDb0/a
>> ptitude-robot-1.2.14/aptitude-robot line 103.
>> 
>> #   Failed test 'check for error string'
>> #   at 
>> /build/dom-aptitude-robot_1.2.14-1-i386-p0IDb0/aptitude-robot-1.2.14/t/010_simple-calls.t
>>  line 22.
>> #          got: 'Error:  is not a aptitude-robot config directory'
>> #     expected: 'Error: /dev/null is not a aptitude-robot config directory'
> 
> That's an interesting case, and I can't reproduce it.
> From the output above it looks like config_dir is not set, but I
> don't see how this can happen; and it doesn't seem to be Perl 5.18
> related.
> 
> Anyway, I'm sure Elmar and Axel know their code better and can come
> up with some insights :)

Finally, we could reproduce this bug.  It has nothing to do with perl 5.18 but 
with Moose vs. Mouse.

aptitude-robot uses Any::Moose which defaults to Mouse unless Moose is already 
installed on the system.  With Mouse it would run the tests without problems 
but with Moose (and no Mouse installed) we get exactly the errors Dominic 
reported.

We still need to find out why Moose would trigger these errors when Mouse does 
not.  Ultimately however, this is the motivation to replace Mouse with Moo, 
which was planned anyway.

Regards     -- Elmar

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to