lejeczek

Hi.

A bit of feedback.

→ $ dnf -y copr enable rhcontainerbot/podman-next centos-stream+epel-next
→ $ dnf update
…
Downloading Packages:
[SKIPPED] containers-common-extra-1-90.el8.noarch.rpm: Already downloaded
[SKIPPED] podman-gvproxy-4.6.0~dev-1.20230530123955908317.main.609.g0ab95af37.el8.x86_64.rpm: Already downloaded
[SKIPPED] catatonit-0.1.7-7.el9.x86_64.rpm: Already downloaded
[SKIPPED] aardvark-dns-1.7.0~dev-1.20230530095610093461.main.36.gcd45bae.el8.x86_64.rpm: Already downloaded
[SKIPPED] container-selinux-2.210.0-1.20230414192129918782.main.1.g36709f0.el8.noarch.rpm: Already downloaded
[SKIPPED] containers-common-1-90.el8.noarch.rpm: Already downloaded
[SKIPPED] crun-0.0-20230526001803.e398b24.el8.x86_64.rpm: Already downloaded
[SKIPPED] netavark-1.7.0~dev-1.20230530100010313200.main.52.g1234384.el8.x86_64.rpm: Already downloaded
[SKIPPED] podman-4.6.0~dev-1.20230530123955908317.main.609.g0ab95af37.el8.x86_64.rpm: Already downloaded
[SKIPPED] skopeo-1.12.1~dev-1.20230519025134889929.main.25.gcf502780.el8.x86_64.rpm: Already downloaded
[SKIPPED] slirp4netns-1.2.0-10.el8.x86_64.rpm: Already downloaded
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘dnf clean packages’.
Error: Transaction test error:
file /usr/share/man/man8/container_selinux.8.gz from install of container-selinux-101:2.210.0-1.20230414192129918782.main.1.g36709f0.el8.noarch conflicts with file from package selinux-policy-doc-38.1.13-1.el9.noarch

thanks, L.

lsm5 Packaging Team

Hi @lejeczek , do you still see this? The file has been commented out from the spec.

thm Packaging Team

On Rocky 9.3, I see this:

 Problem 1: cannot install the best update candidate for package container-selinux-3:2.221.0-1.el9.noarch
  - nothing provides selinux-policy >= 38.1.33-1.el9 needed by container-selinux-102:2.230.0-1.20240302184335236362.main.0.g5cec853.el9.noarch from copr:copr.fedorainfracloud.org:rhcontainerbot:podman-next
  - nothing provides selinux-policy-base >= 38.1.33-1.el9 needed by container-selinux-102:2.230.0-1.20240302184335236362.main.0.g5cec853.el9.noarch from copr:copr.fedorainfracloud.org:rhcontainerbot:podman-next
  - nothing provides selinux-policy-targeted >= 38.1.33-1.el9 needed by container-selinux-102:2.230.0-1.20240302184335236362.main.0.g5cec853.el9.noarch from copr:copr.fedorainfracloud.org:rhcontainerbot:podman-next
 Problem 2: cannot install the best update candidate for package skopeo-102:1.14.1-1.20240208232627607756.main.27.gde7e8dbf.el9.x86_64
  - nothing provides libdevmapper.so.1.02(DM_1_02_197)(64bit) needed by skopeo-102:1.14.1-1.20240301193333510611.main.41.g4a35c66c.el9.x86_64 from copr:copr.fedorainfracloud.org:rhcontainerbot:podman-next

Is this to be expected?

1 reply

lsm5 Packaging Team

@thm sorry only seeing your comment now. I’m unable to reproduce this on a RHEL 9.3 container. Are you still seeing this?

thm Packaging Team

Yes, this is still a problem:

# dnf upgrade
Last metadata expiration check: 0:03:41 ago on Wed May  8 16:04:17 2024.
Error: 
 Problem: cannot install the best update candidate for package container-selinux-3:2.221.0-1.el9.noarch
  - nothing provides selinux-policy >= 38.1.35-2.el9 needed by container-selinux-102:2.231.0-1.20240426153701694453.main.3.ga3cba5e.el9.noarch from copr:copr.fedorainfracloud.org:rhcontainerbot:podman-next
  - nothing provides selinux-policy-base >= 38.1.35-2.el9 needed by container-selinux-102:2.231.0-1.20240426153701694453.main.3.ga3cba5e.el9.noarch from copr:copr.fedorainfracloud.org:rhcontainerbot:podman-next
  - nothing provides selinux-policy-targeted >= 38.1.35-2.el9 needed by container-selinux-102:2.231.0-1.20240426153701694453.main.3.ga3cba5e.el9.noarch from copr:copr.fedorainfracloud.org:rhcontainerbot:podman-next
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Where would I get selinux-policy >= 38.1.35-2.el9?

1 reply

thm Packaging Team

Seems I missed to enable a repo. But with release of 9.4 the problem vanished anyway, at least for now.