FYI yum upgrade fails with samba4 duplicate with PIAF Green

[Talkingscientist]

I thought I broke it. Finally I gave up, terminated my EC2 instance, deleted the volume and re did everything from the AMI. First command I tried was
yum upgrade
it ends with

--> Running transaction check
---> Package libtdb-devel.x86_64 0:1.2.10-1.el6 will be installed
--> Processing Conflict: samba4-common-4.0.0-55.el6.rc4.x86_64 conflicts samba-common < 3.9.9
--> Processing Conflict: samba4-4.0.0-55.el6.rc4.x86_64 conflicts samba < 3.9.9
--> Finished Dependency Resolution
Error: samba4-common conflicts with samba-common
Error: samba4 conflicts with samba
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

 

[Talkingscientist]

I swear I searched for yum upgrade in the forums and nothing came up, after posting this it showed similar so I'm reading those now. Don't hate me

 

[wardmundy]

Don't use yum upgrade with our systems. It breaks stuff... as you have found out.

 

[darmock]

You discovered on of the "rules" that Piaf types should live by which is DO NOT USE YUM EVER. There is no need to use yum unless a VERIFIABLE and REPRODUCIBLE security exploit has been discovered and you have been advised in this forum to use yum XXXXX

While we do have yum update in update-source it also takes into account some instances where using yum XXXXX breaks some aspects of asterisk/dahdi. All of the boxes I maintain never get a yum anything on them unless there is a problem as outlined above.

One of the reasons that people like to run yum every few seconds (note this is an exaggeration) is their experience with windows which does require frequent updates in order to run. Linux is not like that and unless there is something in an update that you JUST CAN'T LIVE WITHOUT leave it alone. After all you are using this as a dedicated pbx right?



Tom