I'd vote for releasing as 1.6.5 (or 1.6.4.1), and removing 1.6.4 from our
downloads. But I could go either way.

-Darius

On Tue, Jan 24, 2012 at 3:47 PM, Ben Wolfe <[email protected]> wrote:

> I didn't realize this when I released 1.6.4, sorry.  :-/  Looks like
> Darius put this documentation into the custom omod's config:
>
> <!-- This module also works with the 1.6.x branch starting from
> 1.6.3.17711, but we can't release a
>          version like that to the repository, because it would
> auto-upgrade 1.7.0 and 1.7.1, and that
>          would break things. The following line can be commented out to
> build that special version -->
>     <require_version>1.6.3.17711</require_version>
>     <!-- <require_version>1.7.2.17710-1.8.*</require_version> -->
>
> I want to clean up the released 1.6.4 with this, any opposition to that?
> Or should I leave it as-is and just release 1.6.5 with the right omod?
>
> Ben
>
>
> On Mon, Jan 23, 2012 at 6:28 PM, Mark Goodrich <[email protected]> wrote:
>
>> Hello all—****
>>
>> ** **
>>
>> I just upgraded from 1.6.3 to 1.6.4 and to spend some time working out
>> some issues with the logic-0.5 and openmrs 1.6.4… I know there have been
>> some previous issues with the move from logic-0.4 and logic-0.5 and wanted
>> to share what I had learned and see if anyone else had experienced what I
>> had experienced…****
>>
>> ** **
>>
>> I think I narrowed the issues I ran into down to two problems:****
>>
>> ** **
>>
>> **-          **The version of the logic module included with the 1.6.4
>> release may be the incorrect version of the module (1.6.4 requires a custom
>> build of logic)****
>>
>> **-          **For some reason, the logic.database_version global
>> property needs to be modified to avoid errors when the sqldiff tries to
>> create tables that already exist****
>>
>> ** **
>>
>> What I ended up doing was stopping tomcat, deleting my openmrs directory
>> as well as my tomcat temp and working directories, and then dropping in the
>> 1.6.4 war file and restarting tomcat.  But then, before logging in to
>> OpenMRS and performing the migration, I replaced the logic-0.5 omod in
>> tomcat/webapps/openmrs/WEB-INF/bundledModules with the custom 1.6.4 version
>> of logic that can be found here (under Requirements):****
>>
>> ** **
>>
>> https://wiki.openmrs.org/display/docs/Logic+Module****
>>
>> ** **
>>
>> After that, I had to manually change the logic.database_version global
>> property from 1.0.0 to 1.4.  Then the module started successfully.****
>>
>> ** **
>>
>> Has anyone else run into anything similar?****
>>
>> ** **
>>
>> Thanks,****
>>
>> Mark****
>>
>> ** **
>>
>> ** **
>>
>> ** **
>> ------------------------------
>> Click here to 
>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-implement-l>from
>>  OpenMRS Implementers' mailing list
>
>
> ------------------------------
> Click here to 
> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-implement-l>from
>  OpenMRS Implementers' mailing list
>

_________________________________________

To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to 
[email protected] with "SIGNOFF openmrs-implement-l" in the  body 
(not the subject) of your e-mail.

[mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]

Reply via email to