Bug#1063653: anope: Please ship new upstream version
Please update this package to 2.0.15 (not 2.1.3, thats the dev branch) asap. The currently shipped version contains a few security issues which should be addressed sooner rather than later. ~ Sadie
Bug#1000019: anope: depends on obsolete pcre3 library
If you update your package to 2.0.12 you can switch your build system to use m_regex_pcre2 instead of m_regex_pcre which should fix this issue. Hope this helps, ~ Sadie
Bug#1000104: inspircd: depends on obsolete pcre3 library
As multiple distributions want to get rid of the old version of PCRE I have decided to import m_regex_pcre2 from inspircd-contrib. As of the next release (which will be happening on the 30th of this month) you'll be able to enable it the same way you enable m_regex_pcre. Hope this helps, ~ Sadie
Bug#1000104: inspircd: depends on obsolete pcre3 library
If you want to fix this on InspIRCd v3 there is a backported module in inspircd-contrib for PCRE2 which can be installed with `./modulemanager install m_regex_pcre2`. This module uses the same internal name so it can be used on the same network as a server using m_regex_pcre. Alternately, you can just ship a different regex backend instead. I'd personally recommend m_regex_stdlib as that requires no dependencies other than a C++11 compiler. ~ Sadie
Bug#955479: InspIRCd package AppArmor issues
It seems like Debian are not shipping the AppArmor file that the InspIRCd build system generates and instead are shipping an incomplete custom one. This problem can be fixed by using the AppArmor file that InspIRCd generates and installs to the script directory (named "apparmor").
Bug#994816: Please update your package to Anope 2.0.10
Package: anope Version: 2.0.9-1 The version you are shipping is out of date. Now your freeze for the Bullseye release is over can you update it in Bookworm/Sid? Thanks, ~Sadie
Bug#994813: Please update your package to InspIRCd 3.11.0
Package: inspircd Version: 3.8.1-2 The version you are shipping is almost a year out of date. Now your freeze for the Bullseye release is over can you update it in Bookworm/Sid? Thanks, ~Sadie
Bug#981009: Charybdis abandoned upstream, do not ship in bullseye
Charybdis' development was terminated due to (among other reasons) threats by a former maintainer. It probably won't be revived. It's successor is probably Solanum (https://github.com/solanum-ircd/solanum) which is a fork that is led by freenode and OFTC people some of whom were contributors to Charybdis. It might be a good idea to package that instead when it gets a release? ~ Sadie
Bug#960650: [SECURITY] Please update to v3.6.0
InspIRCd 3.7.0 is now out and this security bug remains unfixed. Please update as soon as possible. Thanks, ~Sadie
Bug#960650: [SECURITY] Please update to v3.6.0
Package: inspircd Version: 3.4.0-2 InspIRCd v3.6.0 was recently released with a security fix for a crash bug. https://docs.inspircd.org/security/2020-01/ Please can you update your package to this version. Thanks, ~ Sadie
Bug#951339: Debian changes to InspIRCd causes errors when loading the httpd module
Package: inspircd Version: 3.4.0-2 Hello, We have received reports that users of your package are experiencing errors caused by Debian patching the httpd module to not use the vendored version of the http_parser library. Having had a look at the patch (debian.use-http-parser-lib.patch) it seems like your patch is forgetting to link against the library so the module is compiling but failing at runtime. Ideally the fix for this should be to just remove this patch. We only test against the vendored version and there's no guarantee we won't make changes to the vendored libraries which make them incompatible with the mainline version. It's only a tiny library with no external dependencies so this isn't harmful at all. Regards, ~ Sadie
