On Wed, 5 Oct 2011, Goswin von Brederlow wrote: > I think it is safe to say that essential packages have to be configured > before the rest by any bootstraping tool.
The job of any bootstrapping tools is precisely to configure the essential packages. By creating the essential flag, we have all agreed that we will not use the Depends field on any package which is Essential: yes. This means that the knowledge about which package should be configured first is left as a task for bootstrapping tools. I understand that you want to see this issue fixed, but you are looking for the wrong solution, which is to ignore completely the definition of essential flag. Instead, I would try to see why this used to work in the past and why it does no longer work. Lack of a dependency which policy says we should not make explicit does not count as a "cause", and it's therefore the wrong fix. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
