search for: downgrades

On 25/01/17 14:26, Jonathan Billings wrote: > On Wed, Jan 25, 2017 at 11:32:16AM +0000, lejeczek wrote: >> hi guys, gals >> >> do you see this: >> >> ~]$ yum downgrade samba >> Resolving Dependencies >> [...] >> --> Processing Dependency: libtevent.so.0(TEVENT_0.9.9) for package: >> samba-client-libs-4.4.4 >> >> ..and process

We're using ansible to configure our CentOS 6 servers, and we have a task to install a specific version of a package: - name: install thrift2 yum: name=ripencc-thrift2-{{ version }} In this ansible task, the "version" variable is set by the operator. When we want to upgrade, it works. But today we had to downgrade, and noticed that ansible wasn't downgrading it. So we tried

hi guys, gals do you see this: ~]$ yum downgrade samba Resolving Dependencies --> Running transaction check ---> Package samba.x86_64 0:4.4.4-9.el7 will be a downgrade --> Processing Dependency: samba-libs = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common-tools = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing

...et''s say that there is a web application which comes in several different plans. Each plan has a different number of users and content items allowed for an account. Obviously we can allow the user to upgrade to a higher level plan by just increasing their limits but how do we handle downgrades? If the user is only allowed x items on the downgraded plan and they currently have x+10 items what do we do? The way I see it there are a few options. 1. Don''t let a user downgrade their plan until they have deleted enough users and items to meet the requirements for the plan they ar...

After the large update from 7.2 -> 7.3 there is one major problem, the amanda backup packages. Strange situation, the host is the amanda server is working fine at backing up all my remote clients. But it has an error backing up itself. The amanda packages did not change version (3.3.3) and I've done no configuration change. I'm not looking for help debugging this at the moment.

There was an upgrade on a couple of our servers yesterday, mid-afternoon our time, of httpd and httpd-devel, and suddenly SiteMinder (bleah) stopped working correctly, and is now pegging a cpu, according to top. So, as a last resort, I tried downgrading both of them. When I did so, the server that uses ssl *erased* mod-ssl, not downgrading it, and I'll have to find where I can get the previous

Hi all, I am trying to use puppet (2.7.18) for downgrading varnish cache on Centos Linux (6.3). Unfortunately there are two varnish RPMs (which seem to have circular dependencies): varnish-3.0.4-1.el6.x86_64 varnish-libs-3.0.4-1.el6.x86_64 When using "ensure" for downgrading I get a bunch of errors: err: /Stage[main]/Varnish/Package[varnish-libs]/ensure: change from 3.0.4-1.el6

I upgraded to the latest HEAD version of asterisk, and all IAX calls started sounding choppy. It was suggested on the IRC channel that I go back to asterisk -stable to determine if that fixes it. Is downgrading as simple as upgrading? Because now, -stable builds fine, but I get an error on the asterisk console when starting, something about "ast_get_txt" not found. Recompiling and

I tried, last night, to downgrade kdelibs, I think it is, to resolve the libplasma crash that we talked about yesterday... and yum told me there was no upgrade or downgrade. I'm sort of assuming that I'd have to go back to 6.4... unless I need to add a repo - the vault? wget it, and downgrade it locally? mark

Hello all, I have been tasked with "fixing" one of our CentOS boxes by somehow downgrading the libgcc and gcc packages to a specific version (Required by the Oracle Grid Control client). Normally I'd just remove and reinstall the packages however removing libgcc is no fun as I found out the hard way it breaks pretty much every package including rpm & yum. Is there an elegant way

Hi, My apologies for the OT. My googling came up empty and hopefully there are some members in the community that could give me a hint how to solve this issue: Cisco 7961 with SIP firmware 8.3.3. Needed to downgrade it to 8.0.4SRS2. The downgrade process started off good. The 7961 got it's IP address via DHCP, found it's SEP<mac>.cnf.xml file and started to "upgrade"

On Thu, Jan 26, 2017 at 11:44:06AM +0000, lejeczek wrote: > but Centos should, right? > Being able to downgrade can save you a day or a few. I know, for it did save > mine several times, eg. buggy samba new update and downgrade fixed it, etc. > We absolutely should be able to downgrade every rpm, if this is just a > matter of an opinion(I'd fail to see any other reasons to not

Use the 'downgrade' option. https://access.redhat.com/solutions/29617 On Thu, Jun 1, 2017 at 1:46 PM, Anand Buddhdev <anandb at ripe.net> wrote: > We're using ansible to configure our CentOS 6 servers, and we have a > task to install a specific version of a package: > > - name: install thrift2 > yum: name=ripencc-thrift2-{{ version }} > > In this ansible

This is a yum question but relates to some work I am doing with CentOS and other recent discussions on this list so I though I would post here first. Basically I am attempting a Red Hat 7.2 -> CentOS-2 upgrade. So far it has worked like a charm. The problem is though that yum (no doubt by design) will not downgrade packages to the CentOS versions. The problem is that some old RPMs have

...install has left an ldb plugin (encrypted_secrets.so) around which blocks operation as it can't operate with the older Samba version but isn't overwritten as it didn't exist in the older version. However I also need to write up about the GUID index change, which also prevents in-place downgrades. It seems I forgot to mention that in the WHATSNEW. (That requires running source4/scripting/bin/sambaundoguididx before any downgrade in-place from 4.8 to 4.7 and below). Thanks, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Sa...

After considerable experimentation I'm forced to accept that Samba 3 has problems with the combination of being a domain member, the 2.6 kernel, and Dell 2850 hardware. It works fine on the 2.4 kernels but fails on all the 2.6 versions I have avaialble for testing. I have one machine that I really prefer could stay at 2.6 so my last resort there is to try a downgrade to samba 2.X In the

On Thu, 2015-12-31 at 10:16 -0700, Brandon Vincent wrote: > Looks like upstream is working on it [1]. According to the BZ, the > solution for now is to downgrade nfs-utils [2]. Thank you for spotting that one! Don't know it's because I'm still tired from yesterday, but don't seem to be able to downgrade. The command 'yum downgrade nfs-utils' just returns nothing to

On 02/02/17 06:32, Jon LaBadie wrote: > After the large update from 7.2 -> 7.3 there is > one major problem, the amanda backup packages. > > Strange situation, the host is the amanda server > is working fine at backing up all my remote clients. > But it has an error backing up itself. > > The amanda packages did not change version (3.3.3) > and I've done no

Personally, I would do one of three things: 1. Use the -m command to run 'yum install <version>' which /might/ work. 2. Uninstall the newer package and install the version you want. (Check the 'state' directive to do this.) 3. Pin that package version when creating the server/VM so as not to be updated. #3 is useful to us as we kickstart all our servers and VMs, and

I've run into some trouble with a new cPanel VPS, and noticed that it's running CentOS by default, installed via the CentOS http server. My question is, how do I downgrade CentOS to 5.1? -- Kind Regards Rudi Ahlers CEO, SoftDux Web: http://www.SoftDux.com Check out my technical blog, http://blog.softdux.com for Linux or other technical stuff, or visit