Andreas Beckmann <a...@debian.org> (2023-05-30): > crowdsec-firewall-bouncer passed the test
That I don't really understand. > crowdsec-custom-bouncer always failed in sid (and testing) with > --install-recommends, crowdsec-firewall-bouncer always succeeded > > The difference caused by --install-recommends is > > * crowdsec (which crowdsec-custom-bouncer Recommends) gets installed > * but crowdsec-custom-bouncer gets configured first, i.e. after crowdsec got > unpacked but before crowdsec could create the configuration file > /etc/crowdsec/config.yaml > * crowdsec-custom-bouncer.postinst only checks for cscli which is available > after unpacacking Sure, I got that part, and we're also seeing it now with a simple `apt-get install $bouncer` in a fresh VM, so this is a real issue I'd like to fix ASAP. My question is why that wouldn't show up for crowdsec-firewall-bouncer as well since the logic is essentially the same! (It does a little firewall detection, and there's basically a s/custom/firewall/ for a few filenames, but the cscli part is exactly the same. And they both only have crowdsec listed in Recommends.) Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
signature.asc
Description: PGP signature
