-
Notifications
You must be signed in to change notification settings - Fork 435
Phantomjs 1.9.16 does not install on Ubuntu 14.04 running on Vagrant shared folder #341
Comments
fwiw, I tried installing phantomjs on a vagrant shared folder on ubuntu, On Tue, May 19, 2015 at 8:59 PM, Nick Barrett [email protected]
|
Was it a Windows 7 x64 host? |
|
i pushed a phantomjs 1.9.17 with some additional logging around this, mb try again and see what happens? |
I had a similar issue on Debian Jessie. It seems like the install script calls The following helped in my case (executed as root):
|
given that it's been a month and no further repro steps, there's not much we can do about this. i will assume the 1.9.17 update fixed it. closing this bug. |
Thanks @nicks. I haven't found that passage, because I have searched for the error message, which is not provided by your mentioned doc. |
C:\Users\jlopesde\heroku\desolate-taiga-1397>npm install
Download already available at C:\Users\jlopesde\AppData\Local\Temp\phantomjs\pha npm ERR! [email protected] install: |
Good day, @nicks. I ran into this issue myself. My set up is like @njbarrett - I have Virtualbox 4.3 running with Windows 7 x64 as host and Ubuntu 14.04 as the guest. When I attempt to install the latest phantomjs for a project on a shared folder from inside Ubuntu, I get the same ENOTDIR error. If I specifically install phantomjs 1.9.13, I don't see this issue. I noticed that #279 was resolved by getting a fix from the fs-extra package, but perhaps it is still broken somehow for this particular setup. Maybe we can get the maintainers of that package to verify and fix that bug or, alternatively, maybe phantomjs can find a way to not depend on that package. |
@chucksplatt the approach in 1.9.13 does not work in newer versions of node, so rolling back is not an option. I fiddled for about an hour with the OP's repro steps and was not able to repro the issue. I will try fiddling with your repro steps later tonight or tomorrow; it might be a separate issue. |
So coming back to this issue I recently installed 1.9.17 on the same platform as described in my OP.
|
I spent some more time trying to reproduce this, and was not able to repro with the steps provided. At this point, I do not plan on spending more time on this. My theory is that it's a problem with the permissions on your virtual drives. If someone can prove that this is a problem with the phantomjs package, you are more than welcome to debug the issue and either send us a test case or send us a patch. |
oooooooo i think i was able to come up with a repro case, but it may be different than the issue you're seeing. i think there are some virtual file systems that report cross-file-system move errors incorrectly. will see if we can make upstream more robust against bad errors. |
Thanks for continuing to investigate! Much appreciated. |
I was able to test this today and can confirm it now works and installs without issues! Thank you. |
The issue, as originally reported in #279 is still an issue on Ubuntu 14.04 running on a Vagrant shared folder.
The text was updated successfully, but these errors were encountered: