4 ms·

The WITH_XC_NETWORKING build option is off by default so the developers have obviously intended this to be a valid build configuration.

• fallingsquirrel 2y ago
  Sure, but that doesn't change the fact that a point release suddenly broke everyone's workflows and is causing maintenance headaches. I don't think the technical minutia of how exactly things were broken is the issue. If Debian shipped a Linux kernel point release that disabled networking I think people would be similarly upset, even though it's also just a build option and intended to be a valid build configuration (and would even more secure!)
  • Dah00n 2y ago
    >If Debian shipped a Linux kernel point release that disabled networking That is not comparable. "If Debian shipped a Linux kernel point release that removed a risky networking plugin and some disabled-by-default plugins and made a -full version" that would be comparable.
    • MatthiasPortzel 2y ago
      It’s exactly comparable. The browser-autofill functionality in KeyPassXC is not a plug-in and it’s not risky. The person saying that is the Debian maintainer.
    • nulld3v 2y ago
      Hmm, excluding the comment about the missing "-full" version, I don't see how it is not comparable. There is nothing that makes the networking code in KeepassXC more "risky" compared to the networking code in Linux.
  • kasabali 2y ago
    > that doesn't change the fact that a point release suddenly broke everyone's workflows BS. This change was in Debian sid/testing. That's what it's for. Debian stable users' workflow hasn't been broken.