Package: libbuffy-bindings
Version: 0.5
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080710 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on
i386.

Relevant part:
(cd tests && ./test.pl)
1..89
"my" variable $folder masks earlier declaration in same scope at ./test.pl line 
37.
"my" variable $folder masks earlier declaration in same scope at ./test.pl line 
44.
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
ok 14
ok 15
ok 16
ok 17
ok 18
ok 19
ok 20
ok 21
ok 22
ok 23
ok 24
ok 25
ok 26
ok 27
ok 28
ok 29
ok 30
ok 31
ok 32
ok 33
ok 34
ok 35
ok 36
ok 37
ok 38
ok 39
ok 40
ok 41
ok 42
ok 43
ok 44
ok 45
ok 46
ok 47
ok 48
ok 49
ok 50
ok 51
ok 52
ok 53
ok 54
ok 55
ok 56
ok 57
ok 58
ok 59
ok 60
ok 61
ok 62
ok 63
ok 64
ok 65
ok 66
ok 67
ok 68
ok 69
ok 70
ok 71
ok 72
ok 73
ok 74
ok 75
ok 76
ok 77
ok 78
ok 79
ok 80
ok 81
ok 82
ok 83
ok 84
ok 85
ok 86
ok 87
ok 88
ok 89
(cd tests && ./test.py)
Traceback (most recent call last):
  File "./test.py", line 6, in <module>
    import Buffy
  File "../python/Buffy.py", line 7, in <module>
    import _Buffy
ImportError: No module named _Buffy
make[1]: *** [check] Error 1
make[1]: Leaving directory 
`/build/user-libbuffy-bindings_0.5-amd64-KGInPn/libbuffy-bindings-0.5'
make: *** [debian/stamp-makefile-check] Error 2
dpkg-buildpackage: failure: debian/rules build gave error exit status 2

The full build log is available from:
   http://people.debian.org/~lucas/logs/2008/07/10

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment.  Internet was not accessible from the build systems.

-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED]             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to