Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
~♠ lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ~♠ apt-cache policy npm npm: Installed: 1.3.10~dfsg-1 Candidate: 1.3.10~dfsg-1 Version table: *** 1.3.10~dfsg-1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expect the temporary directory of npm to be set either in `~/.cache/npm/` or in `~/.npm/tmp`. 4) What happened instead `npm` defaults to `~/tmp`. If the file `~/tmp` exists (and it does, as I use it as a `vim` buffer when working), `npm` has a really bad time (because the temp dir is a file!) I can only imagine the chaos if some other package decides to use `~/tmp` or `~/tmp/` ... I don't think this issue ever got pushed upstream, here it is on github: https://github.com/npm/npm/issues/2936 I propose it is moved to a directory that isn't as vaguely defined as `~/tmp` such as: * `~/.cache/npm/` * `~/.npm/tmp` * `~/.config/npm/tmp` or if the data is expected not to persist on reboot: * `/tmp/npm/tmp` * `/tmp/npm` ** Affects: npm (Ubuntu) Importance: Undecided Status: New ** Summary changed: - tmp + npm uses ~/tmp/ ** Description changed: - 1) ~♠ lsb_release -rd + 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System + -> About Ubuntu + + ~♠ lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 - 2) ~♠ apt-cache policy npm + 2) The version of the package you are using, via 'apt-cache policy + pkgname' or by checking in Software Center + + ~♠ apt-cache policy npm npm: - Installed: 1.3.10~dfsg-1 - Candidate: 1.3.10~dfsg-1 - Version table: - *** 1.3.10~dfsg-1 0 - 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.3.10~dfsg-1 + Candidate: 1.3.10~dfsg-1 + Version table: + *** 1.3.10~dfsg-1 0 + 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages + 100 /var/lib/dpkg/status - 3) I expect the temporary directory of npm to be set either in - `~/.cache/` or in `~/.npm/tmp`. + 3) What you expected to happen - 4) npm defaults to `~/tmp`. If the file `~/tmp` exists (and it does, as - I use it as a `vim` buffer when working), `npm` has a really bad time + I expect the temporary directory of npm to be set either in `~/.cache/` + or in `~/.npm/tmp`. + + 4) What happened instead + + `npm` defaults to `~/tmp`. If the file `~/tmp` exists (and it does, as I + use it as a `vim` buffer when working), `npm` has a really bad time (because the temp dir is a file!) I can only imagine the chaos if some other package decides to use `~/tmp` or `~/tmp/` ... I don't think this issue ever got pushed upstream, here it is on github: https://github.com/npm/npm/issues/2936 I propose it is moved to a directory that isn't as vaguely defined as `~/tmp` such as: * `~/.cache/npm/` * `~/.npm/tmp` * `~/.config/npm/tmp` or if the data is expected not to persist on reboot: * `/tmp/npm/tmp` * `/tmp/npm` ** Description changed: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ~♠ lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ~♠ apt-cache policy npm npm: Installed: 1.3.10~dfsg-1 Candidate: 1.3.10~dfsg-1 Version table: *** 1.3.10~dfsg-1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen - I expect the temporary directory of npm to be set either in `~/.cache/` - or in `~/.npm/tmp`. + I expect the temporary directory of npm to be set either in + `~/.cache/npm/` or in `~/.npm/tmp`. 4) What happened instead `npm` defaults to `~/tmp`. If the file `~/tmp` exists (and it does, as I use it as a `vim` buffer when working), `npm` has a really bad time (because the temp dir is a file!) I can only imagine the chaos if some other package decides to use `~/tmp` or `~/tmp/` ... I don't think this issue ever got pushed upstream, here it is on github: https://github.com/npm/npm/issues/2936 I propose it is moved to a directory that isn't as vaguely defined as `~/tmp` such as: * `~/.cache/npm/` * `~/.npm/tmp` * `~/.config/npm/tmp` or if the data is expected not to persist on reboot: * `/tmp/npm/tmp` * `/tmp/npm` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543797 Title: npm uses ~/tmp/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/npm/+bug/1543797/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
