Sven Hartge wrote:
> Package: bacula-director-sqlite
> Version: 3.0.2-2.0~sh.2
> Severity: important
>
> Hi.
>
> After the upgrade from bacula-director-sqlite to bacula-director-sqlite3
> the configfile for the director /etc/bacula/bacula-dir.conf is lost and
> replaced by the default one without notice.
>
> I believe this is because this configfile belongs to
> bacula-director-sqlite and it is removed with its package during the upgrade.
>
> Since (as far as I know) no configfile may belong to more than one
> package, I have no idea, how to solve this problem to allow a smooth
> upgrade from the deprecated sqlite package to the new sqlite3 one.
This one is a something of a mystery to me.
There is a postinst that is doing:
if [ ! -f $DSTDIR/$CONFIG ]; then
TARGET=$DSTDIR/$CONFIG
else
TARGET=$DSTDIR/$CONFIG.dist
fi
and then copies (and munges) a default config file to that location. But
your config file was already there.
The directors also have a postinst that does:
case "$1" in
purge)
rm -f $CONFFILE $CONFFILE.dist
db_purge
;;
but your bacula-director-sqlite wasn't being removed, much less purged.
I am confused how this could happen. Could it perhaps have been related
to the (just fixed) dep on sqlite2 that caused the package to be removed?
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
