[Dbconfig-common-devel] dbconfig and default values

[sean finney]

hi radu,

On Tue, Apr 11, 2006 at 05:34:23PM +0300, Radu Spineanu wrote:
> Creating config file /etc/dbconfig-common/simba.conf with new version
> Configuration file `/etc/simba/simba-db.cfg'
>  ==> File on system created by you or by a script.
>  ==> File also in package provided by package maintainer.
>    What would you like to do about it ?  Your options are:
>     Y or I  : install the package maintainer's version
>     N or O  : keep your currently-installed version
>       D     : show the differences between the versions
>       S     : show the side-by-side differences between the versions
>       Z     : start a new shell to examine the situation
>  The default action is to keep your current version.
> ***  simba-db.cfg  (Y/I/N/O/D/Z) [default=N] ?
> [...]
> 
> That file does not exist neither in the package or on the filesystem. If

but it does exist in the ucf database.   my guess/hope is that this is
a side effect of your developing the package and not actually a bug.
if you purge the package, and reinstall it, do you still get the
problem?

> i hit D:
> 
> --- /dev/null   2006-04-10 13:15:48.167259456 +0300
> +++ /tmp/dbconfig-generate-include.lo0pUi       2006-04-11
> 17:10:28.215596400 +0300
> @@ -0,0 +1,7 @@
> +# local database configuration file:
<snip>

this happens when a file is removed from the filesystem but
still exists in the ucf database.  so you would see something like
this if you manually removed the file and then reconfigured/upgraded
your package (or possibly even reinstall with dbc depending on
circumstances), or if dbc wasn't doing its job managing the ucf
file.  like i said, my guess/hope is the former :)


	sean

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/attachments/20060411/4087658c/attachment.pgp