there is still one thing, that is unclear for me. Chromium is security unsupported package. But does it also mean, that it is unsupported at all (can be non-function after install by apt-get install chromium)?
I am aware, that wheezy chromium package is quite outdated for today web. But isn't this decision precedence for another similar packages? Security support for ruby-rails-2.3 was also ceased. Let's say, that I have application that is tested against that. I can still easily install it and run it under that, even if there are some described and non-fixed security vulnerabilities. And that wouldn't be true if some library, that it depand on would be upgraded to non-compatible version. I see it as a problem, that wasn't here in pre-lts verions. If I'll install woody, all packaged would be outdated, but fully function. That will not be true with wheezy anymore (at least until libnss3 downgrade).
Is there some debian policy regarding it?
P.S.: Current chrome-stable has unment dependencies in wheezy