Your message dated Wed, 31 May 2023 18:48:52 +0000 with message-id <e1q4qso-00fkom...@fasolo.debian.org> and subject line Bug#1035499: fixed in crowdsec-custom-bouncer 0.0.15-3 has caused the Debian Bug report #1035499, regarding crowdsec-custom-bouncer: fails to install with --install-recommends: open /etc/crowdsec/config.yaml: no such file or directory to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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 severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package crowdsec. Preparing to unpack .../4-crowdsec_1.4.6-3+b1_i386.deb ... Unpacking crowdsec (1.4.6-3+b1) ... Selecting previously unselected package crowdsec-custom-bouncer. Preparing to unpack .../5-crowdsec-custom-bouncer_0.0.15-2+b1_i386.deb ... Unpacking crowdsec-custom-bouncer (0.0.15-2+b1) ... Setting up crowdsec-custom-bouncer (0.0.15-2+b1) ... [ESC][31mFATA[ESC][0m[03-05-2023 23:19:26] while reading yaml file: open /etc/crowdsec/config.yaml: no such file or directory dpkg: error processing package crowdsec-custom-bouncer (--configure): installed crowdsec-custom-bouncer package post-installation script subprocess returned error exit status 1 Setting up libsqlite3-0:i386 (3.40.1-2) ... Setting up libssl3:i386 (3.0.8-1) ... Setting up openssl (3.0.8-1) ... Setting up ca-certificates (20230311) ... Updating certificates in /etc/ssl/certs... 140 added, 0 removed; done. Setting up crowdsec (1.4.6-3+b1) ... I: Registering to LAPI (/etc/crowdsec/local_api_credentials.yaml) W: Missing /etc/machine-id, initializing I: Registering to CAPI (/etc/crowdsec/online_api_credentials.yaml) I: Setting up offline hub (see README.Debian) I: Enabling upstream-recommended items, first installation (via symlinks from /etc/crowdsec) I: Enabling WAL for SQLite [fstype=] (see README.Debian) Processing triggers for libc-bin (2.36-9) ... Processing triggers for ca-certificates (20230311) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Errors were encountered while processing: crowdsec-custom-bouncer Note that crowdsec gets configured after crowdsec-custom-bouncer in this case because there is only a Recommends. cheers, Andreascrowdsec-custom-bouncer_0.0.15-2+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---Source: crowdsec-custom-bouncer Source-Version: 0.0.15-3 Done: Cyril Brulebois <cy...@debamax.com> We believe that the bug you reported is fixed in the latest version of crowdsec-custom-bouncer, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cyril Brulebois <cy...@debamax.com> (supplier of updated crowdsec-custom-bouncer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Wed, 31 May 2023 19:01:19 +0200 Source: crowdsec-custom-bouncer Architecture: source Version: 0.0.15-3 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team <team+pkg...@tracker.debian.org> Changed-By: Cyril Brulebois <cy...@debamax.com> Closes: 1035499 Changes: crowdsec-custom-bouncer (0.0.15-3) unstable; urgency=medium . * Fix failure to install if crowdsec is unpacked but not configured (Closes: #1035499): - If both cscli and /etc/crowdsec/config.yaml exist, register as previously, via `cscli bouncers add`. - If cscli exists but /etc/crowdsec/config.yaml doesn't, create an API key similarly to what cscli would do (32 hexadecimal digits), and queue registration in /var/lib/crowdsec/pending-registration. * Add ConditionPathExists=!/var/lib/crowdsec/pending-registration to the systemd unit accordingly, so that it's skipped until crowdsec's postinst deals with the pending-registration file, removes it, and starts the units. * Use mode 600 when creating crowdsec-custom-bouncer.yaml.local, since it contains an API key. Checksums-Sha1: 86aa355c128667678f54ccc2bd35200264d7f385 2502 crowdsec-custom-bouncer_0.0.15-3.dsc c68cb6f6aab618e21e3c3b0bfd759c17d8738cf8 6524 crowdsec-custom-bouncer_0.0.15-3.debian.tar.xz 234d7bedc60df81bf16ecf67443cb9c6669e8de0 6660 crowdsec-custom-bouncer_0.0.15-3_source.buildinfo Checksums-Sha256: e25b9d611faef374a641c64450177da970d4c65c7514a779f7dc163f252c2e9e 2502 crowdsec-custom-bouncer_0.0.15-3.dsc 6f3aff3b4f86c3618f4bd2dad5030d7168deb471e734f02ae4a3dcb1032bbde6 6524 crowdsec-custom-bouncer_0.0.15-3.debian.tar.xz 8eac9f63eb0df504b681eeb39ae28ff855d3a722b5566ab3f60ca3d033a8141b 6660 crowdsec-custom-bouncer_0.0.15-3_source.buildinfo Files: 92bbb8f545b9aaa0b5a2a8143378c625 2502 golang optional crowdsec-custom-bouncer_0.0.15-3.dsc 43d231d57c5d401dfff4f2c3c8a7e622 6524 golang optional crowdsec-custom-bouncer_0.0.15-3.debian.tar.xz ed6595317545cfd48f925e9ff3e7770d 6660 golang optional crowdsec-custom-bouncer_0.0.15-3_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJEBAEBCgAuFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmR3fYIQHGtpYmlAZGVi aWFuLm9yZwAKCRD/kUrwwrNVILtTEACpo/SRXC+KLlYAoV96BPDO1NjPeelUCwZA Ab/4V1DLrzjpp7Oz36P9/1QF9Pi0nXmKz5OKo9o27ttyiXOnWzW/jou0w42UuYdC bqDU8CEWY+vC6IcAcQ7oNbkCP0i4linccWTeWHeAW8CM/U5XWlgLCWsPbJwS7rYj FDXso9B7FpSU3raZCyppJ3PMhX1roXa0fL0XPoIBUMHXS01IZt7WGPPj8wqjtljb WPz9pI3ksTEKRtoSf+ZYT1f6c7IBcZwLaLbRYlpgH+Kkeha5v8le79fTy66JVmPj V+83hi/Fjfasr4EmixvWieDF3mqwj5lhomiuFvgvONLRIgDe/pwZVSTwz9Pmfma4 Qr1DqnmkDZ3lkOCseNyMhbuadJ5R6pmoybxvxU0JRQlZQKII8YDoBFdHKDES5o9X bBPeyjePIKnXf/TDhn8YWfYNAUkKSDkgu4BqYO2x47V7ahYD6qZfmp5+mcNCBTGD Tpon3PLIhyKuzxpuOUnA4NdbkHBUokYPjadwW7NN6XlBI6O/vPD+SsDOm34vbHsj 4HJ1RbrLq3yvz7LA4sy3Zyj4fpBMT9sM94VJKDs3R4ErwRassSFWldezIlVqGRVL N++0gKhpZL1gHgroF0tnN7tBAwTMvcc/oLeQ0YVZCvZXvN3R616iJMMhf7+TkOKd xhLAFKdfBg== =e6l/ -----END PGP SIGNATURE-----
--- End Message ---