Loïc Minier <[EMAIL PROTECTED]> writes: > When this thread started, you had decided to bind the fix with the new > upstream release and you had blocked the new upstream release with the > switch of the default Python version. Now you're also blocking this > new upstream release with a major new guile version.
It is amazing how you could get something so simple so very wrong. What I said ages ago was that it's *not* bound with the new upstream release; rather, it's bound with me *not knowing* whether the new upstream release could be packaged in the short-term. Thomas
