Package Details: system76-driver 20.04.94-1

Git Clone URL: https://aur.archlinux.org/system76-driver.git (read-only, click to copy)
Package Base: system76-driver
Description: Universal driver for System76 computers
Upstream URL: https://github.com/pop-os/system76-driver
Licenses: GPL-2.0-or-later
Submitter: ava1ar
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 23
Popularity: 0.000111
First Submitted: 2013-08-18 05:41 (UTC)
Last Updated: 2024-08-17 15:39 (UTC)

Dependencies (36)

Required by (0)

Sources (3)

Latest Comments

1 2 3 4 5 6 .. 17 Next › Last »

yochananmarqos commented on 2024-08-19 21:12 (UTC) (edited on 2024-08-19 21:13 (UTC) by yochananmarqos)

@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.

nameless commented on 2024-08-19 20:51 (UTC)

@yochananmarqos: Thanks for the correction. There's both a warning and an error. I should have been clearer that I had both.

The error I'm referring to is this one: ERROR system76driver/tests/test_gtk.py - ValueError: Namespace Gtk is already loaded with version 4.0. It's in the installation log output. It seems to only affect the tests.

yochananmarqos commented on 2024-08-19 19:26 (UTC)

@nameless: It's warning, not an error. The build completes in a clean chroot.

The warning is valid, however it doesn't really make any difference. If you know Python and Gtk well enough to create a comprehensive upstream issue, feel free.

nameless commented on 2024-08-19 18:56 (UTC) (edited on 2024-08-19 18:58 (UTC) by nameless)

I ran into an error in check(). It does look like the package builds, but there are failing tests. Should this be reported upstream?

Installation Log 
==> Starting build()...
* Getting build dependencies for wheel...
/usr/lib/python3.12/site-packages/setuptools/dist.py:318: InformationOnly: Normalizing '20.04.94' to '20.4.94'
  self.metadata.version = self._normalize_version(self.metadata.version)
* Building wheel...
/usr/lib/python3.12/site-packages/setuptools/dist.py:318: InformationOnly: Normalizing '20.04.94' to '20.4.94'
  self.metadata.version = self._normalize_version(self.metadata.version)
Successfully built system76driver-20.4.94-py3-none-any.whl
==> Starting check()...
======================================================== test session starts =========================================================
platform linux -- Python 3.12.4, pytest-8.3.2, pluggy-1.5.0
rootdir: /home/gxd/.cache/paru/clone/system76-driver/src/system76-driver
plugins: typeguard-4.3.0
collected 109 items / 1 error                                                                                                        

=============================================================== ERRORS ===============================================================
_________________________________________ ERROR collecting system76driver/tests/test_gtk.py __________________________________________
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
========================================================== warnings summary ==========================================================
system76driver/tests/test_gtk.py:28
  /home/gxd/.cache/paru/clone/system76-driver/src/system76-driver/system76driver/tests/test_gtk.py:28: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '4.0') before import to ensure that the right version gets loaded.
    from gi.repository import Gtk

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
====================================================== short test summary info =======================================================
ERROR system76driver/tests/test_gtk.py - ValueError: Namespace Gtk is already loaded with version 4.0
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
==================================================== 1 warning, 1 error in 0.67s =====================================================
==> Entering fakeroot environment...
==> Starting package()...

zo0M commented on 2024-05-08 04:21 (UTC) (edited on 2024-05-08 04:22 (UTC) by zo0M)

I get an error during the update:

Installation log 
Preparing...
Synchronizing package databases...
Refreshing AUR...
Cloning system76-driver build files...
Generating system76-driver information...
Checking system76-driver dependencies...
Resolving dependencies...
Checking inter-conflicts...

Building system76-driver...
==> Making package: system76-driver 20.04.89-1 (Wed 08 May 2024 07:15:38 AM EEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating system76-driver git repo...
  -> Found cli.patch
  -> Found wayland.patch
  -> Found actions.patch
==> Validating source files with sha256sums...
    system76-driver ... NOT FOUND
    cli.patch ... Passed
    wayland.patch ... Passed
    actions.patch ... Passed
==> ERROR: One or more files did not pass the validity check!
Failed to build system76-driver

nikogura commented on 2023-05-30 20:39 (UTC)

False alarm. A fully clean build succeeds.

sr98vn commented on 2023-02-20 21:43 (UTC)

@Parker8283 Can confirm that python-setuptools version 67.3.2 (recently updated) allows system76-driver to build now, thanks!

Parker8283 commented on 2023-02-20 01:53 (UTC)

Downgrading python-setuptools 67.3.0 --> 67.2.0 worked for me, the package builds now. Found the real issue/PR: SetupTools #3823. This was released in 67.3.1. Looks like 67.3.2 is in testing currently, so once that moves to extra, it should build fine.

Eeems commented on 2023-02-19 01:28 (UTC)

@Parker8283 and @sr98vn this could be related to the issue with setuptools that @Parker8283 identified. That said, I've been having this package build daily with no issue, and it's using python-setuptools 1:67.3.0-1 https://github.com/Eeems/repo.eeems.codes/actions/runs/4208706435/jobs/7305093989#step:9:77

If you just need an updated build of the package for now, you can get the package from my repo if you trust my build mechanism. You can also try building it yourself with the container that I'm building with. You can find the Dockerfiles here: https://github.com/Eeems/images

1 2 3 4 5 6 .. 17 Next › Last »