Control: severity -1 normal On Wed, 18 Apr 2018 10:30:56 -0700 Steve Langasek <steve.langa...@canonical.com> wrote: > > There is at least one bug here in the package, which is that the > autopkgtests make a brittle assumption that eth0 will be available in the > test bed. eth0 is a legacy interface name in the kernel, and despite the > fact that eth0 is currently present on the ci.debian.net testbeds, this is > not a robust assumption. If you want to reorder the tests so that the > config file setup is done first, then that would address the bug in the > autopkgtests. >
Hi, thanks for taking the time to elaborate. I talked to upstream to know if they plan to implement something for interface names at runtime. No plans. And I don't have time to work on that myself. Downgrading the severity to avoid the package removal from testing. On a side note: you mentioned the daemon should be up and running to consider the package being OK installed. While I agree that by installing the package we should get a daemon ready to use, How would you do that? given suricata acts as a firewall, the config is strictly baked per environment and no preset could be used as default?
