[OpenSIPS-Users] Upgrade version problems in a production system (mediaproxy)

[Adrian Georgescu]

Carlo,

We use only Debian development branch both for the development of our  
software and for our deployments. If you use Debian unstable you are  
the safest as we are testing and using our packages only this  
environment.

While the name 'stable' brings some confidence for the inexperienced,  
in practice when it comes to bleeding edge developments like we do,  
the stable version can become obsolete fast and you could be stuck by  
running it because of the dependencies that do not make it to the  
stable branch as soon as we develop our software. When things do not  
work you will hear the same story "your distribution is too old" to  
run this software.

So the most stable distribution is unstable.

Adrian


On Jul 24, 2009, at 3:45 PM, Carlo Dimaggio wrote:

> Hi all,
>
> I'm wondering about the right distribution and version for a
> production environment: i ask you this because of some problems in
> upgrading my systems.
> I'm using two Ubuntu 8.04 Server LTS with opensips 1.5.2, callcontrol
> 2.0.4, mediaproxy 2.3.4, cdrtool 6.8.1. I didn't have any error in
> upgrading opensips and the other softwares until now, but today I have
> tried to upgrade mediaproxy to 2.3.5 and I'm experienced with the old
> version of different packages (python-application, python-support,
> python-gnutls, libgnutls,...) and I am unable to install this new
> versions (for dependencies).
>
> My question is: how can mantain an updated production server? I have
> seen that an updated python-application is always needed for new
> versions of mediaproxy...
> How do you handle this process (without using an unstable/testing
> distribution)?
>
>
> Thank you and regards,
> Carlo Dimaggio
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users