Apart from doing yum update all, is there any way to update RHEL 7.2 to RHEL 7.2. AM looking for system packages alone to be updated and leave the application level to be in their current version.
I assume by system packages you mean the ones supplied from official RHEL repos, and by application level you mean third-party software installed on top of the RHEL system. If that's the case, then disable the third-party repos for the upgrading process. I.e. something like:
yum --disablerepo=* --enablerepo=rhel-7-server-rpms update
Alternatively, you can exclude specific packages from the upgrade. For that, you can use the versionlock yum plugin (available from the yum-plugin-versionlock package). Use it as follows:
yum versionlock <package>-*
This locks all packages whose names start with <package>- to their current versions.
Yet another method is to use the --exclude option of yum, or--to make it permanent--specify which packages to exclude in the yum.conf file. See How do I exclude kernel or other packages from getting updated in Red Hat Enterprise Linux while updating system via yum? for instructions on how to use those options.
Related
does anyone know how I could install MariaDB 5.5 server with Homebrew on Mac OS? I've tried running brew install mariadb#5.5 but it doesn’t work.
You can also Try Building it from source!
you can use Homebrew to build MariaDB from source.Its helpful if you want to use a different version of the server or enable some different capabilities that are not included in the bottle package or if you are having issues with the bottle package.
To build MariaDB Server with these engines, you must first install boost and judy.
And please can you be specific about the errors you encountered.
You might want to check this site:
Now a bit of background of my current setup:
I have Python3.3 running on Centos 6. I'm currently working on a web application using Flask that runs on Apache 2.2.15 with mode WSGI 4.5.3 and virtualenv 15.0.2.
pip --version pip 8.1.2 from /usr/local/bin/lib/python3.3/site-packages (python 3.3)
I have installed pysvn with pip and when I run pip show pysvn says
Location: /usr/local/bin/lib/python3.3/site-packages
755 permissions recursively set to /usr/local/bin/lib/python3.3/site-packages. And I passed --system-site-packages argument to virtualenv to use the global site packages.
Even when I try to import the package from python interpreter it does not work. So it is not specific to my virtualenv setup but rather a global problem.
I must mention that other packages installed with pip work perfectly fine (i.e. flask).
I've exhausted all other avenues before coming forward to you guys. Any suggestion would be highly appreciated as I ran out of ideas.
L.E.
I did manage to install it in the end. I'm not completly sure yet why and how but I presume is was compatibility issue.
First of all I have uninstalled svn 1.6+ and installed version 1.8.16 instead which seems to be tested against the latest two versions.
Second, I have uninstalled the troublesome pysvn instance and installed pysvn-1.8.0 workbench "sudo /var/www/FlaskApp/FlaskApp/flask/bin/pip install pysvn-1.8.0.tar.gz". In this case I have installed it my local environment. The 1.9.0 version of pysvn did not work.
L.L.E.
False positive, still doesn't work. I'm going to interact with svn via command line from my script.
L.L.L.E.
After installing svn 1.8.16 and svn-devel along with the rest of dependencies described in the readme file I have managed to successfully install it from the source fallowing the instructions.
Thanks for your help Barry.
pysvn is not available from PyPI because PyPI has no way to allow me to upload pysvn for each supported SVN version. Let alone deal with the issues of installing on a Linux distro given the choices for pysvn dependencies.
(APR, SVN, OpenSSL etc).
Fedora packages pysvn for the Fedora release.
I'm assuming that means it is on RHEL and therefore packaged by CentOS.
(But I do not have RHEL or CentOS to check this on)
If you find that a package is not available for your CentOs is not hard
to build pysvn on a linux distro. Get the source kit and follow the readme.html should get you going.
Barry (pysvn maintainer)
When I try to install a previous version of Cloudera with all packages(Cloudera Manager, CDH with all applications and so forth) through install manager binary always installs the lastest version of Cloudera (now 5.8) even if the manager installer bin was found in the Cloudera 5.4 directory in the repository. I want to install Cloudera 5.4. For that, I have found Cloudera 5.4 RPMs in the repository to install manually in RHEL but when I install them, yum finds dependency errors with the database and daemon packages perhaps because of a previous failure in the installation. Because of this I think this is not the best manner of install Cloudera 5.4. Anyone that knows how to install a previous version of Cloudera or have installed or have experience in that or can give me some advise on how to install it? Thanks!
While, I'm not clear on why you would want an older version of CM, you can adjust your cloudera-manager.repo file to point to the specific version you want. Something like this:
[cloudera-manager]
name = Cloudera Manager, Version 5.4.10
baseurl = https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.4.10/
gpgkey = https://archive.cloudera.com/redhat/cdh/RPM-GPG-KEY-cloudera
gpgcheck = 1
My CentOS 6.6 has sqlite3 3.6.20 installed, and I tried to update
by
yum update sqlite
but it shows 'No Package marked for update'
How can I install/update 3.7.7+ for using shared memory between instances?
Yum can only find newer versions of packages that are available in the yum repositories configured for the machine. If using the stock CentOS repository, SQLite 3.6.20 would be the latest.
You would need to either add a repository with a more recent version, find and download the new version of the software or download the source and compile/install.
From a quick Google search it does appear there are RPMs for CentOS 6 and SQLite 3.7.17.
I use Debian sid (amd64), rolling updates as often as weekly. I downloaded recently the desktop version 0.99.902 of RStudio from their offical site and issued (as root, of course):
dpkg -i rstudio-0.99.902-amd64.deb
to no avail:
dpkg: dependency problems prevent configuration of rstudio:
rstudio depends on libgstreamer0.10-0; however:
Package libgstreamer0.10-0 is not installed.
rstudio depends on libgstreamer-plugins-base0.10-0; however:
Package libgstreamer-plugins-base0.10-0 is not installed.
Newer versions (1.0-0) of these 2 packages are installed on the system, but those older ones (0.10-0) are not available anymore on the official Debian repos.
What should be done to have RStudio installed and fully operational under
Debian sid? I have, of course, installed R debs, from official Debian
repositories, without any issues...
Thanks for any help!
RStudio 1.0.153, released on July 20th 2017, depends on GStreamer 1.0 instead of GStreamer 0.10. It can be installed on modern Debian/Ubuntu without any additional setup, rendering this question and my answer obsolete.
To be more specific, there are two different DEB packages. One is aimed at Ubuntu 16.04 (or later) and Debian 9 (or later), comes only in 64-bit flavor and depends on newer GStreamer 1.0. Another package supports Ubuntu from 12.04 up to 15.10 and Debian 8 and it comes in both 32-bit and 64-bit flavors. This one still depends on older GStreamer 0.10.
Original answer remains below.
As of mid-2016, RStudio has hard dependency on GStreamer 0.10 and there is no way around it. You have to install libgstreamer0.10-0 and libgstreamer-plugins-base0.10-0 to use RStudio.
These packages can be easily pulled in from Debian Jessie (stable). Just add Jessie repository to your sources.list and use apt-pinning to give it lower priority:
# /etc/apt/sources.list:
deb http://httpredir.debian.org/debian jessie main
# /etc/apt/preferences.d/01_release:
Package: *
Pin: release o=Debian,a=unstable
Pin-Priority: 600
Package: *
Pin: release o=Debian,n=jessie
Pin-Priority: 10
Then issue apt-get update and follow up with apt-get install libgstreamer0.10-0 libgstreamer-plugins-base0.10-0.
If you have happened to put RStudio .deb file into local repository, then use apt-get install rstudio and GStreamer0.10 will be pulled in by dependency resolver. This has additional advantage of marking these libraries as automatically installed - they will be subject to automatic removal once RStudio drop them as dependency.
But will that break my system?
No.
Upstream developers designed GStreamer0.10 and GStreamer1.0 as co-installable and able to run at the same time (source). In fact, both were available in Debian repository since September 2012 up to April 2016.
In this pinning setup, packages from Jessie repository will be pulled in only when Jessie is the only provider of requested package. There is no risk of overwriting any package from unstable with older version from stable.
Why does RStudio depend on obsolete library?
Because GStreamer0.10 is the newest version available in both Debian Jessie and Ubuntu 12.04, two distributions they want to support.
RStudio will eventually have to upgrade their dependency to GStreamer1.0, as it will gradually become the only version available. I guess this change may be introduced in spring 2017. First, support for Ubuntu 12.04 will end in April. Rstudio is likely to bump base system requirement to 14.04 - one that has both GStreamer0.10 and 1.0. Second, Debian Stretch - that will have only GStreamer1.0 available - is expected to be released around that time.
I found Miroslaw's answer to be excellent. But, due to the passage of time you will need one more package: libssl1.0.0, so your setup apt-get will look like
apt-get install libgstreamer0.10-0 libgstreamer-plugins-base0.10-0 libssl1.0.0
Download libgstreamer0.10-0 for your machine from any of the mirrors.
Open terminal in the directory where the file is downloaded.
Install it using the command, sudo dpkg -i file.deb. Example sudo dpkg -i libgstreamer0.10-0_0.10.36-1ubuntu1_amd64.deb.
Now open the directory where rstudio.deb is located and install it in the same way.
Download the libraries
http://ftp.br.debian.org/debian/pool/main/g/gstreamer0.10/libgstreamer0.10-0_0.10.36-1.5_amd64.deb
http://ftp.br.debian.org/debian/pool/main/g/gst-plugins-base0.10/libgstreamer-plugins-base0.10-0_0.10.36-2_amd64.deb
Install them with gdebi or dpkg -i and that is it