Bug 2344333

+++ This bug was initially created as a clone of Bug #2344322 +++

Attempt to install systemd in registry.fedoraproject.org/fedora:rawhide container fails.


Reproducible: Always

Steps to Reproduce:
1. podman run --rm registry.fedoraproject.org/fedora:rawhide dnf install -y systemd

Actual Results:  
$ podman run --rm registry.fedoraproject.org/fedora:rawhide dnf install -y systemd
Updating and loading repositories:
 Fedora rawhide openh264 (From Cisco) - 100% |   5.8 KiB/s |   6.0 KiB |  00m01s
 Fedora - Rawhide - Developmental packa 100% |   6.1 MiB/s |  21.6 MiB |  00m04s
Repositories loaded.
Failed to resolve the transaction:
Problem: problem with installed package
  - installed package systemd-standalone-sysusers-257.2-17.fc42.x86_64 conflicts with systemd provided by systemd-257.2-17.fc42.i686 from rawhide
  - package systemd-257.2-17.fc42.i686 from rawhide conflicts with systemd-standalone-sysusers provided by systemd-standalone-sysusers-257.2-17.fc42.x86_64 from rawhide
  - conflicting requests
  - installed package systemd-standalone-sysusers-257.2-17.fc42.x86_64 conflicts with systemd provided by systemd-257.2-17.fc42.x86_64 from rawhide
  - package systemd-257.2-17.fc42.x86_64 from rawhide conflicts with systemd-standalone-sysusers provided by systemd-standalone-sysusers-257.2-17.fc42.x86_64 from rawhide
You can try to add to command line:
  --allowerasing to allow removing of installed packages to resolve problems
  --skip-broken to skip uninstallable packages


Expected Results:  
No error, systemd installed.

--- Additional comment from Zbigniew Jędrzejewski-Szmek on 2025-02-07 11:00:12 UTC ---

I'm not sure how exactly the rawhide image is put together, i.e. what packages are
*supposed* to be installed, but in general this not an error.

Apparently, systemd-standalone-sysusers is installed in the image.
To replace that with normal systemd, add --allowerasing.

If it is expect that the base image contains systemd, or that systemd can
be installed without --allowerasing, then I think you should report this against
the image definition. Please put me in CC if you do. I'm interesting in
understanding if there is a problem. But we don't track image definitions
in bugzilla.

--- Additional comment from Alexey Tikhonov on 2025-02-07 11:22:38 UTC ---

JFTR: we encounter this (or similar) issue both working with F42 and Rawhide containers:
```
    Problem: problem with installed package
      - installed package systemd-standalone-sysusers-257.2-17.fc42.x86_64 conflicts with systemd provided by systemd-257.2-17.fc42.i686 from fedora
      - package systemd-257.2-17.fc42.i686 from fedora conflicts with systemd-standalone-sysusers provided by systemd-standalone-sysusers-257.2-17.fc42.x86_64 from fedora
      - package openssh-server-9.9p1-7.fc42.x86_64 from fedora requires systemd, but none of the providers can be installed
      - installed package systemd-standalone-sysusers-257.2-17.fc42.x86_64 conflicts with systemd provided by systemd-257.2-17.fc42.x86_64 from fedora
      - package systemd-257.2-17.fc42.x86_64 from fedora conflicts with systemd-standalone-sysusers provided by systemd-standalone-sysusers-257.2-17.fc42.x86_64 from fedora
```

--- Additional comment from Zbigniew Jędrzejewski-Szmek on 2025-02-07 11:28:18 UTC ---

This is probably somehow related to the sysusers merge. Rpm gained a dependency
on /usr/bin/systemd-sysusers, which is provided by either systemd and systemd-standalone-sysusers,
and some image definitions were changed to prefer systemd-standalone-sysusers.
But the packaging itself is correct. The question of whether some image is suitable
for what you want to use it for cannot be answered here.

--- Additional comment from Jan Pazdziora on 2025-02-07 11:29:33 UTC ---

I fail to see why systemd / systemd-standalone-sysusers are packaged in such a way that upgrading from systemd-standalone-sysusers to full systemd is not supported without the nuclear option of --allowerasing.

IIRC, product Fedora Container Images and component base (https://bugzilla.redhat.com/buglist.cgi?classification=Fedora&component=base&product=Fedora%20Container%20Images) is where Fedora container images are tracked.