The SIGCHASE code is limited to the dig and host commands, and (as far as I can tell), any regression would be limited to failures when using the sigchase options (which currently just say "invalid option +sigchase", so they wouldn't particularly be regressions as much as continued bugs.) The code seems to be checking if sigchase is in use everywhere that the code behaves differently because of the compile switch.
lamont -- SRU for bind9 to 9.4.2.dfsg.P2 on hardy https://bugs.launchpad.net/bugs/279316 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
