Bug 2218362 - selinux-policy-doc and container-selinux.8 manpage ownership
Summary: selinux-policy-doc and container-selinux.8 manpage ownership
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: selinux-policy
Version: 8.8
Hardware: Unspecified
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Zdenek Pytela
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On: 2209120
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-28 20:41 UTC by Zdenek Pytela
Modified: 2023-07-11 07:48 UTC (History)
9 users (show)

Fixed In Version: selinux-policy-3.14.3-123.el8
Doc Type: No Doc Update
Doc Text:
Clone Of: 2209120
Environment:
Last Closed:
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-161141 0 None None None 2023-06-28 20:44:06 UTC

Description Zdenek Pytela 2023-06-28 20:41:14 UTC
+++ This bug was initially created as a clone of Bug #2209120 +++

The container_selinux.8 manpage is a part of upstream container-selinux and imho best owned by the container-selinux package.

I think it should be removed from selinux-policy-doc.

Reproducible: Didn't try

--- Additional comment from Lokesh Mandvekar on 2023-05-22 20:01:17 CEST ---

PTAL https://src.fedoraproject.org/rpms/selinux-policy/pull-request/340#

--- Additional comment from Lokesh Mandvekar on 2023-06-27 19:32:16 CEST ---

Thanks Zdenek, did this get fixed in 38.18? Any idea when it will land in fedora 38, 37 and also CentOS Stream 8,9 ?

We're now handling container-selinux via packit and we also manage a `podman-next` copr with centos stream envs, that's why I ask about all distro versions.

--- Additional comment from Zdenek Pytela on 2023-06-27 20:08:16 CEST ---

(In reply to Lokesh Mandvekar from comment #2)
> Thanks Zdenek, did this get fixed in 38.18? Any idea when it will land in
> fedora 38, 37 and also CentOS Stream 8,9 ?
> 
> We're now handling container-selinux via packit and we also manage a
> `podman-next` copr with centos stream envs, that's why I ask about all
> distro versions.

Actually selinux-policy-38.17-1.fc38.noarch as announced in
https://src.fedoraproject.org/rpms/selinux-policy/pull-request/340#comment-146092

If you need it i F37, I can do that too, but build was not planned soon, so let me know.

--- Additional comment from Lokesh Mandvekar on 2023-06-27 20:30:20 CEST ---

(In reply to Zdenek Pytela from comment #3)
> (In reply to Lokesh Mandvekar from comment #2)
> > Thanks Zdenek, did this get fixed in 38.18? Any idea when it will land in
> > fedora 38, 37 and also CentOS Stream 8,9 ?
> > 
> > We're now handling container-selinux via packit and we also manage a
> > `podman-next` copr with centos stream envs, that's why I ask about all
> > distro versions.
> 
> Actually selinux-policy-38.17-1.fc38.noarch as announced in
> https://src.fedoraproject.org/rpms/selinux-policy/pull-request/340#comment-
> 146092
> 
> If you need it i F37, I can do that too, but build was not planned soon, so
> let me know.

Would be great if you could, thanks! Also, how about centos stream ETA?

--- Additional comment from Zdenek Pytela on 2023-06-28 08:45:04 CEST ---

(In reply to Lokesh Mandvekar from comment #4)
> (In reply to Zdenek Pytela from comment #3)
> > (In reply to Lokesh Mandvekar from comment #2)
> > > Thanks Zdenek, did this get fixed in 38.18? Any idea when it will land in
> > > fedora 38, 37 and also CentOS Stream 8,9 ?
> > > 
> > > We're now handling container-selinux via packit and we also manage a
> > > `podman-next` copr with centos stream envs, that's why I ask about all
> > > distro versions.
> > 
> > Actually selinux-policy-38.17-1.fc38.noarch as announced in
> > https://src.fedoraproject.org/rpms/selinux-policy/pull-request/340#comment-
> > 146092
> > 
> > If you need it i F37, I can do that too, but build was not planned soon, so
> > let me know.
> 
> Would be great if you could, thanks! Also, how about centos stream ETA?

We need a bz both for RHEL 8 and RHEL 9 if this is required.


Note You need to log in before you can comment on or make changes to this bug.