Task #905
Updated by Aaron Marcuse-Kubitza about 10 years ago
_see #887, #902_ try each of the following, in order: h3(. alternate OS approach # fix @`make install`@, which sets up the entire BIEN installation and dependencies # test the import on the local testing machine (a Mac), which already has most of the dependencies # if that doesn't work, try the clean VM approach below h3(. clean VM approach # -prepare clean VMs- # fix @`make install`@, which sets up the entire BIEN installation and dependencies _the remaining bugs are now in the from-scratch setup of the database itself, and relate to the order in which interrelated components are installed: a schema must be installed after schemas it depends on, a view must be installed after table columns it uses have been auto-renamed, etc._ ** normally, we do not reinstall the DB from scratch, so the bugs in @`make install`@ only become apparent when it is run on a partial installation # install the database from scratch on a clean VM (VirtualBox) ** this would involve adding any missing dependencies to our install scripts # test the import in the clean VM with a sample datasource to see if that reproduces the problem ** if it does, we know it's a bug in Postgres/Ubuntu and can troubleshoot using VM images with different Postgres/Ubuntu versions ** if it doesn't, it's a problem specific to just the vegbiendev VM and we would reset the vegbiendev VM to a clean Ubuntu install and reinstall our dependencies h3(. Postgres rollback approach # roll back Postgres to the version it was at in the last successful import ** this may require building Postgres from source, because past _revisions_ of the same numeric version might only be available in version control, not in binary form via apt-get (which numbers packages by numeric version) ** if this isn't possible, it may be necessary to downgrade to Postgres 9.2 (which will unfortunately be missing some features that we now use) # see if this fixes the problem h3(. VM rollback approach # restore vegbiendev to last working configuration # upgrade Postgres # see if this reproduces the problem