R `update.packages()` deletes some packages
up vote
0
down vote
favorite
It seems that almost every time I run update.packages()
, most of the packages are updated, but also a few are removed and not replaced. This time, I copied the activity trail, and after discovering some packages were missing, it appears that those deleted packages correspond to messages like this:
package ‘MASS’ successfully unpacked and MD5 sums checked
Warning: cannot remove prior installation of package ‘MASS’
While the message says the package wasn't deleted, it was. Apparently, update.packages()
thinks it wasn't, so it doesn't replace it with the new code that it had downloaded.
Losing a sporadic few packages that I thought I was updating is extremely annoying; so I would like to understand what it is that's going wrong so I can avoid it.
I may have a clue about what happens. I use RStudio for most of my work, but I usually bring up a new RGui session and run update.packages()
there, so I can keep working while all those updates are being done. Is this likely to be what is causing these deletions? And if so, why?
r package updates
add a comment |
up vote
0
down vote
favorite
It seems that almost every time I run update.packages()
, most of the packages are updated, but also a few are removed and not replaced. This time, I copied the activity trail, and after discovering some packages were missing, it appears that those deleted packages correspond to messages like this:
package ‘MASS’ successfully unpacked and MD5 sums checked
Warning: cannot remove prior installation of package ‘MASS’
While the message says the package wasn't deleted, it was. Apparently, update.packages()
thinks it wasn't, so it doesn't replace it with the new code that it had downloaded.
Losing a sporadic few packages that I thought I was updating is extremely annoying; so I would like to understand what it is that's going wrong so I can avoid it.
I may have a clue about what happens. I use RStudio for most of my work, but I usually bring up a new RGui session and run update.packages()
there, so I can keep working while all those updates are being done. Is this likely to be what is causing these deletions? And if so, why?
r package updates
Well, "unpacked" doesn't mean removed. Nothing in that message means that MASS has been removed. Messages like that usually come up for me when I have the package actively loaded when i'm trying to update it and it can't be unloaded because it's being used. It's best to update in a fresh session where you have no packages loaded. It's probably that they aren't deleted, but they may become incompatible with the other versions you have install.
– MrFlick
Nov 19 at 20:07
No. I am not imagining this. The package was actually removed. I can see that by looking st the library directory where the folder no longer exists.
– rvl
Nov 19 at 20:10
I edited the question in an attempt to clarify.
– rvl
Nov 19 at 20:49
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
It seems that almost every time I run update.packages()
, most of the packages are updated, but also a few are removed and not replaced. This time, I copied the activity trail, and after discovering some packages were missing, it appears that those deleted packages correspond to messages like this:
package ‘MASS’ successfully unpacked and MD5 sums checked
Warning: cannot remove prior installation of package ‘MASS’
While the message says the package wasn't deleted, it was. Apparently, update.packages()
thinks it wasn't, so it doesn't replace it with the new code that it had downloaded.
Losing a sporadic few packages that I thought I was updating is extremely annoying; so I would like to understand what it is that's going wrong so I can avoid it.
I may have a clue about what happens. I use RStudio for most of my work, but I usually bring up a new RGui session and run update.packages()
there, so I can keep working while all those updates are being done. Is this likely to be what is causing these deletions? And if so, why?
r package updates
It seems that almost every time I run update.packages()
, most of the packages are updated, but also a few are removed and not replaced. This time, I copied the activity trail, and after discovering some packages were missing, it appears that those deleted packages correspond to messages like this:
package ‘MASS’ successfully unpacked and MD5 sums checked
Warning: cannot remove prior installation of package ‘MASS’
While the message says the package wasn't deleted, it was. Apparently, update.packages()
thinks it wasn't, so it doesn't replace it with the new code that it had downloaded.
Losing a sporadic few packages that I thought I was updating is extremely annoying; so I would like to understand what it is that's going wrong so I can avoid it.
I may have a clue about what happens. I use RStudio for most of my work, but I usually bring up a new RGui session and run update.packages()
there, so I can keep working while all those updates are being done. Is this likely to be what is causing these deletions? And if so, why?
r package updates
r package updates
edited Nov 19 at 20:43
asked Nov 19 at 19:58
rvl
1,7601613
1,7601613
Well, "unpacked" doesn't mean removed. Nothing in that message means that MASS has been removed. Messages like that usually come up for me when I have the package actively loaded when i'm trying to update it and it can't be unloaded because it's being used. It's best to update in a fresh session where you have no packages loaded. It's probably that they aren't deleted, but they may become incompatible with the other versions you have install.
– MrFlick
Nov 19 at 20:07
No. I am not imagining this. The package was actually removed. I can see that by looking st the library directory where the folder no longer exists.
– rvl
Nov 19 at 20:10
I edited the question in an attempt to clarify.
– rvl
Nov 19 at 20:49
add a comment |
Well, "unpacked" doesn't mean removed. Nothing in that message means that MASS has been removed. Messages like that usually come up for me when I have the package actively loaded when i'm trying to update it and it can't be unloaded because it's being used. It's best to update in a fresh session where you have no packages loaded. It's probably that they aren't deleted, but they may become incompatible with the other versions you have install.
– MrFlick
Nov 19 at 20:07
No. I am not imagining this. The package was actually removed. I can see that by looking st the library directory where the folder no longer exists.
– rvl
Nov 19 at 20:10
I edited the question in an attempt to clarify.
– rvl
Nov 19 at 20:49
Well, "unpacked" doesn't mean removed. Nothing in that message means that MASS has been removed. Messages like that usually come up for me when I have the package actively loaded when i'm trying to update it and it can't be unloaded because it's being used. It's best to update in a fresh session where you have no packages loaded. It's probably that they aren't deleted, but they may become incompatible with the other versions you have install.
– MrFlick
Nov 19 at 20:07
Well, "unpacked" doesn't mean removed. Nothing in that message means that MASS has been removed. Messages like that usually come up for me when I have the package actively loaded when i'm trying to update it and it can't be unloaded because it's being used. It's best to update in a fresh session where you have no packages loaded. It's probably that they aren't deleted, but they may become incompatible with the other versions you have install.
– MrFlick
Nov 19 at 20:07
No. I am not imagining this. The package was actually removed. I can see that by looking st the library directory where the folder no longer exists.
– rvl
Nov 19 at 20:10
No. I am not imagining this. The package was actually removed. I can see that by looking st the library directory where the folder no longer exists.
– rvl
Nov 19 at 20:10
I edited the question in an attempt to clarify.
– rvl
Nov 19 at 20:49
I edited the question in an attempt to clarify.
– rvl
Nov 19 at 20:49
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53381782%2fr-update-packages-deletes-some-packages%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Well, "unpacked" doesn't mean removed. Nothing in that message means that MASS has been removed. Messages like that usually come up for me when I have the package actively loaded when i'm trying to update it and it can't be unloaded because it's being used. It's best to update in a fresh session where you have no packages loaded. It's probably that they aren't deleted, but they may become incompatible with the other versions you have install.
– MrFlick
Nov 19 at 20:07
No. I am not imagining this. The package was actually removed. I can see that by looking st the library directory where the folder no longer exists.
– rvl
Nov 19 at 20:10
I edited the question in an attempt to clarify.
– rvl
Nov 19 at 20:49