clone 493938 -1 reassign -1 base retitle -1 Essential packages introduced in a release are not installed automatically tag 493938 + wontfix thanks On Wed, Aug 06, 2008 at 04:48:24PM -0400, Dan Merillat wrote: > Yes, it was really not present on my machine and required installing. > > Older installation doing upgrades rather then blowing it away and > reinstalling. As far as I can tell, neither apt-get nor aptitude ever > noticed a missing essential/required package that appeared after the > initial install. Perhaps this is really a package management bug? It looks like, reassigning to base. I'm not sure if this is an apt bug in itself, or not. To explain the situation: mktemp is essential since 2006-05-18, which is the version in Etch. ca-certificates does, of course, not depend on it, although it needs it in postinst. This is already the second bug report I got about this issue, so it seems not that uncommon. The problem: Machines upgraded from Sarge to Etch won't get mktemp pulled in, because nothing depends on essential packages. They won't receive it later on, again out of the same reason. They are only pulled into new installations, by (c)debootstrap, due to their priority and their essential status. So some meta package needs to depend on those newly introduced essential packages for one release (as we don't support skipping one anyway). Kind regards, Philipp Kern
Attachment:
signature.asc
Description: Digital signature