I see that the RPM packages are named as below , but then I am confused about how a RPM released with new patch named ?
For e.g
RPM packages typically have file names like foo-1.0-1.i386.rpm.
The file name includes the package name (foo), version (1.0), release (1),
and architecture (i386).
Now I have a unix odbc installed on my box whose version is unixODBC-2.2.14-12.el6_3.x86_64 . There was a bug in unixodbc which was resolved in 2.2.14p2-1 so I am wondering which unixodbc rpm should I be looking for
does 2.2.14p2-1 means unixODBC-2.2.14-21.el6_3.x86_64 or unixODBC-2.2.14-12.el6_3.x86_64 . I know all RPMs created for el6 with this patch and above will have fix but I see the RHEL has just the below three version unixODBC-2.2.14-12.el6_3.x86_64 , unixODBC-2.2.14-11.el6_3.x86_64 and unixODBC-2.2.14-14.el6_3.x86_64 in its repo .
The usual convention is "version"-"release" with an optional "dot-plus-distribution" as part of the release. The version matches upstream; the release is changed by the packager (each time they add a patch or rebuild for other reasons). See also https://fedoraproject.org/wiki/Packaging:Versioning.
In your example, 2.2.14p2-1 would mean unixODBC's version number is "2.2.14p2" and it is the first time the vendor packaged it. That may or may not be included in 2.2.14-14.el6_3, the 14th release of "2.2.14" for CentOS 6.3. I say "maybe" because the "p2" of the upstream could be indicating a patch that CentOS already applies that the upstream has accepted. Or they just haven't downloaded and built the newest version yet.
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.
I am planning to upgrade artifactory-pro from 4.14.2 to 5.7. Has anyone done this so far? We use npm, bower, debian, yum repositories. Any recommendation or insight is appreciated.
As I see it, the upgrade depends on two main factors:
Your installation type(ZIP/RPM/RPM OSS/Debian/Docker). Here you can find detailed instructions for each type:
ZIP installation
RPM installation
RPM OSS installation
Debian installation
Docker installation
In case you use an HA cluster, here are the instructions.
While no special operations are required except those are mentioned in the instructions - please pay attention to updates and other special instructions since there are specific instructions to upgrading from Artifactory 4.x to 5.4.x and above. As can be seen here (for example).
Like in any other upgrade process, make sure you have a full system backup (Artifactory configuration, metadata, and artifacts)
I just did a fresh install of Fedora 25 (followed by an install of dotnet core 1.1) to explore the possibilities of doing some dotnet core development in an linux environment. On attempting to add my first package I received the following error:
No executable found matching command "dotnet-add"
I have seen some similar errors in other SO posts, but nothing that seems to be helping this issue. I attached some images below of the error, dotnet version info, system path, and dotnet location.
Thanks ahead of any tips!
You have installed a version of the dotnet SDK ("CLI" / dotnet-dev package) of the preview2 time, which is still project.json based. This version of the CLI does not contain the dotnet add set of verbs. These were publicly released with the 1.0.0 version. (at the time of writing, the current version of the SDK / CLI is 1.0.4).
Depending on which instructions you followed to install the components, make sure to update to new versions of the SDK / CLI (e.g. microsoft's install instructions for Fedora).
Note that the version of the SDK / CLI is a different one that the version of the runtime(s) on the machine.
Had the same trouble running VS 2017 Version 15.3.5 found a very helpful article
http://thedatafarm.com/data-access/no-executable-found-matching-command-dotnet-ef/
My Basic problem is the tooling is split into two:
One for CLI: Microsoft.EntityFrameworkCore.Tools.DotNet
One for Powershell: Microsoft.EntityFrameworkCore.Tools
Riak has great documentation on how to upgrade Riak if it was initially installed via a package ( http://docs.basho.com/riak/1.2.1/cookbooks/Rolling-Upgrades/ ). But how do you upgrade Riak if you originally downloaded/installed it from source?
The current version of Riak I'm using is 1.0.
It's pretty much the same except in step 3 instead of
sudo dpkg -i <riak_package_name>.deb
you just download the tarball with new version and install it as you did first time.
But frankly speaking in 99% cases it's easier to do it via packages. I believe you can upgrade to packaged version from manually installed one by following their rolling update instructions precisely.
I have an RPM package for my application and the path of the installation is /company/application/version.
I am finding this difficult as it is a unix platform and there is no registry concept.
I need few things to be clarified:
How can i check the previous installed version number?
Every time I install my different version application all gets installed (i.e 2.5 and 2.6 both are considered as 2 different softwares because of the installation directory structure.)
How can I stop the newer version when old is already installed?
Without seeing the spec file, this is just shooting in the dark, but I would guess you are probably missing the 'Version' tag in your spec file. See http://www.rpm.org/max-rpm/s1-rpm-inside-tags.html. In general, Maximum RPM is a good resource.