New comment by ap4y on void-packages repository

https://github.com/void-linux/void-packages/pull/25140#issuecomment-701151296

Comment:
Thanks  a lot for  the review @CameronNemo, really appreciate it. I wasn't aware of the issues with virtual packages and couldn't find related information in the manual or issues. I'm curious where a can read more about those before going with my original idea and rev bumping `podman` and `runc`.

I also had a chance to test a pure cgroupv2 mode (i.e. unified) and had some issues with rootless mode in `runc`, `crun` runs seems to be  getting the same error but it's ignored.  Haven't fully investigated this one.

```
ap4y » podman --runtime runc run --rm -ti alpine sh
Error: container_linux.go:370: starting container process caused: process_linux.go:326: applying cgroup configuration for process caused: mkdir /sys/fs/cgroup/libpod_parent: permission denied: OCI runtime permission denied error
ap4y » podman --runtime crun --log-level info run --rm -ti alpine sh
INFO[0000] podman filtering at log level info
WARN[0000] Error initializing configured OCI runtime kata: no valid executable found for OCI runtime kata: invalid argument
INFO[0000] Setting parallel job count to 37
WARN[0000] Failed to add conmon to cgroupfs sandbox cgroup: error creating cgroup path /libpod_parent/conmon: write /sys/fs/cgroup/cgroup.subtree_control: open /sys/fs/cgroup/cgroup.subtree_control: permission denied
INFO[0000] Got Conmon PID as 6067
/ #
ap4y » podman info
host:
  arch: amd64
  buildahVersion: 1.16.1
  cgroupVersion: v2
```

Since `crun` looks like a bit more stable option for cgroupv2 I think using `ignorepkg` might be a bit clunky solution.