On Wed, Aug 22, 2007 at 02:39:53PM -0000, Ian Jackson wrote: > It is difficult to do much better because of the way that apt invokes > dpkg - in particular, the new dpkg doesn't get to run until the next run > after it has been installed,
True, though in this case that is part of the same apt run (apt unpacks and configures dpkg, then does everything else in a separate dpkg run with the new dpkg). > and apt generally instructs dpkg only to process specific packages. > We don't want to make dpkg process these transitional trigger states > for all packages in an apparently unrelated run because that would be > very unexpected for someone using dpkg from the command line (eg to > fix a broken system). > > So I don't propose to do anything about this in dpkg. However, we must > make sure that the dist-upgrader definitely runs dpkg --configure > --pending after the upgrade. OK, this seems reasonable, but perhaps 'apt-get upgrade' should also do this rather than just doing it in the dist-upgrader? After all apt normally does try to configure anything that's unconfigured, IIRC; it just doesn't notice that it needs to deal with pending triggers. I think it would be reasonable for apt to check for pending triggers and deal with them at the end of 'apt-get [dist-]upgrade'. -- dist-upgrader should run dpkg --configure --pending https://bugs.launchpad.net/bugs/134000 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
