Thank you, I appreciate it!

@Parker8283: You guessed the reason, indeed. You make a valid point, I'll switch the dependency back.

Is there a reason that the system76-firmware-daemon dependency was changed to force system76-firmware-git? It looks like maybe for panp16 support, but for those who don't use that model, it seems like it shouldn't be required? The system76-firmware-daemon dependency would have already allowed the installation of system76-firmware-git for those that need it, and that seems like something that could be put in a Wiki page for the people that need it for the time being.

@raxod502: Thanks, fixed.

@aujxn: The tests pass in a clean chroot. Either way, I've relaxed the test so it won't stop on failure.

@yochananmarqos Even with 'not test_gtk' in the pkgbuild it still tries to run the test and fails for me

The program is crashing when opened with the error

Traceback (most recent call last):
  File "/usr/bin/system76-driver", line 28, in <module>
    import system76driver
ModuleNotFoundError: No module named 'system76driver'

The Gtk 4.0 check seems to be a hard error now.

system76driver/tests/test_gtk.py:32: in <module>
    from system76driver import gtk
system76driver/gtk.py:29: in <module>
    gi.require_version('Gtk', '3.0')
/usr/lib/python3.12/site-packages/gi/__init__.py:113: in require_version
    raise ValueError('Namespace %s is already loaded with version %s' %
E   ValueError: Namespace Gtk is already loaded with version 4.0

==> ERROR: A failure occurred in check().
    Aborting...
error: failed to build 'system76-driver-20.04.100-1':
error: packages failed to build: system76-driver-20.04.100-1

@nameless: I see. Gtk4 is not required by this package, therefore the tests get confused about it being present.

Either way, the tests failing will not stop the package from building.

EDIT: I made edits.