Fun with xmlsec pinned package

[CapnKernel]

And by fun, I mean pain.

I'm continuing to work on the bare metal install instructions (plus flow-on changes to other docs), but running into a problem.

The docs I'm working on are on the mainmaster branch, and so the xmlsec package in src/backend/requirements.in (and hence src/backend/requirements.txt is pinned to 1.3.17. However a change I've made to the bare metal instructions is to get the user to clone from the stable branch. In that branch, xmlsec is pinned to 1.3.14.

The problem comes when I'm testing out bare metal installs on what I use locally, which is Fedora. There's no wheel to fetch, so pip tries to build the wheel locally. This fails initially because there's no xmlsec1 binary, but even after I install xmlsec1-devel, building fails with a compilation error.

I note this problem doesn't seem to happen on Ubuntu. I also note that xmlsec has been causing you pain too (#9713).

Does xmlsec still need to be pinned to 1.3.14 in the stable branch?

[SchrodingersGat]

Not sure about that, we would have to try to run off a stable branch with a newer xmlsec lib. However keep in mind that any major changes to the docs will be targeting the next stable release, which is based of current "master" - if that makes sense

[CapnKernel]

Oh I see. When people see my changes, stable will have been moved up to be today's master or beyond, which is pinned to 1.3.17. All good! Thanks for explaining!