mahara-contributors team mailing list archive

[François Marier <francois@xxxxxxxxxx>]

There is a bug for this on the Debian tracker already:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472565

** Changed in: mahara
       Status: Confirmed => Invalid

** Changed in: mahara
     Assignee: Nigel-catalyst (nigel-catalyst) => (unassigned)

** Bug watch added: Debian Bug tracker #472565
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472565

-- 
Debian packages should make use of dbconfig-common
https://bugs.launchpad.net/bugs/547900
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.

Status in Mahara ePortfolio: Invalid

Bug description:
Andrew McMillan suggested making use of dbconfig-common to create the database and the required user account using debconf, instead of relying on instructions in the README.Debian file.

Here's the description for that package:

 dbconfig-common presents a policy and implementation for
 managing various databases used by applications included in
 debian packages.

 dbconfig-common can:
  * support mysql, postgresql, and sqlite based applications
  * create databases and database users
  * access local or remote databases
  * upgrade/modify databases when upstream changes database structure
  * remove databases and database users
  * generate config files in many formats with the database info
  * import configs from packages previously managing databases on their own
  * prompt users with a set of normalized, pre-translated questions
  * handle failures gracefully, with an option to retry.
  * do all the hard work automatically
  * work for package maintainers with little effort on their part
  * work for local admins with little effort on their part
  * comply with an agreed upon set of standards for behaviour
  * do absolutely nothing if it is the whim of the local admin
  * perform all operations from within the standard flow of debian
    package maintenance (no additional skill is required of the local
    admin)

This bug was imported from eduforge.org, see:
https://eduforge.org/tracker/index.php?func=detail&aid=1733&group_id=176&atid=742