The second one requires libgtk-3-dev to install which requires 128 MiB of NEW gtk3 shit to install...
Me NO WANT TO INSTALL GTK3 shit to get a menu to fucking work
Sorry for yelling and the language...
Nothing to see here, carry on...

I think there is a lot to see here!! I want to rename it from GTK+ to GTK-
I just checked, and I've been using VSIDO since mid 2012 sometime. No problems at all. That the gtk+ team did this with no thought in mind for the end user goes beyond the pale. When they made the decision to move to CSS, they should also have made the move to provide theme developers at a minimum, some way to "rescue" their current themes rather than just abandoning ALL of them to the dust-bin of history. They had to know it was going to break lots of things. If they didn't, then shame on them, and if they did, and did it anyway, then shame on us as a community.
I've looked at a lot of themes over the last few months. As PackRat mentioned, this first popped up in Arch (which I just so happened to be running at the time, to my great chagrin, and at great cost) it also happened everywhere else. This was not an issue of 'sometime' breakage in an unstable (re: Sid) distro. This was breakage on a level that affected most all distro's! That is why I was "ranting and raving" and "yelling and screaming" with my earlier post.
Hey, if I compile an RC version of the Kernel, and it breaks my OS, then it's my bad! If I do an upgrade on my distro, and YOU (gtk+ dev's) broke my distro, then WTF?
As I type this, I'm hoping I've come up with a workable solution. I've been pondering since I saw the 'apt-pinning' post VastOne made above. (or somewhere close by!) It triggered a thought... (I haven't rebooted yet, so it may have all been a huge SELF-DESTRUCT, crash and burn kind of thing!)

I'll post back here after a reboot and let you all know the results, and if it works, I'll tell what I did...