Hi,

For the information, I had some problems with rpm -Uvh otrs ( on latest 2.2.1 to 2.2.2 upgrade ) while upgrading with modified files of the 2.2.1 rpm presents ( we customise some files to our needs) and these files were not upgraded to the 2.2.2 version, even not a .rpmnew or .rpmsave was create.

So that's "good" in a certain point of view to prevent our modified files not being overwritten by new package files but that's not a good thing because it prevents us having the latest version of files from 2.2.2 in any way.

rpm -ivh was better in this case, like others cases in which I had the same type of thing with specific rpms ... maybe some packages built problems ? ( not properly managing upgrade with .rpmnew/.rpmsave file creation ? )

Laurent

Le samedi 11 août 2007 à 00:16 +0200, Nils Breunese (Lemonbit) a écrit : 
Laurent Minost wrote:

> Same as Nils, everything went OK when I upgraded from 2.2.1 to  
> 2.2.2 with the two SQL statements addon provided on the download  
> page ( done on Fedora 7 and RedHat EL4).
>
> But as a difference, I prefer using a new OTRS install by backuping  
> old dirs/SQL dump then rpm -e old otrs package and then rpm -ivh  
> new package, then i set back all my config changes needed and all  
> my customizations on source code by a home-made shell script using  
> diff and patch against old and new version ...
> I got some strange things for others packages when rpm -Uvh  
> sometimes ...

rpm -U has always worked fine for us.

Nils Breunese.
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support or consulting for your OTRS system?
=> http://www.otrs.com/