On Tue, Sep 01, 2026 at 09:51:01PM +0200, Håvard F. Aasen wrote: > I saw that something was off, but I didn't think it was this. I can > remove libbluetooth-dev if that is better solution, it's optional for > utils.
Generally, we prefer Debian packages to enable functionality that they can. Bootstrapping is a necessity, but it's the main driver of our packaging decisions. I'd like to leave this at your discretion. > I can also add your patch if you prefer. Either way works equally fine for bootstrapping. Those builds already have to turn on the nopython build profile. Enabling another profile is not a burden to bootstrapping. The main burden to libcap-ng maintenance is that these profiles need to work with future changes. If they cease doing so, the most likely outcome is that I send a patch. I spent a brief look at the autopkgtest failures. python3-defaults is in the process of dropping Python 3.13 as a supported version, but this hasn't migrated to forky yet. So when libcap-ng is built in sid (without 3.13) and then tested in forky (with 3.13), the test fails importing the module. This issue should resolve itself once python3-defaults migrates. The heimdal regression is not as obvious. Helmut
