Package: dbconfig-common Version: 1.8.29 Severity: normal Hi,
it would be nice if this scenario were supported: Two package, one a frontend and one a real dbconfig package, should be able to share the configuration by setting the same package name in the calls to dbc_go. Currently it seems to fail when the frontend package is purged, confusing the other package. Note that I do not have that setup any more with my packages, so I don’t have a developing test case. But it’s still a nice to have item :-) Greetings, Joachim -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.otto Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages dbconfig-common depends on: ii debconf [debconf-2.0] 1.5.10 Debian configuration management sy ii ucf 2.0017 Update Configuration File: preserv dbconfig-common recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
