[Debconf-devel] Bug#864875: debconf: frontend exits with status 10 after last upgrade when /var/cache is tmpfs

[Colin Watson]

On Thu, Feb 15, 2018 at 08:58:29PM +0200, Niko Tyni wrote:
> On Thu, Feb 15, 2018 at 03:26:50PM +0000, Colin Watson wrote:
> > On Thu, Feb 15, 2018 at 10:39:15AM +0000, Dominic Hargreaves wrote:
> > > The debconf database *is* in /var/cache so I don't know how anything
> > > can be expected to work after it's wiped. But according to the FHS
> > > what Franz is doing is completely allowable...
> > > 
> > > CCing the Debconf developers in case they can shed any light on this.
> > 
> > Sounds like the long-known https://bugs.debian.org/247134.  It probably
> > needs to be dealt with at some point, but oh goodness the anticipated
> > migration pain ...
> 
> I'm a bit surprised by #247134. Doesn't the "debconf is not a registry"
> mantra imply that all data in /var/cache/debconf should be possible to
> regenerate from config files in /etc/ and the like?

Well, that's the noble intent, but (even aside from debconf not quite
recreating the bits it needs for itself) I'm not aware that anyone tests
it and it's probably never been true in reality.

-- 
Colin Watson                                       [cjwatson at debian.org]