On Fri, Jan 06, 2012 at 05:44:28PM -0000, Thomas Bushnell, BSG wrote:
> I'm confused about why chroot_setup is the issue here. It's the apt-
> install command inside the grub_probe command which is spitting out
> output, and the output it spits out looks like typical apt-get output.
apt-install uses chroot_setup, via in-target. The apt-get output goes
to stderr (due to 'debconf-apt-progress --logstderr') and thence to
syslog and doesn't interfere with grub_probe. By contrast, the
dpkg-divert output went to stdout.
Besides, chroot_setup is the only thing anywhere around here that
changed recently; I'd have guessed at that myself if Scott hadn't beaten
me to it!
On Fri, Jan 06, 2012 at 05:44:28PM -0000, Thomas Bushnell, BSG wrote:
> I'm confused about why chroot_setup is the issue here. It's the apt-
> install command inside the grub_probe command which is spitting out
> output, and the output it spits out looks like typical apt-get output.
apt-install uses chroot_setup, via in-target. The apt-get output goes apt-progress --logstderr') and thence to
to stderr (due to 'debconf-
syslog and doesn't interfere with grub_probe. By contrast, the
dpkg-divert output went to stdout.
Besides, chroot_setup is the only thing anywhere around here that
changed recently; I'd have guessed at that myself if Scott hadn't beaten
me to it!