On Wed, Jun 13, 2012 at 09:54:23AM +0300, Teodor MICU wrote: > 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».
Oh, I did not express myself very clear here, sorry for that. Its not calling dpkg but its calling the code in apt that would call dpkg and instead of calling dpkg that code will simply print all the commands it would run. But it does not actually run them just pretend. Still, this is probably a bit confusing, so I wonder if it should a) print something that explains that its just printing what would be done but not doing it b) not do that at all and provide a different (hidden) option to enable this behavior as only useful in rare debugging cases Thanks! Michael -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
