Am Dienstag, 30. Mai 2017, 14:20:25 CEST schrieb Dominique Chabord: > 2017-05-30 14:06 GMT+02:00 Sergi Almacellas Abellana <[email protected]>: > > El 30/05/17 a les 12:21, Dominique Chabord ha escrit: > >> my questions are : > >> - what is the roll-back procedure in case some problems appear at any > >> step > >> ? > > > > If you are using a new virtualenv just have a backup of your database and > > you have it. If everything does not go well, restore the backup and use > > the > > previous version code. > > This was a question to Axel about rpm, at OS level iiuc. Do you know > how to revert a rpm upgrade ?
Just a reversal of a RPM should not be an issue: % zypper se -s pkg will give you the list of versions that zypper knows about (has a cached version of / can see in your repos). You can then forcefully install (downgrade) pkg to pkg-1.2.3 with: % zypper in --oldpackage pkg-1.2.3 You should get a warning about a downgrade. I'm not actually sure if this will downgrade libraries (if necessary) but I would hope it does (since zypper would see it as a reinstall with different Requires). Question is what other adaptions are being made (e.g. changes to the database). So the real safe way is to use a previous snapshot to go back to start.... > > 1. Deploy the new version code: > > 2. Upgrade the database structure while not stopping the previous server. > > (Here is when bad things can happen) > > 3. Stop the old server and start the new one. > > if you use rpm strategy, I think you cannot run two versions on the > same machine. This was the question. > > > I share Axel idea and it would be nice to update Tryton as we update > postgresql, but I think we cannot (yet ?) You mean from packages? Not sure what should stop us..... although some manual activities can not be avoided I think. Cheers Axel -- You received this message because you are subscribed to the Google Groups "tryton" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton/2243087.z8SFzMFpUr%40t520.axxite.internal.
