Martin Pitt

> rpm-ostree groupinstall Hardware-Support Gives me error: Unknown command 'groupinstall' But if something like that works, you can do by yourself then, it's an overlay.

@darch7 : I reverted the lxterminal → alacritty change. I just tried the latter, and it's just too broken. No working mouse copy&paste, colors in mutt etc. look weird, bash...

I was still working on #131, but there's really no urgency to that. I released [0.28.0](https://github.com/martinpitt/python-dbusmock/releases/tag/0.28.0), it's also on PyPI. Fedora and Debian updates are coming.

That seems fine to me. I just really wonder how you use that in upower, I [left a question there](https://github.com/GNOME/glib/commit/96a8c02d240d7c9ae366c63771291413384bdfb7#r54773831). FTR, I'm on PTO until Aug 25 with no access...

I tried this patch: ```diff diff --git dbusmock/testcase.py dbusmock/testcase.py index 6fb81d6..9814b8e 100644 --- dbusmock/testcase.py +++ dbusmock/testcase.py @@ -21,6 +21,8 @@ from typing import Tuple, Dict, Any import dbus +from gi.repository...

Right now you can do this on the CLI, as [described in README](https://github.com/martinpitt/python-dbusmock#simple-example-from-shell): sudo systemctl stop upower sudo python3 -m dbusmock -t upower Then `upower --dump` shows the mocked devices,...

The `systemctl stop upower` is actually not necessary, as dbusmock.py uses `allow_replacement=True` and `replace_existing=True`. You can also specify parameters in JSON form with `-p`. Once stopping the mock, D-Bus activation...

The [D-Bus specification](https://dbus.freedesktop.org/doc/dbus-specification.html) just has "signals"; they all get emitted somewhere (that's the point of them), and otherwise behave pretty much like a method call without a return call/value. What...

This now [breaks Fedora 36 builds](https://bugzilla.redhat.com/show_bug.cgi?id=2115999) due to the filesystem package [using lua in posttrans](https://src.fedoraproject.org/rpms/filesystem/c/47d37ac94192f792df5ed0faa15e78daa6644758). Does anyone know some workaround? Like, can we tell `rpm-ostree build` to simply ignore these...

This gave me headaches as well. I just filed issue #1296 with a proposal to make this Just Work and more elegant.