Thirdlane.com logo

Yum conflict with thirdlane-ast14-pbxm-conf-mt-1.0-1.noarch

Posted by jesperkjeldsen on Mon, 07/05/2010
Forums
Thirdlane platform General Questions

Hi
I tried to update my Thirdlane box with Webmin/Yum, but ends up in a conflict with thirdlane-ast14-pbxm-conf-mt-1.0-1.noarch.
A lot error like this (with different .conf files):
file /etc/asterisk/voicemail.conf from install of asterisk14-config-1.4.30-1.i386 conflicts with file from package thirdlane-ast14-pbxm-conf-mt-1.0-1.noarch

I tried, on my demo-box, removing the thirdlane-ast14-pbxm-conf-mt-1.0-1.noarch package and the it seems to work. But as I don't really know what that file is there for I don't want to do it on my productionbox without hearing what you other says+

Regards
Jesper

Submitted by jesperkjeldsen on Mon, 07/26/2010 Permalink

Hi, I am a bit surprised that no one has comments to this. Either all of you uses an old Asterisk and live with that or you have compiled from the ground (not used the ISO) ;-)

I will wait for the new ISO to be ready and upgrade that way.

Regards
Jesper

Submitted by eeman on Tue, 07/27/2010 Permalink

I dont use RPM for asterisk. I've explained a number of times that its a horrible situation to be put into. There is no path backwards in that repository. If you choose to update.. and find yourself going from asterisk 1.4.26 to 1.4.31 .. and lets say they broke attended transfers in that version... you're screwed. You can't revert because the old rpm's aren't in that repo. You're now stuck, with a broken system, waiting for a fix. If your really really lucky it gets fixed quickly in the next version at which time you still have to wait for the RPM to be created and put into the repo. Nobody is that lucky every time. Some fixes take several versions to get fixed. I don't know anyone who can afford to run in a broken state for months. You will either have to revert to a working version or lose a large customer base. The only way to revert is to remove RPMs and compile manually. Once you go down this path there are no longer any RPM updates that will happen when you type yum update for your asterisk/dahdi packages. This is why I dont bother in the first place. Eventually you're going to be in a circumstance of having to compile. With the older ISOs the required libraries to compile the modules included in the RPMs were not even installed which made for a complete mess when trying to compile manually. This is rumored to be fixed in the upcoming version.