Processing control commands:
> clone -1 -2
Bug #1035499 [crowdsec-custom-bouncer] crowdsec-custom-bouncer: fails to
install with --install-recommends: open /etc/crowdsec/config.yaml: no such file
or directory
Bug 1035499 cloned as bug 1036985
> reassign -2 crowdsec-firewall-bouncer 0.0.25-2
Bug
Control: clone -1 -2
Control: reassign -2 crowdsec-firewall-bouncer 0.0.25-2
Control: retitle -2 crowdsec-firewall-bouncer: fails to install with
--install-recommends: open /etc/crowdsec/config.yaml: no such file or directory
Andreas Beckmann (2023-05-31):
> You just got lucky in the
On 30/05/2023 23.59, Cyril Brulebois wrote:
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
Andreas Beckmann (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
>
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
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
Hallo Andreas,
Cyril Brulebois (2023-05-27):
> Andreas Beckmann (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
Processing commands for cont...@bugs.debian.org:
> tags 1035499 bookworm-ignore
Bug #1035499 [crowdsec-custom-bouncer] crowdsec-custom-bouncer: fails to
install with --install-recommends: open /etc/crowdsec/config.yaml: no such file
or directory
Added tag(s) bookworm-ignore.
> user
tags 1035499 bookworm-ignore
user release.debian@packages.debian.org
usertag 1035499 bookworm-can-defer
Hi Cyril,
On 27-05-2023 10:18, Cyril Brulebois wrote:
At this point, I'd like to formally request a bookworm-ignore tag.
As agree, I'm marking this bug as such. Normally I'd only use
Hi,
Andreas Beckmann (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
Package: crowdsec-custom-bouncer
Version: 0.0.15-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
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
11 matches
Mail list logo
