Error upgrading from 5.0.0 to 5.0.1

[aredridel]

I'm opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don't understand.
• Other (see below for feature requests):

What's going wrong?

npm i -g npm@latest left me with an error message and no working npm.

:; npm i -g npm@latest
/Users/aredridel/bin/npm -> /Users/aredridel/lib/node_modules/npm/bin/npm-cli.js
npm ERR! path /Users/aredridel/share/man/man5/package.json.5
npm ERR! code EEXIST
npm ERR! Refusing to delete /Users/aredridel/share/man/man5/package.json.5: ../../../Projects/npm/man/man5/package.json.5 symlink target is not controlled by npm /Users/aredridel/share/man/man5
npm ERR! File exists: /Users/aredridel/share/man/man5/package.json.5
npm ERR! Move it away, and try again.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/aredridel/.npm/_logs/2017-05-31T16_34_55_670Z-debug.log

How can the CLI team reproduce the problem?

I have the prefix set to my home directory for global installs.

npm i -g npm@5.0.0 and then npm i -g npm@5.0.1

supporting information:

• npm -v prints: was 5.0.0
• node -v prints: v7.9.0
• npm config get registry prints: It's the default registry
• Windows, OS X/macOS, or Linux?: macOS
• Network issues:
  • Geographic location where npm was run: Boston
  • I use a proxy to connect to the npm registry.
  • I use a proxy to connect to the web.
  • I use a proxy when downloading Git repos.
  • I access the npm registry via a VPN
  • I don't use a proxy, but have limited or unreliable internet access.
• Container:
  • I develop using Vagrant on Windows.
  • I develop using Vagrant on OS X or Linux.
  • I develop / deploy using Docker.
  • I deploy to a PaaS (Triton, Heroku).

Log at https://gist.github.com/aredridel/0c90ee71b13b721828ed3c330b542482

[apertureless]

Check out #16851