On 2026-01-29, Sune Vuorela <[email protected]> wrote: > On 2026-01-28, Sune Vuorela <[email protected]> wrote: >>>>> >>>>> ksmtp - LAST WEEK BEFORE REMOVAL >>>>> * https://invent.kde.org/pim/ksmtp/-/pipelines/1147459 >>>>> * https://invent.kde.org/pim/ksmtp/-/pipelines/1149245 (stable) >>>>> * Windows tests fail >>>>> >>>> >>>> SASL issue still seems to be persisting, don't suppose anyone from PIM can >>>> comment on what this is trying to do? >>> >>> I do wonder what has happened here - is sasl compiled without something >>> it was compiled with in the past? >> >> Maybe sasl is looking in the wrong place for the plugins ? >> >> - everything looks to be kind of reasonable compiled. But I'm not sure >> if it is (not) relocatable or if the LoadLibrrary calls fails or ... > > Everything is broken in sasl-land. > > The version bump in craft > (https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/5638977137104bc7bf1c495437b4c1185483b9a5) > > did 82 additions and 3035 deletions but the result is broken. > > It looks like their native build system doesn't support static plugins > (which we used in the past), the native build system seems to hardcode > the paths to plugins to > #define PLUGINDIR "C:\\CMU\\bin\\sasl2" > > and that's not where we install them (they go into BININSTALLDIR/sasl2) > > I hope we have someone who likes windows and C to go fix this, the > alternative is I guess to drop everything startitng from ksmtp on > windows.
Alternatively there seems to also be a solution file; maybe craft can be tricked to use that instead? /Sune
