Hi Jim!
Found:
a) the reason (for all pkg updates giving "non-zero exit")
and
b) a workaround
(maybe you can suggest shorter solution to avoid this problem for future pkg updates).
So, this is the solution...
a) the reason:
I had an initial ".Rprofile" file,
which became effective
every time I started Rstudio.
It included this command:
...
.First <- function() {
autoloads <- c("tidyverse","visdat","skimr")
options(defaultPackages = c(getOption("defaultPackages"), autoloads))
}
Somehow, the pkgs autoloaded (above),
interfered with the update of purrr and other pkgs!.
...
b) my (long) workaround:
I commented-out the above code
in my .Rprofile file: (w/ CTRL-SHIFT-C)
# .First <- function() {
# autoloads <- c("tidyverse","visdat","skimr")
# options(defaultPackages = c(getOption("defaultPackages"), autoloads))
# }
I then re-started my Rstudio
with the temporary commented-out .Rprofile code,
and clicked [Update] in the Packages pane.
Great!.
ALL pkgs updated fine!.
(no more "non-zero exit" status!).
YAY!
Then... I uncommented
the commented .Rprofile code (CTRL-SHIFT-C again),
saved and sourced it,
and restarted Rstudio again.
JIM,
- maybe you can suggest a shorter solution
with more practical solution/steps,
to avoid this problem for future pkg updates.
Instead of this LOOOONG sol
every time there is a PKG update...
Hey!
My hair is already turning white, as it is 