Draft: systemd/systemd: enabled homed

changed target branch from master to master_staging_systemd

changed the description

added 207 commits

f95fab77...cd7ea0b1 - 204 commits from branch postmarketOS:master_staging_systemd
fdfea553 - systemd/systemd: fix typo in arch reasoning
9e006c37 - systemd/systemd-services: add nsss daemon service
e9b0fc79 - systemd/systemd: enable systemd-homed

Compare with previous version

changed the description

added 1 commit

4c04451f - systemd/systemd: enable systemd-homed

Compare with previous version

~~Partially depends on ~~~~https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/76177~~~~ for the user/group to be satisfied for the systemd nsss service.~~ Rejected because Alpine isn't switching to nsss currently. Still got the update through so that is good.

Bummer. I assumed such a response from upstream, but never actually tried it. I think we should either persue patching musl to support nss directly, getting musl's fallback nscd working or patching musl for nsss integration locally. As some codepaths in systemd check wheter the NSS module is currently opened (as lookups can otherwise happen), I think the first option has besser results for now.

I would honestly like a user-querying interface from systemd for libc that doesn't require random modules at runtime. https://systemd.io/USER_GROUP_API/

I also don't have the energy to persue this topic further, it's all yours ;3

An issue I have found with nsss is that it isn't fully compatible with nss because of some sort of code purity thing? I don't understand fully but I have been working in the background on gluing the two together so I don't have to patch systemd.

I would love to get musl to support nss, but I doubt it because they said they wouldn't support it. I think the best bet for that would be to revive https://github.com/pikhq/musl-nscd.

added status::mr-stale label

Sorry to bother you @JustSoup321,

but we've detected that this merge request hasn't seen any recent activity. If you need help, want to discuss your approach with developers, or you are all done and this is waiting for review, you can ping @postmarketOS. You can also ask on matrix in #devel:postmarketos.org or #postmarketos-devel on OFTC.

Thanks for your contribution.