Yes, I ran into the same issue. I have pretty much received the same problem with every other package in the newly updated unstable feed (2/24), even though I have installed the updated dependencies. The packages in that feed before the post recent update seemed to work fine. Perhaps there is something we are all missing, or maybe there might be a compatibility issue somewhere. I can only speculate, as I have no direct involvement.
~AIG