Your message dated Tue, 30 Jul 2013 00:35:30 -0400
with message-id <878v0owtpp....@naesten.dyndns.org>
and subject line Re: Bug#602668: libdevel-bt-perl: FTBFS on armel
has caused the Debian Bug report #602668,
regarding libdevel-bt-perl: FTBFS on armel
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 ow...@bugs.debian.org
immediately.)


-- 
602668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdevel-bt-perl
Version: 0.05-1
Severity: serious

Hello,

Your package fails to build on armel with following error:
Test Summary Report
-------------------
t/basic.t             (Wstat: 1280 Tests: 5 Failed: 5)
  Failed tests:  1-5
    Non-zero exit status: 5
    Files=4, Tests=5,  9 wallclock secs ( 0.21 usr  0.02 sys +  1.81 cusr  0.38 
csys =  2.42 CPU)
    Result: FAIL
    make[1]: *** [test_dynamic] Error 255
    make[1]: Leaving directory 
`/build/buildd-libdevel-bt-perl_0.05-1-armel-gAnCHp/libdevel-bt-perl-0.05'
    dh_auto_test: make -j1 test returned exit code 2
    make: *** [build] Error 29

Full buildlog at: 
https://buildd.debian.org/fetch.cgi?pkg=libdevel-bt-perl;ver=0.05-1;arch=armel;stamp=1288778427

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--- End Message ---
--- Begin Message ---
While this presumably is or was a problem with GDB, this particular
manifestation seems to have disappeared, so I'm closing this bug.

(I'm actually kind of sad it doesn't still do this because I was hoping
it had the same cause as another, more intermittent backtrace problem.)

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!

--- End Message ---

Reply via email to