On 30/05/2023 21.18, Andreas Beckmann wrote:
On 30/05/2023 20.24, Cyril Brulebois wrote:
Alright, with RC 4 out of the way, I'm looking at this issue again, and
it seems the “sibling package” crowdsec-firewall-bouncer is affected by
the exact same issue (not surprisingly). I'm curious as to whether it
showed up in those piuparts tests, if you have bug reports yet to be
filed, or something else.
I have successful test logs from Apr 09 for crowdsec-firewall-bouncer,
rescheduled them right now, will report later what happened.
crowdsec-firewall-bouncer passed the test
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
Andreas
