Arch Linux

mepqfilho

Member

Registered: 2017-01-02

Posts: 32

virtualenv already exists in usr, how to safely deal with it?

I messed up when I first picked up Arch last year and went for virtualenv and virtualenvwrapper installations through pip, and not through pacman. I never bothered because in the end I didn't have a need for custom environments, so I just gave up and moved on with locally installed site packages on the base interpreter ever since (through pip install --user package).

Now that I'm in need of a local environment to run TensorFlow, I'm trying to install python-virtualenv correctly via pacman but it fails since /usr/bin/virtualenv already exists.

Can I just scrap this file or should I run some checks before? Which checks should I run in this case?

eschwartz

Fellow

Registered: 2014-08-08

Posts: 4,097

Re: virtualenv already exists in usr, how to safely deal with it?

pacman -S lostfiles; lostfiles

Take a look at files which are not tracked by pacman and don't belong as root-owned files. /usr/bin/virtualenv will be one of them. Delete anything applicable and reinstall using pacman once your system is clean.

FWIW, if you did in fact pip install --user virtualenv it should have installed /home/mepqfilho/.local/bin/virtualenv rather than to /usr/bin

---

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)