It looks like this is definitely a bug in pth (or something pth uses).
When libpth20 2.0.7-16 was built, it bombed out with the same error while running tests, but the build rules silently ignore the failure :(
http://launchpadlibrarian.net/48374229/buildlog_ubuntu-maverick-armel.pth_2.0.7-16_FULLYBUILT.txt.gz
It looks like this is definitely a bug in pth (or something pth uses).
When libpth20 2.0.7-16 was built, it bombed out with the same error while running tests, but the build rules silently ignore the failure :(
http:// launchpadlibrar ian.net/ 48374229/ buildlog_ ubuntu- maverick- armel.pth_ 2.0.7-16_ FULLYBUILT. txt.gz