Runtime dependencies are still missing:
❯ sudo dnf install ~/Downloads/python3-tmuxp-1.9.2-3.el8.noarch.rpm
Last metadata expiration check: 0:14:18 ago on Wed 26 Jan 2022 02:50:28 PM PST.
Error:
Problem: conflicting requests
- nothing provides python3.6dist(click) >= 7 needed by python3-tmuxp-1.9.2-3.el8.noarch
- nothing provides python3.6dist(kaptan) >= 0.5.10 needed by python3-tmuxp-1.9.2-3.el8.noarch
- nothing provides python3.6dist(libtmux) >= 0.10.1 needed by python3-tmuxp-1.9.2-3.el8.noarch
- nothing provides python3.6dist(libtmux) < 0.11 needed by python3-tmuxp-1.9.2-3.el8.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Tested on distrobox, works fine
Testing inside c8s within distrobox, 'mr help' throws a warning before showing the manpage, but is otherwise fine:
$ mr help
"/tmp/W7Dq0NLQSE" may be a binary file. See it anyway?
I'm hit by this issue when first trying distrobox enter
: https://github.com/containers/podman/issues/11255
~
❯ podman logs -f f35
Error: using --follow with the journald --log-driver but without the journald --events-backend (file) is not supported
~
❯ podman logs -f debian-packaging
Error: using --follow with the journald --log-driver but without the journald --events-backend (file) is not supported
The solution in the podman issue works, creating this file:
❯ cat /etc/containers/containers.conf
# distrobox via podman needs this
# see https://github.com/containers/podman/issues/11255
[engine]
events_logger = "journald"
It might be worth filing a bug for both podman in RHEL 8 and in RHEL 9, since per the tracker it's affecting RHEL 9 too - and either ship a README documenting the workaround and possibly get it documented upstream in https://github.com/89luca89/distrobox/blob/main/docs/compatibility.md too
Tested with CentOS and Debian containers, works fine
Works fine, tested initializing and entering CentOS Stream 9 and Debian
oh wow thank you!
due to https://github.com/nextcloud/desktop/issues/4141, not pushing to stable yet
@nonamedotc ack, I've disabled auto-push to stable
@carlwgeorge you're right, not sure how this happened, this is meant for EPEL9-next.