Your message dated Wed, 09 Oct 2013 20:17:11 +0800 with message-id <[email protected]> and subject line After another build attempt, it doesn't FTBFS has caused the Debian Bug report #724632, regarding FTBFS on kfreebsd-i386 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 [email protected] immediately.) -- 724632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724632 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: python-greenlet Version: 0.4.0-2 Severity: serious Hi, It's been 188 days that python-greenlet isn't migrating to testing because it's out of date on kfreebsd-i386, due to FTBFS. Relevant part: ====================================================================== FAIL: test_threaded_leak (tests.test_leaks.ArgRefcountTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/build/buildd-python-greenlet_0.4.0-2-kfreebsd-i386-g1IMfO/python-greenlet-0.4.0/tests/test_leaks.py", line 43, in test_threaded_leak self.assertTrue(g() is None) AssertionError ---------------------------------------------------------------------- Ran 61 tests in 0.433s FAILED (failures=1) python 2.6.8 (32 bit) using greenlet 0.4.0 from /build/buildd-python-greenlet_0.4.0-2-kfreebsd-i386-g1IMfO/python-greenlet-0.4.0/build/test-2.6/greenlet.so make[1]: *** [test-2.6-stamp] Error 1 make[1]: Leaving directory `/build/buildd-python-greenlet_0.4.0-2-kfreebsd-i386-g1IMfO/python-greenlet-0.4.0' make: *** [build-arch] Error 2 Please fix the unit testing or allow it to fail so that python-greenlet can migrate to Jessie. Cheers, Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---Hi, As the package was rebuilt recently, and that it worked (probably because there's no Python 2.6 anymore!), this bug can be closed. As a side note, I really think this was the role of the package maintainer to take care of this. If you don't have time to take care of your package, I would suggest that you at least put it under the Python Module team. Cheers, Thomas Goirand (zigo)
--- End Message ---
