package multistrap tag 593326 + wontfix quit Neil Williams wrote: >> Currently multistrap emits a lot of output. > Actually, it outputs very little itself. Most comes from apt and dpkg.
Right. >> It would be nice if this could be elided, with a --quiet option. > Exactly what output are you seeking to remove? I was mainly thinking of passing -q or -qq on to apt-get. > However, multistrap operations take an appreciable amount of time and > some form of user feedback is essential. Granted, when the user is sitting there watching it. The use case I have in mind is when I run multistrap from a cron job, or just kick off a build, go have lunch, then come back and read the output. I want to reduce the amount of "I'm working!" output so that any "I'm NOT working!" output will stand out. I tried simply discarding stdout, and this appears to work. Usually I'm too nervous to do that, because so many programs are ill-behaved and print errors to stdout. Fortunately, apt-get and dpkg behave :-) > [...] Progress indicators are ugly but letting the script appear to > hang is worse. If that is what you expect, I will have to close this > bug as wontfix. While I agree that progress indicators should be on *by default*, I think it should be possible to opt-out of them in batch runs. Since we disagree, I've WONTFIXed this ticket; I'll simply set my batch jobs to redirect stdout from multistrap to /dev/null. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
