Error: Trying to remove "sangoma-pbx", which is protected


#1

PBX Version: 15.0.16.77
PBX Distro: 12.7.8-2008-1.sng7
Asterisk Version: 16.13.0

Running: yum update -y and getting error
Error: Trying to remove “sangoma-pbx”, which is protected

I can see posts before about this but the solutions seem to be rather specific, so would rather not do anything without advice.

> --> Finished Dependency Resolution
> --> Running transaction check
> ---> Package kernel.x86_64 0:3.10.0-514.26.2.el7 will be erased
> --> Processing Dependency: kernel(napi_complete_done) = 0x905307be for package: kmod-via-rhine-1.5.2-1.sng7.x86_64
> --> Processing Dependency: kernel(napi_complete_done) = 0x905307be for package: kmod-forcedeth-0.65-1.sng7.x86_64
> --> Processing Dependency: kernel(napi_complete_done) = 0x905307be for package: kmod-via-velocity-1.16-1.sng7.x86_64
> --> Processing Dependency: kernel(skb_clone_tx_timestamp) = 0x83433c92 for package: kmod-forcedeth-0.65-1.sng7.x86_64
> --> Running transaction check
> ---> Package kmod-forcedeth.x86_64 0:0.65-1.sng7 will be erased
> --> Processing Dependency: kmod-forcedeth for package: sangoma-pbx-2008-1.sng7.noarch
> ---> Package kmod-via-rhine.x86_64 0:1.5.2-1.sng7 will be erased
> ---> Package kmod-via-velocity.x86_64 0:1.16-1.sng7 will be erased
> --> Running transaction check
> ---> Package sangoma-pbx.noarch 0:2008-1.sng7 will be erased
> --> Finished Dependency Resolution
> Error: Trying to remove "sangoma-pbx", which is protected

(Dave Burgess) #2

Memory like pudding, but it seems to me that this is the culprit. I don’t remember if you have to remove this or update it, but there’s a step where this ends up being the wrong version and it screws you up.


(Jared Busch) #3

Downgrade it actually.

yum downgrade kmod-forcedeth

#4

Thanks.

There are several similar lines there. Do all need to be down graded?

I have found other instances of this error and the advice did not contain any general (logical) advice that I feel comfortable applying.

In one of them they advised downgrading the same thing twice!


(Jared Busch) #5

I believe they are dependencies, so they will automatically downgrade also.

The command will show you everything it will downgrade, and let you say yes or no to continue.


#6

Downgraded as suggested but the other two still came up. So I bit the bullet and done those also.

The upgrade then worked!

Many thanks! Much appreciated.