[OSM-dev] Osmosis broken
brett at bretth.com
Sun Mar 2 08:36:44 GMT 2008
Just happened to check my email, I won't be back for another week or so. To
fix the problem, do the following steps (I can't access anything from
internet cafes myself).
Login as bretth on dev
Change to the ~/app/osmosis directory
Modify src/com/bretth/osmosis/core/mysql/v0_5/MySqlVersionConstants.java and
change the version constant (do NOT run svn update!!!)
Run "ant clean all" to rebuild osmosis
Run "chmod u+x ./bin/osmosis*" to make the launch scripts executable
The cron jobs should pick up where they left off although this might take a
while. It might be necessary to delete all existing output files and modify
the timestamp files contained under the ~/app/dailydiff ~/app/hourlydiff and
Alternatively, just wait another week or so :-)
On 2/25/08, Karl Newman <siliconfiend at gmail.com> wrote:
> On Sun, Feb 24, 2008 at 9:44 AM, Tom Hughes <tom at compton.nu> wrote:
> > In message <52ae42fa0802240831i1b2ac661jcc3598bd0f30e093 at mail.gmail.com>
> > "Karl Newman" <siliconfiend at gmail.com> wrote:
> > > On Sun, Feb 24, 2008 at 5:18 AM, Tom Hughes <tom at compton.nu> wrote:
> > >
> > > > That'll be when I updated the database to schema version 11 for
> > Steve's
> > > > changes. Unfortunately that breaks Osmosis... I think Brett's away
> > at the
> > > > moment, so this might not be very easy to fix.
> > >
> > > Actually, I think it's not too bad to fix. I don't think Osmosis cares
> > about
> > > user preferences (assuming that was the major change), so all you have
> > to do
> > > is bump the expected schema version to 11. It's in
> > >
> > Osmosis/src/com/bretth/osmosis/core/mysql/v0_5/MySqlVersionConstants.java Of
> > > course, then you'd have to recompile and deploy the new version.
> > The problem is not changing the code, it's that I have no idea how
> > to go about building it or deploying the fixed version on dev.
> I thought the trouble was in finding the right place in the code to
> modify. I'm set up to compile a new Osmosis.jar, so I could provide it to
> you, but I don't know anything about the setup on dev.
> > > Alternately, you could temporarily modify the command line to add the
> > option
> > > validateSchemaVersion=no to the database read task. It might be nice
> > to be
> > > able to override the expected schema version with a command line
> > argument,
> > > but that's not in there right now.
> > That sounds a bit easier...
> > Tom
> I think that's your best bet for now until BrettH gets back from his
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dev