Fri Sep 11 08:32:13 PDT 2009
- Previous message: [Slony1-hackers] slonyVersion() and getModuleVersion() mismatch in current CVS
- Next message: [Slony1-hackers] slonyVersion() and getModuleVersion() mismatch in current CVS
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bernd Helmle <mailings at oopsware.de> writes: > Folks, > > seems current CVS is inconsistent between module version and schema > version strings. Build from a fresh CVS checkout gives the following: > > > SELECT _movies.slonyVersion(); > slonyversion > -------------- > 2.0.3 > (1 row) > > SELECT _movies.getModuleVersion(); > getmoduleversion > ------------------ > 2.0.2 > (1 row) > > Accordingly, slon complains in db_checkSchemaVersion(): > > ERROR Slony-I schema version is 2.0.3 > ERROR please upgrade Slony-I schema to version 2.0.2 > FATAL main: Node has wrong Slony-I schema or module version loaded > > Seems we have to bump up SLONY_I_VERSION_STRING, too (patch level in > the schema > is already set to 3) ? I expect that you failed to run "autoconf"; the value in BUILDHOME/config.h.in is indeed 2.0.3; that gets stowed in config.h by autoconf. -- output = reverse("ofni.sailifa.ac" "@" "enworbbc") Christopher Browne "Bother," said Pooh, "Eeyore, ready two photon torpedoes and lock phasers on the Heffalump, Piglet, meet me in transporter room three"
- Previous message: [Slony1-hackers] slonyVersion() and getModuleVersion() mismatch in current CVS
- Next message: [Slony1-hackers] slonyVersion() and getModuleVersion() mismatch in current CVS
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-hackers mailing list