Your message dated Sat, 27 Jun 2015 20:34:15 +0200 with message-id <[email protected]> and subject line Fixed in pyosmium/2.1.0-2 has caused the Debian Bug report #789865, regarding pyosmium: FTBFS (32-bit): test_broken_timestamp AssertionError: ValueError not raised 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.) -- 789865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789865 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: pyosmium Version: 2.1.0-1 Severity: important 32-bit builds of pyosmium have been failing: I: pybuild base:170: cd test && python2.7 run_tests.py ....F.............. ====================================================================== FAIL: test_broken_timestamp (test_io.TestReaderFromFile) ---------------------------------------------------------------------- Traceback (most recent call last): File "/«PKGBUILDDIR»/test/test_io.py", line 45, in test_broken_timestamp o.apply(rd, o.SimpleHandler()) AssertionError: ValueError not raised Could you please take a look? You might have to disable the test there, if it assumes a 64-bit time_t. Thanks!
--- End Message ---
--- Begin Message ---fixed 789865 pyosmium/2.1.0-2 thanks
--- End Message ---
_______________________________________________ Pkg-grass-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
