I am trying to write a WPF application using Caliburn.Micro but want to start with the 4.0.62-alpha version (I know it is alpha, by time I am ready the Beta will be out) If I install 3.0.2 I can't upgrade to 4.0.62alpha for Core and Micro, if I on;y install 4.0.6.2-alpha then the Bootstrapper is missing.
I tried installing just the -alpha Micro and .Core, also tried installing 3.0.2 and replacing .Core and .Micro. All were blocked due to conflicting dependencies.
Can I only install the -alpha from source code?
Related
When we ssh onto this Linux server, it says Welcome to Ubuntu 16.04.7 LTS (GNU/Linux 4.4.0-193-generic x86_64), so this is the type of server we are on.
When we run R to launch R in the server from terminal, and then version, we get:
What is the easiest way to upgrade from version 3.4.4 to version 3.5.3? We don't want to upgrade to v4 or to the latest version quite yet until we ensure no breaking issues with our codebase on R v4, however we would like to make this upgrade to 3.5.3 so we can run an R library that requires 3.5.3+.
How can we do this from the command line on the server here, and after switching from 3.4.4 to 3.5.3 do we then need to re-install all R libraries on the server as well? I'm worried if I start running stuff from the command line and I mess up that I'll break our current R app.
I would be surprised if there is a .deb available for this OS release/R release combination.
This page only offers R 4.1, but as far back as 16.04 LTS
This page offers older R versions, but only back to 18.04 LTS
It's also possible that one of the backports on the Debian packages page would work on your system (it reports that 3.5.3 is available for Debian "jessie", although I have no idea how that lines up with Ubuntu releases).
I guess it's possible that one of those .debs works for your system though ... ? If you do install from .deb, you may have to be careful not to clobber your current version (e.g. using the --instdir argument to dpkg).
Building from source:
download the source tarball for R 3.5.3
untar, ./configure, make, sudo make install (assuming you have all the necessary development tools, system libraries, etc.; you'll have to troubleshoot/install as you go along)
It might be worth ./configure --prefix=/path/to/testdir to put the new version in a completely separate location, just to make extra-sure you don't stomp on your current install. (This would also simplify the library-path stuff below.)
Packages do need to be re-installed when switching major versions (e.g. 3.4.x to 3.5.x); one way to do it is to copy the system library of packages to a new place (adjust library paths as necessary; see R installation and administration manual).
Then, you should be able to update.packages(checkBuilt=TRUE, ask=FALSE) to update everything.
The tricky spots are (1) getting the library paths right (this will depend a bit on how things are set up in your existing installation; (2) it's conceivable that some current versions of packages on CRAN will fail to re-install/re-build under R 3.5.3. devtools::install_version() would help, although you'd have to track down the correct version manually. I recall someone posting about a package that would install an archived version by date, which could save a lot of poking around ...
I'm trying to open my Boilerplate Application(.NET Core 3.1)in VSCode in Linux but below exception, keep appeared for me. Is there any difference between .NET Core for Linux and for Windows or What is the problem?
Detected package downgrade: Abp.ZeroCore from 5.7.0 to 5.1.0. Reference the package directly from the project to select a different version.
No this is not related to the OS that you run your application.
As stated in the error message there a downgrade in one of your nuget packages.
Go to your Boilerplate.csproj and try to manually set the version of Abp.ZeroCore nuget package from 5.1.0 that it is currently to 5.7.0.
I am using Realm Object Server 1.8.3 manually installed from a .deb file (found on packagecloud.io) on my Ubuntu 16.10 and I would like to upgrade to a 2.x release (2.5.1 is the latest at the time of writing).
Unfortunately, packagecloud.io does not have 2.x packages (except some 2.0.0 release candidates and alpha versions) available and the installation instructions are using a different mechanism and do not integrate with systemd as far as I can tell.
Any hints on how to best do this or where to find a package?
There's no .deb file because ROS 2.x is published as an npm package. While you're right that there's no integration with systemd, because it's an npm package, you can use pm2 to daemonize your install (pm2 integrates with systemd).
Before you can daemonize it though, you'll need to follow the step-by-step guide on upgrading ROS 1.x to 2.x (won't repost it here as it's fairly lengthy and may become obsolete as new versions of ROS are released).
After you've done that, running it with pm2 is fairly straightforward:
npm install -g pm2
pm2 start path/to/myserver/dist/index.js
I follow the instructions to install meteor 1.6 on Windows(10) as stated on Meteor.com (choco install meteor) and it's installed a meteor v0.0.2 ?
When I try to run any meteor command I get: bash: meteor: command not found
and when I try choco upgrade meteor I get:
$ choco upgrade meteor
Chocolatey v0.10.8
Upgrading the following packages:
meteor
By upgrading you accept licenses for the packages.
meteor v0.0.2 is the latest version available based on your source(s).
Chocolatey upgraded 0/1 packages.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
I tried choco uninstall meteor and then reinstall choco instlal meteor but same issue. Searching around online a little I found this page:
https://chocolatey.org/packages/meteor
I do have meteor installed and running on version 1.6.0.1 on Window 10's Ubuntu bash which was installed via curl https://install.meteor.com/ | sh
Following on from above post https://stackoverflow.com/a/47967277/642729 by Gary Ewan Park. The below comment on https://chocolatey.org/packages/meteor clarifies the Chocolately/Meteor versioning
The current version of Meteor is 1.6;
is this the version in the 0.0.2 Chocolatey package?
[Garrie Powers • 2 months ago]
The version number of the Chocolatey package is the version of the installer.
Meteor is unique in the way it works in that all versions
are capable of springboarding to other versions.
Therefore, in the same way as the Unix installer installs the latest version,
the Chocolatey installer will always install the latest version.
So at this exact moment, the answer to your question is "yes"!
[Jesse Rosenberger Garrie Powers • 2 months ago]
The best advice would be to reach out to the maintainers of that package of chocolatey.org. This can be done by clicking on the "Contact Maintainers" link of this page:
https://chocolatey.org/packages/meteor
It would seem that the creators of the application, also own the Chocolatey package, so hopefully they will get back to you.
From the official installer github:
The version of this Meteor installer is not to be confused with Meteor itself. Meteor, once installed, will always "springboard" to (download, install and run) the correct version of Meteor necessary for the application being executed.
...
When necessary, specific versions of Meteor can be installed using
Chocoloatey's --params argument which will download that specific
version from Meteor's installation server. For example, to install
Meteor 1.5.4.4:
C:> choco install meteor --params="'/RELEASE:1.6.0.1'"
Note: Prior to
Meteor 1.6, 64-bit versions were not available. Therefore, in order to
install versions prior to Meteor 1.6, you'll also need to pass
Chocolatey's --x86 option when running choco install on 64-bit Windows
platforms. For example:
C:> choco install meteor --x86 --params="'/RELEASE:1.5.4.4'"
I am trying to install iPDC on a Centos unix laptop.
I am getting a make error when I attempt to install the programme - I have attached a screenshot of my problem.
The command run is sudo make install and I am attempting to install as the root user.
Your installed GTK version is probably too old to support this software. GtkBuilder (a component within GTK) showed up at version 2.12. To find out what version you have, run pkg-config --modversion gtk+-2.0 at the command line. But that version has been around for quite some time. What version Centos are you running? I assume 5, which is quite old.
Upgrading GTK can be tricky, as most of your desktop software relies on it. If you're in for an adventure, the "easiest" would be to upgrade your Centos OS (to 6.x). You might be able to compile a more recent GTK from source and keep it separate from your system GTK, but that will take some patience.
It seems that GTK is not installed.
Try something like: yum install gtk2 or yum install gtk2-devel