Package: dbconfig-common
Version: 1.8.29+etch1
Followup-For: Bug #418479
I've tried installing webcalendar. webcalendar is in testing/unstable,
and I use a stable version with occasional testing/unstable/experimental
packages. (dbconfig-common is in stable version)
I came across the following dbconfig-common message while trying to
install webcalendar:
============================================================================
Configuring webclendar
webcalendar must have a database installed and configured before it
can be used. If you like, this can be handled with bdconfig-common.
If you are an advanced database administrator and know that you want
to perform this configuration manually, or if your database has
already been installed and configured, you should reuse this option.
Details on what needs to be done should most likely be provided in
/usr/share/doc/webclendar/
Otherwise, you should probably choose this option.
Configure database for webcalendar with dbconfig-common?
<Yes> <No>
============================================================================
I answered Yes to this question and postgresql to the next one. Things
did not work out. I contacted the maintainer of webcalendar, made these
remarks, and it turns out that the average user that I am did not
understand that an installed database was needed. This is why I'd like
to suggest the following:
1) In the first paragraph of the debconf message, why not precise things
in the following sense: "If you like configuration can be handled with
dbconfig-common." This would make me wonder more about installation of
the database.
2) The reference to the documentation should be separated from the
second paragraph. This paragraph indeed starts with a "If you are an
advanced database admnistrator [...] or if your database has already
been installed and configured", which is not the case for me. The fact
that the link is in the same paragraph made me think that this should
not concern me that much.
Hope this remark will help others.
Sincerely yours,
Guillaume Yziquel.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable'), (300, 'testing'), (100, 'unstable'), (30,
'experimental')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-amd64
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
Versions of packages dbconfig-common depends on:
ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii ucf 2.0020 Update Configuration File: preserv
dbconfig-common recommends no packages.
-- debconf information:
dbconfig-common/remote-questions-default: false
dbconfig-common/db/basepath:
dbconfig-common/pgsql/revertconf: false
dbconfig-common/install-error: abort
dbconfig-common/pgsql/no-empty-passwords:
dbconfig-common/pgsql/admin-user: postgres
dbconfig-common/dbconfig-install: true
dbconfig-common/internal/skip-preseed: false
dbconfig-common/db/dbname:
dbconfig-common/dbconfig-reinstall: false
dbconfig-common/remote/host:
dbconfig-common/pgsql/manualconf:
dbconfig-common/pgsql/changeconf: false
dbconfig-common/remote/newhost:
dbconfig-common/dbconfig-remove: true
dbconfig-common/dbconfig-upgrade: true
dbconfig-common/mysql/method: unix socket
dbconfig-common/pgsql/no-user-choose-other-method:
dbconfig-common/upgrade-backup: true
dbconfig-common/internal/reconfiguring: false
dbconfig-common/passwords-do-not-match:
dbconfig-common/pgsql/authmethod-admin: ident
dbconfig-common/remove-error: abort
dbconfig-common/remember-admin-pass: false
dbconfig-common/mysql/admin-user: root
dbconfig-common/pgsql/method: unix socket
dbconfig-common/pgsql/authmethod-user:
dbconfig-common/upgrade-error: abort
dbconfig-common/database-type:
dbconfig-common/db/app-user:
dbconfig-common/remote/port:
dbconfig-common/purge: false
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
