Python exception on installation about critic HOT 6 OPEN

Then I've tried uninstall.py and it first failed because /etc/critic wasn't created.
I've created it and ran uninstall.py again - it completed successfully.
Tried run install.py again and got:

Where should Critic's persistent data files live? [/var/lib/critic]
Invalid input: directory already exists (NOTE: if Critic is already installed and you want to upgrade to the latest version of Critic, then run upgrade.py rather than re-running install.py).

Looks like uninstall misses some stuff.

from critic.

Which distro where you trying to install on when you saw the original install.py crash?

As a temporary workaround until uninstall.py is improved, you might be able to completely remove critic and loose all data etc using this nasty sledgehammer:

    sudo killall -u critic
    sleep 0.2
    sudo killall -9 -u critic
    sudo service critic-main stop
    sudo service apache2 stop
    sudo rm -rf /etc/critic /var/{lib,log,cache,run}/critic /usr/share/critic /var/git
    sudo rm -f /etc/apache2/sites-{enabled,available}/critic-main /etc/init.d/critic-main /usr/bin/criticctl
    sudo -u postgres psql -c "drop database critic;"
    sudo -u postgres psql -c "drop user critic;"
    sudo gpasswd -d molsson critic
    sudo deluser --system critic
    sudo delgroup --system critic
    sudo update-rc.d critic-main remove
    sudo service apache2 restart
    sudo rm -rf ~/src/critic/.install.data

from critic.

replace molsson and ~/src/critic with your equivalents ofc

from critic.

Using Ubuntu 13.04.
Thanks for the sledge hammer. I won't use it for now as I can make uninstall complete successfully after creating that dir manually.
I would be more interested in a way to make it install properly. :)

from critic.

Ubuntu 13.04 is certainly a well-tested and supported OS. Or at least the "server" variant is. Odd that you should have a problem with it. Can you check if you have an (executable) /bin/sh?

from critic.

I found out what's the problem. It's the fact that cloned repo had CRLF line endings (apparently autocrlf = true is not a good default on linux). Works fine with "false" and cloning again.
Feel free to resolve or maybe handle it somehow (bail out quickly with a warning/error maybe?).

from critic.