Hi Jochen, generally updating the database shouldn't be an issue as this is handled by the migration scripts that incrementally update your db schema to match the version. But I would do a backup just in case.
For the outdated ini files you can use the tool called Meld to spot differences between yours and the .sample files. Björn pointed me to this tool after opening this <https://github.com/galaxyproject/galaxy/pull/3410> PR. Cheers, Jelle On Tue, Jan 17, 2017 at 11:34 AM, Jochen Bick <jochen.b...@usys.ethz.ch> wrote: > Hi, > > today we tried to update from 15.10 to 16.10 which included an update of > your database from 129 to 131. > Do we necessary run into problem if we update from an one year old > instance? How is the galaxy.ini updated? Or galaxy.ini does not know any > conda yet. > > > Thanks in advance. > Cheers Jochen > ___________________________________________________________ > Please keep all replies on the list by using "reply all" > in your mail client. To manage your subscriptions to this > and other Galaxy lists, please use the interface at: > https://lists.galaxyproject.org/ > > To search Galaxy mailing lists use the unified search at: > http://galaxyproject.org/search/mailinglists/
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
