The problem is linkage - pam_loginkit links against libsystemd-login, but the LoginKit and systemd ones have the same soname.

It should NOT be an issue as long as the package is built using standard debian methods, as it will use the "local source" compiled one. Anyway, as in another issue i suggested to change the soname, this is even more not an issue

Got it - I'll remove everything except the *-dev ones. Legit?

I think even -dev isn't needed in build conflicts. The package will build against the headers it will have in the source tree, not the one in the system, so, it should use the right one provided by loginkit even if the one provided from systemd is installed, so, it should not be an issue to have the -dev installed from systemd.

Even if my assumption is wrong, libloginkit implement a subset of the api of libsystemd, right? so, the part of the api implemented are the same, isn't it? If my assumtions here are right, even compiling against the wrong headers should not be an issue as long the linkage will be on the right library at runtime, as they expose the same api ( a subset for loginkit, but all the api needed by , for example, GDM are the same ).

Yes, you're right. It's a subset.

Status changed to closed