2012/6/12 Michael Vogt <[email protected]>: > On Thu, Nov 24, 2011 at 02:48:58PM +0200, Teodor MICU wrote: >> I've found a corner case were u-a still executes 'dpkg' when invoked >> with --dry-run. There are packages that should be upgraded but no >> upgrade is performed because it was instructed by '--dry-run' option. >> Also, other packages are blacklisted. > > This is partily intentional as its using a feature inside apt so that > everything is done for real (including the download) and apt will > print what it would do with dpkg. Its probably more of a debug aid.
Is it necessary to call dpkg? What could happen if you disable this debug? > What is the use-case you have for this? I wonder if maybe we need > --dry-run that would actually just stop and a additional > --debug-dpkg or similar that would do what the current --dry-run is > doing. Depends on how important this debug test is. >From a design point of view using just '--dry-run' should not call «dpkg». Thanks -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
