Is it possible to install specific version of scala via rscala::scalaInstall() ?
Currently it installs 2.12.1 which my project doesn't support yet.
I'm also ok with installing 2.11.8 manually but then it's unclear to me how to point R to it. Shall I add SCALA_HOME env var to script that launches RStudio or is there better way ?
Just make sure to add scala to your path and you should be fine.
Source: https://cran.r-project.org/web/packages/rscala/README
Related
I am aware how to silently install 'R for Windows', but how could I update an existing installation silently to a new version?
Install switches I am currently using:
\\foo\R\R_4.0.5\R-4.0.5-win.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /ALLUSERS /LANGUAGE=en /COMPONENTS="main, x64, translations" /DIR="C:\Program Files\R"
For me, it seems like there is no supported update/upgrade switch. Just installing a new version over an existing one results in just having 2 versions listed in appwiz.cpl.
Forcing the same install dir is not helping either, as you still end up with 2 installations, just in the same folder.
Any hint is appreciated. Thanks in advance.
UPDATE:
I am trying to keep the installations on several machines aligned - therefor it would be helpful to update all machine installations periodically to the latest version and ensure the software inventory solution is not reporting N versions on a single machine.
R is designed so that you can have multiple versions installed simultaneously. This is why each version installs into a different directory.
The canonical way to handle this is to check a registry key for the latest installed version, but if you want to avoid messing with the registry, you can try this:
Install into a custom directory
When it comes to upgrading, move that directory to a temporary location
Install the newer version into the original location
If it works, delete the temp location
If it doesn't, delete the failed install and restore the original
Caveat: untested.
help regarding the issue below would be really appreciated :
Command 'Q#: Create new project...' resulted in an error (Running the contributed command: 'quantum.newProject' failed.)
I was trying to follow this exercice : https://learn.microsoft.com/fr-fr/learn/modules/qsharp-create-first-quantum-development-kit/2-install-quantum-development-kit-code
after downloading and running the latest versions of .NET CORE, VSCODE, I can run "Q# Install command line project templates" but can't run "Q# Create a new project : See screenshot1 screenshot 2 CODE SOURCE ERROR
I already done this exercice in May last year but for some reasons I get stuck at the very beginning of the process now.
Could it be a version issue ? I remember that the tutorial was different (May 2020) than the one above I shared to you. Unfortunately I can't find the previous tutorial as it has been updated since.
I tried to uninstall the latest versions to reinstall the versions I downloaded in May : useless, I get the same issue.
Many thanks for you help !
I decided to go with an older version v0.14.2011120240
It seems the new version isn't stable yet.
Install NodeJS: https://nodejs.org/dist/v14.15.4/node-v14.15.4-x64.msi
Then restart VS Code.
"The below steps currently has a dependency to install node.js including npm. We are working on removing that dependency. Alternatively, use our the command line templates to create a Q# project , or use Visual Studio."
https://learn.microsoft.com/de-de/azure/quantum/install-command-line-qdk?tabs=tabid-vscode
I have configured Julia portable or standalone according to the link:Julia portable or standalone
But I want to update to the latest version of Julia 1.5.1.
How to proceed?
Should I add all the packages again?
Is there a way to import it to the new version?
Julia does not support version upgrade. It perhaps might work for some packages but you are always risking to running into issues.
Hence you need to delete the .julia folder (or set a new JULIA_DEPOT_PATH location which is configured by system variable) and just reinstall all the packages.
However if you for some reason strongly want to reuse the .julia folder you can try:
https://discourse.julialang.org/t/a-proper-introduction-on-how-to-update-julia-somewhere-accessible/28166
I got error message, running meteor 1.1.0.3
> ~/.meteor/meteor --version
Meteor 1.1.0.3
> ~/.meteor/meteor
Sorry, this project uses Meteor 1.1.0.2, which is not installed and could not be downloaded. Please check to make sure that you are online.
Shouldn't 1.1.0.3 be backward compatible? Can someone tell me how to get earlier version of Meteor
Meteor uses strict version requirements. So meteor-tool will try to download the exact version you specified in your project. If you are indeed not online and can't change that, or just want to start using the latest version that you seem to have installed, then just edit your .meteor/release file and manually change the meteor version to 1.1.0.3.
How do I find out what is holding my app up from updating? I keep getting the 'This project is at the latest release which is compatible with your current package constraints.' message.
Here is the output from the update command:
Refreshing package metadata. This may take a moment.
Figuring out the best package versions to use. This may take a moment.
Figuring out the best package versions to use. This may take a moment.
Figuring out the best package versions to use. This may take a moment.
This project is at the latest release which is compatible with your
current package constraints.
My packages.js looks like so:
# Meteor packages used by this project, one per line.
#
# 'meteor add' and 'meteor remove' will edit this file for you,
# but you can also edit it by hand.
accounts-base
accounts-password
alanning:roles#=1.2.9
arunoda:npm#0.2.6
ch-activity
ch-activityreport
ch-arrestreport
ch-assetreport
ch-citation
ch-fieldinterviewreport
ch-incidentreport
ch-inspectionreport
ch-location
ch-media
ch-narrative
ch-organization
ch-person
ch-property
ch-signature
ch-vehicle
cmather:iron-router#0.8.2
coffeescript
copleykj:mesosphere#0.1.9
d3
dash-patrol
email
less
mizzao:bootboxjs#4.2.1-master.1
mrt:accounts-ui-bootstrap-3#=0.3.3
mrt:leaflet#0.3.8
mrt:mongo-counter#1.1.0
notices
sacha:spin#2.0.4
standard-app-packages
tsega:bootstrap3-datetimepicker#=0.2.0
I have migrated all the ch-* and dash-* packages to the new format. Those are local, in app, packages. Those cannot be in public repositories.
Try replacing
cmather:iron-router#0.8.2
with
iron:router#0.9.1
in your packages file.
I'm think it may be because not all your packages are compatible with Meteor 0.9.0
If you want to check what packages are currently compatible enter this code:
meteor search (Package Name)
By default meteor will only return compatible packages, so you can find which packages aren't working by searching each one. If you can't find the package, then its probably not compatible and you aren't going to be able to run the latest version of Meteor unless you remove it.
Don't worry though! While Meteor 0.9.0 is quite buggy, they are working hard to update all the packages and patch the bugs. Just give it a few weeks to sort itself out if that doesn't work :)
Best Of Luck! Hope This Helped!
Meteor search is included in the latest release. Docs: http://docs.meteor.com/#meteorsearch
Try running this command and you should be able to access meteor search
meteor update
Also, the update should tell you if there's a package update available, although I had to run update (packagename) on each starred package for it to update
meteor update aldeed:collection2
I found that I had to remove my ~/.npm directory and run meteor again to resolve some npm dependencies I had. Perhaps you have some npm dependencies as well?