circular dependency between systemd and linux-pam(-pmos)

When both packages are outdated in the binary repo, there's a circular dependency that prevents building either of them. This was noticed when !5976 (merged) and !5971 (merged) were merged basically at the same time and bpo became deadlocked (it was worked around in !6001 (merged), but this is not an ideal solution for obvious reasons)

@jane400 mentioned adding some linux-pam-pmos0 package that systemd could depend on but I'm not sure how this would actually be implemented. Maybe @ollieparanoid has some ideas since this is a "bootstrap thing"

changed milestone to %initial systemd support

mentioned in merge request !6001 (merged)

Looked briefly into it (currently heavily focused on finishing up build.postmarketos.org#140 (closed)).

The current situation is:

• x86_64 is not deadlocked anymore
• aarch64 and armv7 apparently don't have a linux-pam-pmos package yet, so they are deadlocked currently.

I can look into making bpo just pick one of the two packages if they are deadlocked, as the assumption is that they build fine once we are past the repo_bootstrap stage once I'm done with build.postmarketos.org#140 (closed) and have the systemd repo merged into master, that is currently my highest priority.

With the current situation: For packages A, B that depend on each other, as long as we only merge changes to A or B and wait until they are built, before merging a change to the other one, it should work. (But I realize how inconvenient and prone to mistakes that is, it should be fixed in bpo.)

Adding a stage0 workaround package in the meantime could work, but not sure if it is worth the effort... I hope to be able to finish up build.postmarketos.org#140 (closed) in a few days so systemd is merged into master.

assigned to @ollieparanoid

this should get it unstuck for now:

• get systemd to the last version that is available for armv7/aarch
• wait until linux-pam-pmos is built and published (should be unstuck now)
• bump systemd again

thanks for your help, I'll go through this process now

sorry for the mess.

seems like the only executable (not so libs) that depends on libsystemd is pam_timestamp_check.

with some sh magic i also found pam_timestamp.so, pam_issue.so

mentioned in merge request !6025 (merged)

closed

mentioned in issue #3604