** Description changed: - [ Rationale / Scope ] + [ Rationale ] The proprietary C++ Entra broker from Microsoft now expects a version being set in the IPC request that linux-entra-sso sends, but the current build does not set one as the build process takes it from git, which is not available at package build time. The older/deprecated proprietary java-based MSFT Entra broker, and the open source Himmelblau Entra broker, are not affected. - [ Impact ] + [ Impact / Scope ] The solution is a change to debian/rules to set an environment variable override that fixes the version to the source package version, bypassing the build system git tag parsing logic. The only runtime difference is that an actual version is included in the IPC, and the only package difference is that the version is stamped in the Python script instead of being an empty string. root@stonking:~# seeded-in-ubuntu linux-entra-sso linux-entra-sso's binaries are not seeded for stonking. [ Test Plan ] <WIP> [ Where problems could occur / Regression Potential ] <WIP> [ Other Info ] Original bug report text follows: Mirroring Debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1148245 The version currently in resolute multiverse doesn't seem to work at all. Luca fixed it in Debian sid following my bug report (version 1.11.0-1 has the fix). Please either update multiverse with the new version or backport the actual build system fix. (See the debian bug for all the details).
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2167899 Title: [FFE/SRU] linux-entra-sso: broken compatibility with new MSFT msalcpp broker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-entra-sso/+bug/2167899/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
