IMHO koji (and mock for that matter) ought to be running the builds inside a captive pty whose ouytput it logs anyway, even if they redirect everything. You never know what crazy nonsense some package is going to try. You can put LIBC_FATAL_STDERR_=1 in the environment to get those messages to stderr instead of /dev/tty. setuid programs will still use /dev/tty. Or, it would use stderr by default if there was no /dev/tty. If you're not going to capture the tty output, then you really should disassociate from the tty (setsid) so /dev/tty does not work at all. I'd call the failure to do one or the other of these a bug in mock or koji. Thanks, Roland -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
