The new version of the package u2622-persistent-session crashes my entire app with no hope to troubleshoot it, so naturally I wanted to downgrade it to 0.3.5 again but found it impossible.
I rolled back everything in git to the version where everything was working, no luck.
I deleted the package manually and did meteor add u2622:persistent-session#0.3.5, no luck.
I changed the value that says 0.4.4 in the file packages but it changes back immediately again.
What the heck do I do to downgrade a package?
Did you read the documentation from atmospherejs ? It should be
meteor add u2622:persistent-session#=0.3.5
(= after #)
Related
I am working on my package, which is hosted on github, using Visual Studio Code (1.67.1). I am using github desktop to push changes to the repository on github. This process works well. However when I re-install my package using:
library(devtools)
install_github("Ellesaere/tkis.package", dependencies=TRUE, force=TRUE)
I often find that an older version is installed, even though the github repository shows the correct version. I cannot figure out what makes it work, or not work. This is getting extremely frustrating, as I continuously find myself restarting R, reinstalling the package, hoping that it installs the correct version this time.
I was wondering if anyone could give some reasons why this could be happening.
I've come across a common problem but do not understand the logic of how R works.
So I had R 3.4 and all my libraries were in /usr/local/.../R/3.4 local direction. These libraries were installed using super user admin rights.
I've recently upgraded to R 4.0.0.2, and installed Rstudio, and do not run Rstudio as super user. I've created a new local direction ~/R/x86_ubuntu/4.0 local library.
Now the .libPaths() has the first entry as my local directory, and subsequent paths point to previous library paths.
So if i enter install.packages(foo), the error says,
This package package ‘foo’ was installed before R 4.0.0: please re-install it.Error: package ‘dotCall64’ could not be loaded.'
However I am re-installing the package from source, yet I get the error that I could not re-install it.
I have also tried the install.updates(check=TRUE,ask=FALSE) command and this still gave the same answer.
There are similar posts to this problem, but I just need an explanation as to why this is failing?
Is it because of the library paths conflict? R is trying to load a previous older 3.4 library directory?
This does not make sense because I've downloaded all my 4.0 libraries from source? why is it still pulling from the older versions?
Should I just remove other library paths? Should I delete my old previous library folders?
So, anytime a new 3.X R version rolls out my work is stalled because it simply creates a 3.X folder for packages and disregards all the previously installed ones which are in the folder with a previous R version name. I use this workaround:
.libPaths(.libPaths(), "path_to_dir_w_old_packages"), but I have to do it everytime I launch my RStudio. I tried to manually reinstall my packages but as always there are some scientific packages that are old and maintained poorly, so there are no suitable versions for 3.X version (but libs loaded from old dir work just fine). Does anyone by chance know any solution for this annoying incommodity?
In R 3.4.3 (Windows 10) while loading the packages arulesViz:
Error: package or namespace load failed for ‘arulesViz’: object ‘cividis’ is not exported by 'namespace:viridisLite'
I tried to uninstall and install, but did not help. What is wrong and how can i correct it?
Basically you need to install the dependencies of arulesViz.
I tried with Scatterplot3d , viznetwork, vcd, virdislite.
I also faced similar problem.
This problem can be resolved by installing package "viridisLite" along with "arulesViz"
for me it worked no need to reinstallthe R or Rstudio
It get solved , after reinstall RStudio + removed old version of R.
Disadvantage is all libraries will also get removed. So you have to load again.
I had the same issue with the seriation package. Ultimately I found that I just had to uninstall and reinstall r and r studio. Then i ran update.packages() and I had no problems.
This is a pain, as there are several packages with dependencies for packages which in turn import viridisLite, and this error is very opaque for users...
One thing I've found works (apart from manually install.packages("") each package mentioned in the error) is to switch repositories to the RStudio-maintained Cloud repo. (repo 0).
The problem seems to have hit people with a default repo that has incompatible versions of packages at the time people use it, and the cloud repo seems to avoid/not suffer from this problem.
Hope this helps
Currently the latest public version of the Spiderable package is 1.0.7 (atmosphere link). However on Github the version has been bumped to 1.0.8 (4 days ago).
I need the features from the 1.0.8 update. What's the best way for me to use the 1.0.8 version? I've tried:
meteor add spiderable#1.0.8
But it didn't work, the output was: error: no such version spiderable#1.0.8 .
This version of spiderable has not yet been published by MDG. This is why it says no such version.
While a package is being developed the version may be higher than the version available for use. When it has been tested its usually published along the next meteor version.
There may still be more changes to the package until its published.
If you want to use the package anyway you can copy the spiderable directory from github into a packages/spiderable directory. This may not work with certain dependency errors depending on whether another package using spiderable is required.
The second is to use the github version of meteor. Which is to clone the meteor project using git clone https://github.com/meteor/meteor then use the meteor binary (with the full absolute path) to run your project instead of meteor on its own.