Bug#560828: dbconfig-common: allow packages to hint to dbconfig common to use local or remote database connections only
On 20/07/2013 10:30 AM, Paul Gevers wrote: I believe this is already possible (currently due to bug 476946 only during installation) by properly preseeding the debconf entry for moodle*/database/method in your package. If you hadn't figured this out in the mean time, please verify if I am correct and reply/close as appropriate. Argh, I'm sure you're right and we were just not correctly preseeding, but I am so far away from that particular package now I really have no idea. Perhaps someone in the packaging team knows. I've cc'd them. Else if they don't reply I'm happy if you close this bug. Best, Penny -- Penny Leach | http://mjollnir.org | @mjollnir | 0xA110DDD2 signature.asc Description: OpenPGP digital signature
Bug#560828: dbconfig-common: allow packages to hint to dbconfig common to use local or remote database connections only
Control: tags -1 moreinfo On 12-12-09 16:59, Penny Leach wrote: Sorry for this bug taking so much time to get attention. We started splitting moodle into three packages, moodle-mysql, moodle-pgsql and moodle-remotedb, in order to get around this problem of whether to depend on database servers or not. If we did that, we would want the first two to be able to tell dbconfig-common that it should always connect to a local db (since we're depending on it), and in the last case, we would want to tell it to only connect to a remote db server. This should I guess overwrite the dbconfig-common debconf setting of whether or not we're likely to connect to remote databases. It would be great if this was possible. Sorry there's no patch attached :( I believe this is already possible (currently due to bug 476946 only during installation) by properly preseeding the debconf entry for moodle*/database/method in your package. If you hadn't figured this out in the mean time, please verify if I am correct and reply/close as appropriate. signature.asc Description: OpenPGP digital signature
Bug#560828: dbconfig-common: allow packages to hint to dbconfig common to use local or remote database connections only
Package: dbconfig-common Version: 1.8.41 Severity: wishlist We started splitting moodle into three packages, moodle-mysql, moodle-pgsql and moodle-remotedb, in order to get around this problem of whether to depend on database servers or not. If we did that, we would want the first two to be able to tell dbconfig-common that it should always connect to a local db (since we're depending on it), and in the last case, we would want to tell it to only connect to a remote db server. This should I guess overwrite the dbconfig-common debconf setting of whether or not we're likely to connect to remote databases. It would be great if this was possible. Sorry there's no patch attached :( -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-vserver-686 (SMP w/2 CPU cores) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dbconfig-common depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii ucf 3.0021 Update Configuration File: preserv dbconfig-common recommends no packages. Versions of packages dbconfig-common suggests: ii mysql-client 5.1.37-2 MySQL database client (metapackage ii mysql-client-5.1 [virtual-mys 5.1.37-2 MySQL database client binaries ii postgresql-client 8.4.0-2front-end programs for PostgreSQL ii postgresql-client-8.4 [postgr 8.4.0-2+b1 front-end programs for PostgreSQL -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
