Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/opt/venvs/ path not amenable to apt-get purge command #280

Closed
rschwiebert opened this issue May 17, 2019 · 4 comments
Closed

/opt/venvs/ path not amenable to apt-get purge command #280

rschwiebert opened this issue May 17, 2019 · 4 comments

Comments

@rschwiebert
Copy link

I have a question on if I'm doing something right or not.

When trying to purge my package:

Removing thepackage (0.0.1) ... Purging configuration files for thepackage (0.0.1) ... dpkg: warning: while removing thepackage, directory '/opt/venvs/thepackage/lib/python2.7/site-packages/pkg_resources/extern' not empty so not removed

I was hoping that would sorta just work... but then again, I might not be aware of some debian script thing I should be doing to facilitate the cleanup of these files. If there is, could you let me know? Thanks.

@marcvs
Copy link

marcvs commented Feb 26, 2021

I've hit the same issue, I'll file a PR that fixed that for me.

@nailor
Copy link
Collaborator

nailor commented Jul 25, 2021

Hi, and sorry for a late comment!

Do we foresee issues with force removal? My gut sets no, but force removal flag is always a bit dangerous

@jhermann
Copy link
Contributor

Well, these are Python packages that store dynamic data into their __path__, and they shouldn't.

I'd say the proper fix is docs -- show how to remove what your selection of 3rd party packages leaves behind in those paths (using some well-known example), and remove the trash in a prerm or postrm.

cf. https://github.com/1and1/debianized-jupyterhub/blob/master/debian/postrm#L25

@nailor
Copy link
Collaborator

nailor commented Jul 31, 2021

Thanks @jhermann , indeed sounds like a sane strategy. I’ll close this issue for now, as indeed the prerm and postrm are the places to do this

@nailor nailor closed this as completed Jul 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants