Re: Bug#766459: debootstrap: should not try to configure
On Mon, 27 Oct 2014, Michael Tautschnig wrote:
> I'm hoping this is not going to be too philosophical, so I'll enlist the facts
> first (please let me know if I got any of them wrong):
> debootstrap'ing a system fails, because
> - chown root:root ... won't work when invoked from base-files' postinst
> - version 7.7 of base-files is the first to actually have this call when invoked
> from within (c)debootstrap
Regarding previous point, it should be noted that base-files postinst
has a lot of chown calls. I would like to know how it is possible that
only the recently added is the one that fails and not the others
(if that's really the case).
BTW: I don't know what is the proper way to debug this (private
repository using reprepro?). Can anybody confirm that the chown that
fails is exactly the one at the very end?
> So let's see what Debian Policy says in 3.8 Essential packages:
> "[...] Since dpkg will not prevent upgrading of other packages while an
> essential package is in an unconfigured state, all essential packages must
> supply all of their core functionality even when unconfigured. If the package
> cannot satisfy this requirement it must not be tagged as essential, and any
> packages depending on this package must instead have explicit dependency fields
> as appropriate. [...]"
This is about dpkg when making upgrades. It means that once an
essential package is properly configured, it should not stop working
because of it being "unconfigured" by dpkg (whatever that means).
I think it does not apply here.
[ snipped philosophical stuff. I would much prefer to have free time
to work on this rather than discuss about it. Really ].