Hot answers tagged yum
The correct fix is to update your SSL certificates. sudo yum upgrade ca-certificates --disablerepo=epel You need to disable the epel repo so that this command will succeed. After you update your certificates you can use yum normally as EPEL will work again.
You can use: yum -y install packagename The "-y" implies "yes".
With yum-utils installed, repoquery will provide the information you seek (here 'epel' being the repository). └─[$]> repoquery -i cherokee Name : cherokee Version : 0.99.49 Release : 1.el5 Architecture: i386 Size : 8495964 Packager : Fedora Project Group : Applications/Internet URL : ...
On my CentOS 6.2, this worked: sudo yum install httpd-tools
As you can see from the output, the release version has changed from 6.6 to 6.7: centos-release.x86_64 6-7.el6.centos.12.3 base So this is perfectly normal. http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.7
I just had to install this on my CentOS 6 server since psycopg2 required pg_config. Boo yah: yum install postgresql-devel Update If you still encounter issues with pg_config, you may need to add it to your PATH, e.g.: export PATH=$PATH:/usr/pgsql-x.x/bin where x.x is your version, such as /usr/pgsql-9.2./bin.
Use the EPEL (Extra Packages for Enterprise Linux) repository. The easiest way to enable it is by installing the epel-release package. Here's how if you have RHEL 5 x86_64: [root@localhost]# rpm -Uvh http://dl.fedoraproject.org/pub/epel/5/x86_64/epel-release-5-4.noarch.rpm [root@localhost]# yum install git
From yum -h: --nogpgcheck disable gpg signature checking
You can discover which package contains the program you want using yum provides: yum provides /usr/bin/ab Then you will see that ab is in the httpd-tools package. And now you can install it: yum install httpd-tools
Whats with the syntax of something followed by parentheses? From http://jfearn.fedorapeople.org/en-US/RPM/0.1/html/RPM_Guide/ch-advanced-packaging.html: Scripting languages such as Perl and Tcl allow for add-on modules. Your package may require some of these add-on modules. RPM uses a special syntax with parenthesis to indicate script ...
Actually I found it, it's /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/. I found out what it was by doing update-alternatives --display java and it showed me the directory /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java
Have you tried this? $ yum list installed bind
The package is called postgresql-libs on Red Hat and derived distributions.
Some packages are held by more than one repository. The priorities plugin choose packages from the highest-priority repository, excluding duplicate entries from other repos.
From what I understand, this error is generated from the priorities plugin as noted by Pawel. In 2009, the maintainer of yum mentioned that he hoped people would not use priorities. To disable the priorities plugin, edit /etc/yum/pluginconf.d/priorities.conf and set enabled = 0. After this change, next time you run yum update, you should not get any ...
Yum supports plugins, so it's entirely possible to write a plugin that reads the cached puppet manifest and warns when a transaction will overwrite a puppet-controlled file. I'm not aware of an existing plugin that does this, but I will probably write just wrote one myself as I like the idea. The plugin checks all newly installed/upgraded/downgraded ...
Worked for me: yum remove php httpd php-cli php-xml php-common httpd-tools yum install php55 php55-mysql php55-pdo
Generally speaking speaking security updates are considered to be somewhat safe, particularly for a distribution with goals like RedHat. Their core focus is creating an operating environment that is consistent. As such the maintainers tend to pick versions of packages and stick with them for the long haul. To see what I mean look at the versions of such ...
I followed the instructions from Install Apache/PHP 5.4.10 on Fedora 17/16, CentOS/RHEL 6.3/5.8 with a slight modification. It took maybe 10min. My exact commands are shown below. Note that the first command had to be changed from what is shown in the article. The change was from epel-release-6-7.noarch.rpm to epel-release-6-8.noarch.rpm. How to add a repo ...
Install apr-util(need to run ab): yum install apr-util Install yum-utils: yum install yum-utils Download httpd an extract ab: mkdir ~/httpd cd ~/httpd yumdownloader httpd rpm2cpio httpd-2.2.3-43.el5.centos.3.i386.rpm | cpio -idmv mv usr/bin/ab /usr/bin/ab cd ~ rm -rf ~/httpd Run ab: ab http://google.ru/ This is ApacheBench, Version 2.0.40-dev ...
What version of yum? On the current version if the installed package is the same version as the most recent one available then the repo it was installed from is shown. $ yum info irssi Installed Packages Name : irssi Arch : i586 Version : 0.8.14 Release : 1.fc11 Size : 2.3 M Repo : installed From repo : updates Summary : ...
You could just build from the sources. The following worked for me (although you may not want to do the update or install every package in "Development tools" and "Additional Development"): sudo yum update sudo yum groupinstall "Development tools" sudo yum groupinstall "Additional Development" wget ...
The key thing to pick up is centos-release.x86_64, which is being upgraded to 6-7.el6.centos.12.3. You haven't said which subversion of CentOS you're on, but assuming you're up to patch, you're on 6.6 - this is the new 6.7 release hitting the mirrors. Those of us using the cr (continuous release) repository saw many of these packages arrive late last week. ...
Pick a mirror from the list of CentOS 6 mirrors and install the packages you need using rpm. You would need to deal with dependencies. Lucky for you, I have a pretty bare VM with CentOS 6 x86_64 installed. I snapshot the VM, ran yum remove python and had some fun getting through some circular dependencies. Final result: # --nodeps: because of circular ...
In order to run 2.2.x you would either need to source another RPM - or build it from source. I would suspect however since you are running 2.2.3 that you are running RedHat Enterprise Linux 5 or one of its derivatives (CentOS 5 etc). You will find that a sizeable number of penetration testing companies or security officers don't take into account that ...
There are at least two reasons for rebooting: You probably want to use the advantages of the newer version (security fixes) Usually during a kernel update the module tree of the old kernel is removed. Thus if you (or some script) unload a module then the system cannot load it again because it finds only the newer one on disk (if at all) and this is ...
Your general update strategy is sound: You have a local repo (which I assume you test in a dev environment), and you update everything based of that (I assume known good) repo. The service restart thing is inevitable: If the underlying code has changed you need to restart the service for that change to take effect. Failing to do so can lead to worse ...
yum update originally just did upgrades of packages to new versions. If, for example, foo-awesome obsoleted foo, yum update wouldn't offer to upgrade from foo to foo-awesome. Adding the --obsoletes flag to yum update made it do the extra checks to also offer that upgrade path. yum upgrade was added as (essentially) an alias for yum --obsoletes update. ...
You can find the version number of a package in your repositories with the yum info command. # yum info rabbitmq-server Available Packages Name : rabbitmq-server Arch : noarch Version : 2.6.1 Release : 1.fc16 Size : 1.1 M Repo : updates Committer : Peter Lemenkov <email@example.com> Committime : Tue Nov 8 ...
Coming way to late but (at least on Fedora 15) one can use yumdb for similar queries: yumdb info 'python*' And what I actually needed to list packages from given repo(s): yumdb search from_repo 'my-*-repo'
Only top voted, non community-wiki answers of a minimum length are eligible