Questions on upgrading from Koha 3.0.1 to 3.0.2/3
Hi everyone, Right now we're running 3.00.01 but we'd like to upgrade to 3.00.03. My first question is, I hope, relatively simple: Can we upgrade directly to 3.00.03 from 3.00.01, or would it be better/more prudent to pass for 3.00.02 first? The second question is, given that we've modified some files (for example, in /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/cataloguing/value_builder, we've modified the plugins for the leader and 008 so that it's possible to use, e.g. |-No attempt to code per Festchrift), what's the best way to handle the upgrade? Is it possible to make changes to files from the upgrade tarball before the make upgrade or is it necessary to go ahead with the upgrade and then follow-up afterwards readding the changes we've made? Thanks in advance for any and all help, it's much appreciated. Patrick Redmon Librarian Casa Balthasar
Bibliotecario Casa Balthasar asked
My first question is, I hope, relatively simple: Can we upgrade directly to 3.00.03 from 3.00.01, or would it be better/more prudent to pass for 3.00.02 first?
I think you should be fine going to 3.00.03, but back up everything and if it fails, installing 3.00.02 might help to identify the problem by narrowing the search.
The second question is, given that we've modified some files (for example, in /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/cataloguing/value_builder, we've modified the plugins for the leader and 008 so that it's possible to use, e.g. |-No attempt to code per Festchrift), what's the best way to handle the upgrade? Is it possible to make changes to files from the upgrade tarball before the make upgrade or is it necessary to go ahead with the upgrade and then follow-up afterwards readding the changes we've made?
If you've not used git revision control, I think the best way is to unpack the original 3.00.01 source, take a copy of your modified 3.00.01 source, do the upgrade and then use a "three-way merge with ancestor" tool on the directories containing the modifications. Emacs has one called Ediff http://www.gnu.org/software/emacs/manual/html_node/ediff/index.html#Top but I expect other pretty ones are available. Again, backup everything. Hope that helps, -- MJ Ray (slef) LMS developer and webmaster at | software www.software.coop http://mjr.towers.org.uk | .... co IMO only: see http://mjr.towers.org.uk/email.html | .... op
Dear MJ, Thanks you very much for the advice. As you guessed correctly, we haven't used git revision control. Now that I understand what's at stake in using it (having gone to check out the details on the koha wiki), is there any way to 're-insert' what we've got so far, other than to simply clone the latest version and do the same sort of 'three-way merge with ancestor' that you'd mentioned? Again, thanks for your help. Best, Patrick Redmon Librarian Casa Balthasar 2009/9/22 MJ Ray <mjr@phonecoop.coop>
Bibliotecario Casa Balthasar asked
My first question is, I hope, relatively simple: Can we upgrade directly to 3.00.03 from 3.00.01, or would it be better/more prudent to pass for 3.00.02 first?
I think you should be fine going to 3.00.03, but back up everything and if it fails, installing 3.00.02 might help to identify the problem by narrowing the search.
The second question is, given that we've modified some files (for example, in
/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/cataloguing/value_builder,
we've modified the plugins for the leader and 008 so that it's possible to use, e.g. |-No attempt to code per Festchrift), what's the best way to handle the upgrade? Is it possible to make changes to files from the upgrade tarball before the make upgrade or is it necessary to go ahead with the upgrade and then follow-up afterwards readding the changes we've made?
If you've not used git revision control, I think the best way is to unpack the original 3.00.01 source, take a copy of your modified 3.00.01 source, do the upgrade and then use a "three-way merge with ancestor" tool on the directories containing the modifications. Emacs has one called Ediff http://www.gnu.org/software/emacs/manual/html_node/ediff/index.html#Top but I expect other pretty ones are available. Again, backup everything.
Hope that helps, -- MJ Ray (slef) LMS developer and webmaster at | software www.software.coop http://mjr.towers.org.uk | .... co IMO only: see http://mjr.towers.org.uk/email.html | .... op
Dear MJ,
Thanks you very much for the advice. As you guessed correctly, we haven't used git revision control. Now that I understand what's at stake in using it (having gone to check out the details on the koha wiki), is there any way to 're-insert' what we've got so far, other than to simply clone the latest version and do the same sort of 'three-way merge with ancestor' that you'd mentioned?
Again, thanks for your help.
Best,
Patrick Redmon Librarian Casa Balthasar Have you used any version control system to manage your code ? There are Subversion and CVS bridges to git. So that you could then catch up the official branches as just an other
Bibliotecario Casa Balthasar a écrit : source. And eventually port your stuff onto official branch. If you used version control system then.... Your unique solution is what MJ said. Friendly -- Henri-Damien LAURENT
participants (3)
-
Bibliotecario Casa Balthasar -
LAURENT Henri-Damien -
MJ Ray