search

vipm-io / vi-tester

VI Tester for LabVIEW
BSD 3-Clause "New" or "Revised" License
28 stars 26 forks source link

Package 3.0.2.294-1: VIPM could not install the package #60

Open kosist opened 3 years ago

kosist commented 3 years ago

While installing package v. 3.0.2.294-1 there is following error:

Error JKI VI Tester

Tested with LabVIEW 2013, 2015 SP1. Previous version could be installed without the issues.

jimkring commented 3 years ago

For some reason VIPM doesn't seem to have permission (Error 8 is a Permission Issue).

Sometimes this happens when running VIPM as administrator -- the cached files become not writable by other users.

Can you look at what the permissions are on that file? It would help us figure out how to avoid the problem in the future.

Note: You can probably get the error to go away by deleting that file and trying the install again. But, it would be great if you could look at the permissions on it, first.

Thanks,

kosist commented 3 years ago

Thank you - I've checked permissions, and it was really a problem.

Permissions

After permissions were fixed, it was possible to install the toolkit. Moreover, after I've unistalled it, removed package from cache and installed it again (so VIPM downloaded package from repository) everything was fine.

Not sure why it has saved package with bad permissions - I launch VIPM all the time with the same permissions level. But, it does not matter now, because root cause is clear. Thank you!

jimkring commented 3 years ago

OK. Here are some other questions, if you know the answers:

kosist commented 3 years ago

It seems that really problem has occurred due to installing packages with Administrative rights. Now when I check spec files - most of them have those wrong permissions (owner of the file - is admin account). Freshly-installed VI Tester's spec has owner set to my local account. I've used my another account on this PC for a while, and then switched to another local account. Maybe it caused the issue. But I'm not sure that the very first time VIPM was launched explicitly with the elevated rights (so it downloaded all latest spec files and set their permissions like that). But overall bug is on my side, sorry for disturbing - now I can install package without the issues... Thanks a lot!

jimkring commented 3 years ago

Thanks for that detailed explanation. It’s really helpful for us in coming up with a long-term solution in VIPM and also in helping other users who experience the same problem to find a workaround.-- Jim Sent from my mobile.