[Gnumed-devel] bootstrapping in en_CA on Mac OS 10.6.x Snow Leopard

[Jim Busser]

Success! About the appended-inline console output...

- the illegal option (on Mac) su --c, as previously explained, seemed of no 
consequence

- where the bootstrapper says
        I need the password for the GNUmed database user [postgres].
        Please type the password: 
        The database owner will be created.
--> can the above line ("The database owner) better say
        The GNUmed database owner [gm-dbo] will be created.
... or is it intended that postgres remain the owner and gm-dbo only a user?

- will all users want the bundles
        bundle "demographics-de"
        ...
        bundle "demographics-es"
        ...
        bundle "au-locale"

- about the destructiveness of this bootstrap... we are careful in the wiki to 
warn that this method *is destructive*  *warning*  *do not do this if you have 
production data* however the output comments that are issued at various stages 
include
        This will update an existing GNUmed version ...
        database to the version ... schema. It does not do
        any harm to the data contained within.
... explanation?

- after adjusting pg_hba.conf per above, I connected from the master client 
(from command line) to access my new local db however
a) the user gets a warning about client version = GIT HEAD
        database version detected: unknown database schema
        database version needed: devel
... is there anything the wanting-to-alpha-test user (or coders) can do to 
better inform or satisfy the above "check"?
b) does the db language setting never get set during bootstrap, therefore 
always be required to be user-acknowledged at first connection, or does it 
sometimes get set during the bootstrap depending on being able to determine the 
locale from (e.g.) the root's locale at the time of bootstrap?

****************************************************

My method for this latest bootstrap on Mac:

This involved the previously installed dependencies from MacPorts, except 
postgres (server) installed from enterprisedb binaries (and selecting, during 
that pg install, locale = en_CA)

1. To gain the root prompt I did
        sudo -i
2. I again forgot to make the root environment know about the dependencies that 
had been installed using MacPorts, so just needed to re-export that PATH
3. I downloaded the newest master source .tgz from gitorious
4. The obstacle "Cannot bootstrap bundles" was fixed by uncommenting, in 
several of the ../bootstrap/ files, the #password prompt for postgres (but, 
curiously, only had to provide it once... maybe to just uncomment in 
bootstrap-local_first or bootstrap-monolithic_core would have sufficed?)
5. I had not bothered yet to reinsert (in the default postgres pg_hba.conf) the 
line
        local   samegroup      +gm-logins                    md5
  but, as already pointed out, this seems not necessary for the bootstrap
6. The console output is below. The bootstrap log file is 1.4Mb... I can send 
it offlist, if Karsten or others should like to look at it.


Here is the console output:
****************************************************
MacBook:wiki_backups djb$ sudo -i
Password:
MacBook:~ root# cd 
/Users/djb/Downloads/gnumed-gnumed/gnumed/gnumed/server/bootstrap 
MacBook:bootstrap root# .bootstrap-latest.sh
-sh: .bootstrap-latest.sh: command not found
MacBook:bootstrap root# export 
PATH=/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/Library/Frameworks/Python.framework/Versions/Current/bin:/bin:/sbin:/usr/bin:/usr/local/bin:/usr/sbin
MacBook:bootstrap root# 
./bootstrap-latest.sh===========================================================Bootstrapping
 latest GNUmed database.

This will set up a GNUmed database of version v14
with the name "gnumed_v14".
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
Creating module import symlink ...
real dir: /Users/djb/Downloads/gnumed-gnumed/gnumed/gnumed/client
    link: /Users/djb/Downloads/gnumed-gnumed/gnumed/gnumed/Gnumed
Adjusting PYTHONPATH ...
/Users/djb/Downloads/gnumed-gnumed/gnumed/gnumed/Gnumed/pycommon/gmTools.py:11: 
DeprecationWarning: the MimeWriter module is deprecated; use the email package 
instead
 import urllib2 as wget, decimal, StringIO, MimeWriter, mimetypes, mimetools
=======================================
Bootstrapping GNUmed database system...
=======================================
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "config" in <gnumed_v2> (or overridden) on <>
bundle "reference" in <gnumed_v2> (or overridden) on <>
bundle "demographics" in <gnumed_v2> (or overridden) on <>
bundle "clinical" in <gnumed_v2> (or overridden) on <>
bundle "documents" in <gnumed_v2> (or overridden) on <>
bundle "office" in <gnumed_v2> (or overridden) on <>
-------------------------------------------------------
This will set up a monolithic GNUmed backend with all bundles
in one database named [gnumed]. It will contain the core schema
without country or language-specific components. Those will
have to be added by using one of the bootstrap-XX.conf file
where XX represents the ISO country code.

Currently this file will also import the test accounts which
MUST be removed prior to real use.

Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "config" ...
Cannot bootstrap bundles.

Please check the log file for details:

 
/Users/djb/Downloads/gnumed-gnumed/gnumed/gnumed/server/bootstrap/bootstrap-latest.log

Bootstrapping "gnumed_v14" did not finish successfully. Aborting.
MacBook:bootstrap root# open 
/Users/djb/Downloads/gnumed-gnumed/gnumed/gnumed/server/bootstrap/bootstrap-latest.log
MacBook:bootstrap root# ./bootstrap-latest.sh
===========================================================
Bootstrapping latest GNUmed database.

This will set up a GNUmed database of version v14
with the name "gnumed_v14".
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
Adjusting PYTHONPATH ...
/Users/djb/Downloads/gnumed-gnumed/gnumed/gnumed/Gnumed/pycommon/gmTools.py:11: 
DeprecationWarning: the MimeWriter module is deprecated; use the email package 
instead
 import urllib2 as wget, decimal, StringIO, MimeWriter, mimetypes, mimetools
=======================================
Bootstrapping GNUmed database system...
=======================================
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "config" in <gnumed_v2> (or overridden) on <>
bundle "reference" in <gnumed_v2> (or overridden) on <>
bundle "demographics" in <gnumed_v2> (or overridden) on <>
bundle "clinical" in <gnumed_v2> (or overridden) on <>
bundle "documents" in <gnumed_v2> (or overridden) on <>
bundle "office" in <gnumed_v2> (or overridden) on <>
-------------------------------------------------------
This will set up a monolithic GNUmed backend with all bundles
in one database named [gnumed]. It will contain the core schema
without country or language-specific components. Those will
have to be added by using one of the bootstrap-XX.conf file
where XX represents the ISO country code.

Currently this file will also import the test accounts which
MUST be removed prior to real use.

Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "config" ...
I need the password for the GNUmed database user [postgres].
Please type the password: 
The database owner will be created.
You will have to provide a new password for it
unless it is pre-defined in the configuration file.

Make sure to remember the password for later use.

I need the password for the GNUmed database user [gm-dbo].
Please type the password: 
==> cloning [template1] (5280 kB) as target database [gnumed_v2] ...
==> transferring users ...
   ... skipped (unconfigured)
==> bootstrapping "reference" ...
==> bootstrapping "demographics" ...
==> bootstrapping "clinical" ...
==> bootstrapping "documents" ...
==> bootstrapping "office" ...
==> setting up auditing ...
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
   ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "demographics-de" in <gnumed_v2> (or overridden) on <>
bundle "clinical-de" in <gnumed_v2> (or overridden) on <>
bundle "reference-de" in <gnumed_v2> (or overridden) on <>
bundle "Uebersetzung" in <gnumed_v2> (or overridden) on <>
-------------------------------------------------------
Dieses Skript installiert Daten in ein GNUmed-Datenbanksystem,
mit denen GNUmed fuer Deutschland angepasst wird.

Die Datenbankstruktur muss bereits in einer GNUmed-Datenbank
installiert sein, ebenso muss mindestens der Nutzer gm-dbo
bereits existieren.
==> bootstrapping "demographics-de" ...
==> bootstrapping "clinical-de" ...
==> bootstrapping "reference-de" ...
==> bootstrapping "Uebersetzung" ...
==> setting up auditing ...
   ... skipped (disabled)
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
   ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "demographics-es" in <gnumed_v2> (or overridden) on <>
-------------------------------------------------------

Este script instala en la base de datos de GNUmed las informaciones
especificas para su uso en Espana (provincias).

Como requisitos, el esquema debe haber sido previamente instalado
en la base de datos "gnumed" y, al menos, el usuario "gm-dbo" debe
haber sido creado.

==> bootstrapping "demographics-es" ...
==> setting up auditing ...
   ... skipped (disabled)
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
   ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "demographics-ca" in <gnumed_v2> (or overridden) on <>
-------------------------------------------------------
This script installs data into a GNUmed database system in
order to localise GNUmed for Canada.

The core database schema must have been imported into a database
"gnumed" already. Also, the user gm-dbo must exist.

==> bootstrapping "demographics-ca" ...
==> setting up auditing ...
   ... skipped (disabled)
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
   ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "au-locale" in <gnumed_v2> (or overridden) on <>
-------------------------------------------------------
This script installs data into a GNUmed database system in
order to localise GNUmed for Australia.

The core database schema must have been imported into a database
"gnumed" already. Also, the user gm-dbo must exist.

==> bootstrapping "au-locale" ...
==> setting up auditing ...
   ... skipped (disabled)
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
   ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "test data" in <gnumed_v2> (or overridden) on <>
-------------------------------------------------------
This script installs test data into an existing GNUmed database
named "gnumed". Also, the database owner "gm-dbo" must exist
already.
==> bootstrapping "test data" ...
==> setting up auditing ...
   ... skipped (disabled)
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
   ... skipped (no scripts to run)
==> setting up auditing ...
   ... skipped (disabled)
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
   ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v2-v3-static" in <gnumed_v3> (or overridden) on <>
bundle "v2-v3-dynamic" in <gnumed_v3> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 2
database to the version 3 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v2-v3-static" ...
==> cloning [gnumed_v2] (19 MB) as target database [gnumed_v3] ...
==> transferring users ...
   ... skipped (unconfigured)
==> bootstrapping "v2-v3-dynamic" ...
==> setting up auditing ...
   ... skipped (disabled)
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
   ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v3-v4-static" in <gnumed_v4> (or overridden) on <>
bundle "v3-v4-dynamic" in <gnumed_v4> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 3
database to the version 4 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v3-v4-static" ...
==> cloning [gnumed_v3] (19 MB) as target database [gnumed_v4] ...
==> transferring users ...
   ... skipped (unconfigured)
==> bootstrapping "v3-v4-dynamic" ...
==> setting up auditing ...
   ... skipped (disabled)
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
   ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v4-v5-static" in <gnumed_v5> (or overridden) on <>
bundle "v4-v5-dynamic" in <gnumed_v5> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 4
database to the version 5 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v4-v5-static" ...
==> cloning [gnumed_v4] (19 MB) as target database [gnumed_v5] ...
==> transferring users ...
   ... skipped (unconfigured)
==> bootstrapping "v4-v5-dynamic" ...
==> setting up auditing ...
   ... skipped (disabled)
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
   ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v5-v6-static" in <gnumed_v6> (or overridden) on <>
bundle "v5-v6-dynamic" in <gnumed_v6> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 5
database to the version 6 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v5-v6-static" ...
==> cloning [gnumed_v5] (19 MB) as target database [gnumed_v6] ...
==> transferring users ...
==> bootstrapping "v5-v6-dynamic" ...
==> setting up auditing ...
   ... skipped (disabled)
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
   ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v6-v7-static" in <gnumed_v7> (or overridden) on <>
bundle "v6-v7-dynamic" in <gnumed_v7> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 6
database to the version 7 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v6-v7-static" ...
==> cloning [gnumed_v6] (19 MB) as target database [gnumed_v7] ...
==> transferring users ...
==> bootstrapping "v6-v7-dynamic" ...
==> setting up auditing ...
   ... skipped (disabled)
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v7-v8-static" in <gnumed_v8> (or overridden) on <>
bundle "v7-v8-dynamic" in <gnumed_v8> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 7
database to the version 8 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v7-v8-static" ...
==> cloning [gnumed_v7] (20 MB) as target database [gnumed_v8] ...
==> transferring users ...
==> bootstrapping "v7-v8-dynamic" ...
==> setting up auditing ...
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
   ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v8-v9-static" in <gnumed_v9> (or overridden) on <>
bundle "v8-v9-dynamic" in <gnumed_v9> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 8
database to the version 9 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v8-v9-static" ...
==> cloning [gnumed_v8] (20 MB) as target database [gnumed_v9] ...
==> transferring users ...
==> bootstrapping "v8-v9-dynamic" ...
==> setting up auditing ...
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
   ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v9-v10-static" in <gnumed_v10> (or overridden) on <>
bundle "v9-v10-dynamic" in <gnumed_v10> (or overridden) on <>
bundle "v10-fixups" in <gnumed_v10> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 9
database to the version 10 schema. It does not do
any harm to the data contained within.

The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v9-v10-static" ...
==> cloning [gnumed_v9] (21 MB) as target database [gnumed_v10] ...
==> transferring users ...
==> bootstrapping "v9-v10-dynamic" ...
==> bootstrapping "v10-fixups" ...
==> setting up auditing ...
   ... skipped (disabled)
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
   ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v10_fixups-pre_v11" in <gnumed_v11> (or overridden) on <>
bundle "v10-v11-static" in <gnumed_v11> (or overridden) on <>
bundle "v10-v11-dynamic" in <gnumed_v11> (or overridden) on <>
bundle "v11-fixups" in <gnumed_v11> (or overridden) on <>
bundle "v11-test_data" in <gnumed_v11> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 10
database to the version 11 schema. It does not do
any harm to the data contained within.

The existing database will be cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v10_fixups-pre_v11" ...
==> cloning [gnumed_v10] (21 MB) as target database [gnumed_v11] ...
==> transferring users ...
==> bootstrapping "v10-v11-static" ...
==> bootstrapping "v10-v11-dynamic" ...
==> bootstrapping "v11-fixups" ...
==> bootstrapping "v11-test_data" ...
==> setting up auditing ...
==> setting up notifications ...
   ... skipped (disabled)
==> upgrading reference data sets ...
   ... skipped (no scripts to run)
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v11_fixups-pre_v12" in <gnumed_v12> (or overridden) on <>
bundle "v11-v12-static" in <gnumed_v12> (or overridden) on <>
bundle "v11-v12-dynamic" in <gnumed_v12> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 11
database to the version 12 schema. It does not do
any harm to the data contained within.

The existing database will be cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v11_fixups-pre_v12" ...
==> cloning [gnumed_v11] (23 MB) as target database [gnumed_v12] ...
==> transferring users ...
==> bootstrapping "v11-v12-static" ...
==> bootstrapping "v11-v12-dynamic" ...
==> setting up auditing ...
==> setting up notifications ...
==> upgrading reference data sets ...
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v12-v13-static" in <gnumed_v13> (or overridden) on <>
bundle "v12-v13-dynamic" in <gnumed_v13> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 12
database to the version 13 schema. It does not do
any harm to the data contained within.

The existing database will be cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v12-v13-static" ...
==> cloning [gnumed_v12] (24 MB) as target database [gnumed_v13] ...
==> transferring users ...
==> bootstrapping "v12-v13-dynamic" ...
==> setting up auditing ...
==> setting up notifications ...
==> upgrading reference data sets ...
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v13-v14-static" in <gnumed_v14> (or overridden) on <>
bundle "v13-v14-dynamic" in <gnumed_v14> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 13
database to the version 14 schema. It does not do
any harm to the data contained within.

The existing database will be cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v13-v14-static" ...
==> cloning [gnumed_v13] (36 MB) as target database [gnumed_v14] ...
==> transferring users ...
==> bootstrapping "v13-v14-dynamic" ...
==> setting up auditing ...
==> setting up notifications ...
==> upgrading reference data sets ...
==> verifying target database schema ...
   ... skipped (devel version)
==> checking migrated data for plausibility ...
==> sanity checking PostgreSQL authentication settings ...

Note that even after successfully bootstrapping the GNUmed 
database PostgreSQL may still need to be configured to
allow GNUmed clients to connect to it.

In many standard PostgreSQL installations this amounts to
adding the authentication directive:

 "local   samegroup   +gm-logins   md5"

in the proper place of the file:

 /Library/PostgreSQL/8.4/data/pg_hba.conf

For details refer to the GNUmed documentation at:

 http://wiki.gnumed.de/bin/view/Gnumed/ConfigurePostgreSQL

Done bootstrapping GNUmed database: We very likely succeeded.
Dropping obsoleted staging database gnumed_v2 ...
(you may need to provide the password for root)
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
Dropping obsoleted staging database gnumed_v3 ...
(you may need to provide the password for root)
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
Dropping obsoleted staging database gnumed_v4 ...
(you may need to provide the password for root)
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
Dropping obsoleted staging database gnumed_v5 ...
(you may need to provide the password for root)
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
Dropping obsoleted staging database gnumed_v6 ...
(you may need to provide the password for root)
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
Dropping obsoleted staging database gnumed_v7 ...
(you may need to provide the password for root)
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
Dropping obsoleted staging database gnumed_v8 ...
(you may need to provide the password for root)
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
Dropping obsoleted staging database gnumed_v9 ...
(you may need to provide the password for root)
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
Dropping obsoleted staging database gnumed_v10 ...
(you may need to provide the password for root)
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
Dropping obsoleted staging database gnumed_v11 ...
(you may need to provide the password for root)
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
Dropping obsoleted staging database gnumed_v12 ...
(you may need to provide the password for root)
su: illegal option -- c
usage: su [-] [-flm] [login [args]]
MacBook:bootstrap root#