https://meduza.io/news/2015/08/25/pravitelstvo-soglasilos-priznat-veloprobegi-aktsiyami-protesta Ура!

Стой, куда ты? Ну ты и соня. Тебя даже вчерашнее падение рубля не разбудило.

https://meduza.io/news/2015/08/25/sud-dosrochno-osvobodil-evgeniyu-vasilievu Ура!

yay, til http://www.unicorn-engine.org/

https://meduza.io/news/2015/08/25/vikipediya-poluchila-uvedomlenie-ob-isklyuchenii-stati-charas-iz-reestra-zapreschennyh-saytov Перемога!

https://imgur.com/gallery/nmlLW

Mercurial
2017
Speaking of extensions, the progress extension has been merged into the core codebase and enabled by default. A popular extension in previous releases, it draws progress bars to report on in-progress operations.

Finally sid deserves its name again. GCC 5 is now the default in unstable and packages for the follow-up transitions are (and can be) uploaded to unstable.
What you should not do:
- upload a library package with an open transition issue [1] without renaming the library package or bumping the soname, just saying "Rebuild with GCC 5", and silently breaking the ABI.
- upload a package which builds a C++ library package, which is built with anything else than g++-5.
- having a vacation and hoping the mess is cleaned up when you come back.

http://thread.gmane.org/gmane.linux.debian.devel.announce/2071

Most Debian users know that you probably shouldn't do a dist-upgrade from an old system -- you upgrade and then you dist-upgrade. Or perhaps this isn't even true, it's tribal lore to avoid getting eaten by the wild beasts of bork that roam around the village walls at night. Anyway that's what I did -- an upgrade, let it chunk for a while, then a dist-upgrade, check the list to make sure it didn't decide to remove one of my kidneys to satisfy the priorities of the bearded demon that lives inside apt-get, OK, let it go, all is well, reboot.