Bastian, would it be possible to retest g-wrap 1.9.11-1 using the current version of guile-1.8-dev (1.8.5+1-1) on s390?
#466778 (which was claimed as the source of the original FTBFS) was fixed in that version but your build failure that requested the reopening of this bug shows: Setting up guile-1.8-dev (1.8.4+1-2) ... If the s390 build works with guile-1.8-dev (1.8.5+1-1), maybe a few rebuilds can be attempted for g-wrap with the latest version of guile-1.8-dev (but the Build-Depends of g-wrap should still be updated to require the fixed version of guile-1.8-dev anyway so this bug can then be retitled and lowered in severity). Alternatively, g-wrap with guile-1.8-dev (1.8.5+1-1) may simply repeat #475673 on s390. (I neither need nor use g-wrap anymore, but as Andreas has not responded, I'm just seeing if the RC bug count can be tweaked by either lowering the severity of this bug or merging it with #475673 if the updated guile-1.8-dev gives the same test failure as on sparc.) -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
signature.asc
Description: This is a digitally signed message part
