Hallo Andreas, Cyril Brulebois <cy...@debamax.com> (2023-05-27): > Andreas Beckmann <a...@debian.org> (2023-05-04): > > during a test with piuparts I noticed your package failed to install. > > As per definition of the release team this makes the package too buggy > > for a release, thus the severity. > > For some reason, I didn't receive this bug report or the autoremoval > notification. > > I've just confirmed that requesting the bouncer's installation, in a > freshly-installed bookworm VM, leads to the same issue. That's something > that definitely worked when the bouncer was first introduced, I'm not > exactly sure why that's no longer the case; I'd be happy to have some > time to gather my thoughts, and upstream's, regarding this issue.
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 might just file a report myself later on, I have to find a solution anyway, and it should be applicable to both packages… but it'd be better to have a report filed anyway, for documentation purposes. When that happens, I'm expecting it to be OK to use the same tags as this bug report… but I've kept Paul in copy to make sure. Also, thanks for your QA work in general. Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
signature.asc
Description: PGP signature
