search for: versionlocking

with installed version 1.3.7 from rpmforge yum --allow-downgrade update rrdtool-1.2.30-1.el5.rf results in "no packages to update" yum --allow-downgrade install rrdtool-1.2.30-1.el5.rf says "already installed" So, how am I supposed to use --allow-downgrade then? I had to rpm -e --nodeps the newer packages to be able to install the older packages. Now I want to lock the

When I query for installed package on the system, I get following result: # yum list installed openssl Loaded plugins: fastestmirror, tsflags, verify, versionlock Loading mirror speeds from cached hostfile Installed Packages openssl.x86_64 1.0.1e-16.el6_5.4 @updates/$releasever When I try to install already installed package (just playing with yum), I get following result: # yum install

I have experienced this myself. It is very upsetting. (Sent from iPhone, so please accept my apologies in advance for any spelling or grammatical errors.) > On Jan 19, 2017, at 2:57 AM, Fabian Arrotin <arrfab at centos.org> wrote: > > log

Hi All, I have finally switched to using hiera (worthy goal!) and I am looking for a flexible way to manage the ''exclude'' line in /etc/yum.conf. I want to be able to specify from different classes RPMs to be excluded in /etc/yum.conf, then build the exclude line from all those classes that set an exclude. In my hiera hierarchy, I use %{calling_module}, but I actually modify

Well, there's a bug in the globbing for the tcsh with 5.4, and my boss has filed a bug report. Meanwhile, I downgraded tcsh on those systems whose users use that as their shell. Until it's resolved, he wants me to pin the version. Googling, I see someone a few years ago, answering someone's question, suggested adding exclude=openoffice* near the top of /etc/yum.conf. I also see, more

On 7/27/2016 9:58 PM, geo.inbox.ignored wrote: > $ sudo yum install NetworkManager-wifi > [sudo] password for geo: > Loaded plugins: aliases, changelog, fastestmirror, ovl, presto, refresh- > : packagekit, security, tmprepo, verify, versionlock > Setting up Install Process > Loading mirror speeds from cached hostfile > * base: mirror.steadfast.net > *

Everyone, I am at a loss on this problem would appreciate some guidance as to where to start to fix it. I noticed that my home gateway server was not being updated with the new kernel and other software, and when I ran yum it aborted with the following notices. I tried a yum clean all, but this did not fix the problem. I thought the problem may be related to one of the repos, but I have other

Just upgraded to 5.4 yesterday morning. (Kudos to those who did that!) That's probably irrelevant to this problem: "yum install mplayer" fails. Here's what happens: ================================================== # yum install mplayer Loaded plugins: fastestmirror, filter-data, kernel-module, keys, kmod, list- : data, merge-conf, security, upgrade-helper,

greetings, wicd is preventing firefox and yumex to connect to internet. when i first try to connect to a web site with firefox, i get err message; Unable to connect when i click [Try Again], connection is made. all further connection attempts are ok. when i try to run yumex, i get error message; Not connected to a network. Do you want to continue selecting [Yes] continues starting

W dniu 19.01.2017 o 10:17, Hal Wigoda pisze: > I have experienced this myself. It is very upsetting. It happened on servers with docker installed. I got error message there: # semanage port -a -t ssh_port_t -p tcp <newport> Re-declaration of type docker_t Failed to create node Bad type declaration at /etc/selinux/targeted/tmp/modules/100/docker/cil:1 OSError: Error After

Hi there -- I need to reconfigure yum on one of our centos 5.3 systems in order for the automatic updates to work. Currently the error messages that I am getting are shown below: $ sudo yum check-update Loaded plugins: allowdowngrade, changelog, downloadonly, fastestmirror, priorities, protectbase, tsflags, versionlock Loading mirror speeds from cached hostfile * base: mirrors.rit.edu *

I thought that Fedora 18 and Fedora 19 included packages for R. But now I find that yum reports nothing available: # yum install R-devel R Loaded plugins: auto-update-debuginfo, langpacks, refresh-packagekit, versionlock No package R-devel available. No package R available. So I went to check manually in the download directory, e.g.

On 01/19/2017 04:47 AM, Marcin Trendota wrote: > W dniu 19.01.2017 o 10:17, Hal Wigoda pisze: >> I have experienced this myself. It is very upsetting. > > > It happened on servers with docker installed. I got error message there: > # semanage port -a -t ssh_port_t -p tcp <newport> > Re-declaration of type docker_t > Failed to create node > Bad type

On 7/27/2016 8:51 PM, geo.inbox.ignored wrote: > have you tried the 7 32 bit? no, all my linux servers now are 64 bit, I havent' run a 32 bit system in a long time. if your internet is working over ethernet, you should be able to install what you need via yum, rather than reinstall from different media... yum install NetworkManager-wifi and you should be able to configure wifi

hi all, i'm trying to understand an issue i'm having with a yum repo (it's a mirror of the c74 repo). there's an rpm in the repo (ibutils-libs in this case); but the client using this repo says it cannot find this rpm (i did yum info ibutils-libs --disablerepo=* --enablerepo=c74 to exclude all other repos). other rpms are ok to use, so nothing structural going wrong (i think)

On 06/29/2017 01:08 PM, Paolo Margara wrote: > > Hi all, > > for the upgrade I followed this procedure: > > * put node in maintenance mode (ensure no client are active) > * yum versionlock delete glusterfs* > * service glusterd stop > * yum update > * systemctl daemon-reload > * service glusterd start > * yum versionlock add glusterfs* > *

> On Dec 10, 2014, at 1:42 AM, Steffen Kaiser <skdovecot at smail.inf.fh-brs.de> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 9 Dec 2014, Stephen Lidie wrote: >>> On Dec 9, 2014, at 11:00 AM, Steffen Kaiser <skdovecot at smail.inf.fh-brs.de> wrote: >>> On Tue, 9 Dec 2014, Stephen Lidie wrote: >>>>> On Dec 9,

Hi all, for the upgrade I followed this procedure: * put node in maintenance mode (ensure no client are active) * yum versionlock delete glusterfs* * service glusterd stop * yum update * systemctl daemon-reload * service glusterd start * yum versionlock add glusterfs* * gluster volume heal vm-images-repo full * gluster volume heal vm-images-repo info on each server every time

CentOS Errata and Bugfix Advisory 2014:0138 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0138.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 074cded096000092dfd80b9b85c440b53d591c21e70de7eee824ea23a526c0f9 yum-NetworkManager-dispatcher-1.1.30-17.el6_5.noarch.rpm

CentOS Errata and Security Advisory 2018:2284 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:2284 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7bfcb55e8ee020fb90438be89a7e6c4659815a47a6a1dc84307ed097c610b164 yum-NetworkManager-dispatcher-1.1.30-42.el6_10.noarch.rpm