Comments

665 Comments

Tested on distrobox, works fine

BZ#1981552 Please branch and build myrepos for EPEL8

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?
BZ#1981552 Please branch and build myrepos for EPEL8

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

karma

Tested with CentOS and Debian containers, works fine

BZ#2034246 Review Request: distrobox - Another tool for containerized command line environments on Linux

Works fine, tested initializing and entering CentOS Stream 9 and Debian

BZ#2034246 Review Request: distrobox - Another tool for containerized command line environments on Linux
Test Case distrobox basic

oh wow thank you!

BZ#2010704 Branch rubygem-asciidoctor and build for EPEL 9

@nonamedotc ack, I've disabled auto-push to stable

@carlwgeorge you're right, not sure how this happened, this is meant for EPEL9-next.

BZ#2031995 Branch and build dumpet for EPEL 9
BZ#2031996 Branch and build livecd-tools for EPEL 9
BZ#2032836 Please branch and build appliance-tools in epel9
karma

Works fine. Note that I can update enlightenment separately from efl, and that causes issues - enlightenment would start fine on a fresh account, prompted customizations, then displays a full screen error message. So - possible improvement, maybe require a specific version of EFL in the enlightenment spec?

BZ#2035644 efl-1.26.0 is available
BZ#2035645 enlightenment-0.25.0 is available
BZ#2036539 efl-1.26.1 is available
BZ#2036540 enlightenment-0.25.1 is available
BZ#2034692 Please branch and build python-progressbar2 in epel9
BZ#2032239 Branch and build appx-util in epel9
BZ#2032216 Branch and build python-docopt in epel9