Control: notfound -1 0.92
Hi Michael,
On Thu, 26 May 2016 12:56:29 +0200 Michael Weghorn <m.wegh...@posteo.de>
wrote:
> On 2016-05-24 04:20, James Valleroy wrote:
> > Is there a way to accommodate this, while also preserving local
> > changes during an upgrade?
>
> Thank you for your quick reply. Reading that post helped me better
> understand the problem and how everything is related with each other.
>
> On further research, I found that the man page of debconf-devel (7)
> (section "Config file handling") describes how config files should be
> handled by debconf.
> The way unattended-upgrades does it is totally according to that.
>
> This showed me that my understanding of debconf so far was not
> sufficient and my first approach of changing the value was not
> appropriate.
> I checked how FAI [1] does it and the appropriate way seems to be to
> use the "DEBCONF_DB_OVERRIDE" environment variable as described in the
> man page of debconf (7).
>
> Example:
>
> root@debian:~# cat /tmp/override.dat
> Name: unattended-upgrades/enable_auto_updates
> Template: unattended-upgrades/enable_auto_updates
> Value: false
> Owners: unattended-upgrades
>
> root@debian:~# DEBCONF_DB_OVERRIDE="File{/tmp/override.dat
> readonly:true}" DEBIAN_FRONTEND=noninteractive dpkg-reconfigure
> unattended-upgrades
> Replacing config file /etc/apt/apt.conf.d/20auto-upgrades with new
> version
> update-rc.d: warning: start and stop actions are no longer
> supported; falling back to defaults
> debconf: DbDriver "_ENV_stack": unable to save changes to:
> unattended-upgrades/enable_auto_updates
>
> Then, to also update the debconf cache:
>
> root@debian:~# debconf-copydb override_db config
> --config=Name:override_db --config=Driver:File
> --config=Filename:"/tmp/override.dat"
>
>
> Therefore, this bug should possibly closed as "invalid".
Doing so.
Cheers,
Balint
