Hi all, I've a sponsored package in debian (nsis) that recently got through NEW. Immediately after this, I got an amd64 FTBFS bug that thankfully came with a patch (immediately applied and fwded upstream). I note that the sparc and mipsel buildds also FTBFS[1] for different reasons to amd64. As a non-DD, the only sparc machines I have access to are the solaris boxen in the sourceforge compile farm. I've tested the relevant parts of the build process there, without any luck - they succeed. So, my question is, how do I deal with this, since this will hold my package out of testing indefinitely? 1. http://buildd.debian.org/fetch.php?&pkg=nsis&ver=2.06-2&arch=sparc&stamp=1113016855&file=log&as=raw http://buildd.debian.org/fetch.php?&pkg=nsis&ver=2.06-2&arch=mipsel&stamp=1113013385&file=log&as=raw -- bye, pabs
Attachment:
signature.asc
Description: This is a digitally signed message part