Haven’t run into this personally yet, but it’s been on my mind. Say Package@v1.2.3 is not working properly in a given environment, but I do not know why and want to reinstall it and its dependencies in case a file got corrupted. I can rm it from the environment, but that doesn’t touch the central installation. update installs another version without touching the broken one that might remain in other environments. If all the active environments happen to not have that package version, I could gc it, but that might not touch an unknown broken dependency, and I really prefer not to tweak every environment just to reinstall then re-add it. I could manually delete files from the .julia folder, but I don’t know how to identify the broken files to save work or the possible dependencies to be safe, and nuking the entire folder or subfolders is overkill that is only tolerable for first-time users. I’m hoping I just missed something obvious or that someone else figured out something.