Package: installation-reports Using DISTRIB_RELEASE="9 (stretch) - installer build 20161212-00:04" the user chooses "No", the default, to the popularity-contest question.
He notices through the corner of his eye, something about the package flashing by on the screen anyway! Indeed the logs expose the fact that the package is installed then removed right away. One big no-op! Please don't install it in the first place if the user has said No. Dec 25 23:38:10 in-target: The following NEW packages will be installed: Dec 25 23:38:10 in-target: popularity-contest Dec 25 23:38:10 in-target: 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Dec 25 23:38:10 in-target: Need to get 0 B/70.6 kB of archives. Dec 25 23:38:10 in-target: After this operation, 179 kB of additional disk space will be used. Dec 25 23:38:10 in-target: Get:1 cdrom://[Debian GNU/Linux testing _Stretch_ - Official Snapshot amd64 NETINST Binary-1 20161212-05:24] stretch/main amd64 popularity-contest all 1.64 [70.6 kB] Dec 25 23:38:10 in-target: Preconfiguring packages ... Dec 25 23:38:14 in-target: Selecting previously unselected package popularity-contest. Dec 25 23:38:14 in-target: ^M Dec 25 23:38:14 in-target: (Reading database ... Dec 25 23:38:14 in-target: 15048 files and directories currently installed.) Dec 25 23:38:14 in-target: Preparing to unpack .../popularity-contest_1.64_all.deb ... Dec 25 23:38:14 in-target: Unpacking popularity-contest (1.64) ...^M Dec 25 23:38:14 in-target: Setting up popularity-contest (1.64) ... Dec 25 23:38:15 in-target: (Reading database ... 15073 files and directories currently installed.) Dec 25 23:38:15 in-target: Removing popularity-contest (1.64) ... Dec 25 23:38:15 in-target: Purging configuration files for popularity-contest (1.64) ... Dec 25 23:38:16 pkgsel: starting tasksel Dec 25 23:39:30 in-target: Reading package lists...
