Arch Linux User Repository

I received error when attempting to run, resolved it by installing pyside2. Should it be added as a dependency?

Error message:

$ guiscrcpy
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/qtpy/__init__.py", line 210, in <module>
    from PySide import __version__ as PYSIDE_VERSION  # analysis:ignore
ModuleNotFoundError: No module named 'PySide'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/guiscrcpy", line 33, in <module>
    sys.exit(load_entry_point('guiscrcpy==4.11.2', 'console_scripts', 'guiscrcpy')())
  File "/usr/bin/guiscrcpy", line 25, in importlib_load_entry_point
    return next(matches).load()
  File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
    module = import_module(match.group('module'))
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 850, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/usr/lib/python3.9/site-packages/guiscrcpy/cli.py", line 9, in <module>
    from qtpy.QtWidgets import QApplication
  File "/usr/lib/python3.9/site-packages/qtpy/__init__.py", line 216, in <module>
    raise PythonQtError('No Qt bindings could be found')
qtpy.PythonQtError: No Qt bindings could be found

python-ruamel-yaml-0.17.16-1-any.pkg.tar.zst seems to be dependency that cannot be updated "The requested URL returned error: 404"

@yochananmarqos, @cgirard

I'm experiencing the same error when building in a clean chroot. I cannot really explain it either, but somehow the warning message (stderr) from python is used in the pkgver variable assignment, rather than the actual (stdout) output of python --version. Which is why pkgver() bails out.

Pre-computing pkgver with makepkg -od or the likes doesn't help here, because the pkgver() function is run despite this when building.

No idea why it's not the case outside of a chroot, but this happens with extra-x86_64-build as well as with the "classic" way (mkarchroot + makechrootpkg).

Anyways, sending the stderr stream to nirvana fixed this for me :

    python setup.py --version 2>/dev/null

This fixed chroot building and didn't harm building on the live system for me.

@cgirard: I can't explain it. Chroot or no chroot, all one has to do is run makepkg -od to generate the pkgver.

@yochananmarqos: So how do you explain it is failing for me, in a clean chroot?

Having a problem reinstalling from a backup. I tried to install from the aur as my restored backup system doesn't seem to have guiscrcpy installed. Unfortunately, there's a problem with verifying the keys, I think? Is there a file somewhere on my system I need to delete so that it can re-generate a new one?

.gnupg': File exists -> problem importing keys

""

==> Import? [Y/n] :: Importing keys with gpg... gpg: Fatal: can't create directory '/home/$USER/.gnupg': File exists -> problem importing keys

$ yay -S guiscrcpy :: There are 2 providers available for guiscrcpy: :: Repository AUR 1) guiscrcpy 2) guiscrcpy-git

Enter a number (default=1): :: Checking for conflicts... :: Checking for inner conflicts... [Aur:1] guiscrcpy-4.10.0-1

1 guiscrcpy (Build Files Exist) ==> Packages to cleanBuild? ==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4) ==> No :: Deleting (1/1): /home/peterwest/.cache/yay/guiscrcpy :: (1/1) Downloaded PKGBUILD: guiscrcpy 1 guiscrcpy (Build Files Exist) ==> Diffs to show? ==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4) ==> n :: (1/1) Parsing SRCINFO: guiscrcpy

:: PGP keys need importing: -> 7427D25413635E1E39657B6B1007816766D390D7, required by: guiscrcpy ==> Import? [Y/n] y :: Importing keys with gpg... gpg: Fatal: can't create directory '/home/$USER/.gnupg': File exists -> problem importing keys

""

@cgirard: No, it's not.

==> Starting pkgver()...
/usr/lib/python3.9/site-packages/setuptools/dist.py:484: UserWarning: Normalizing 'v4.10.0' to '4.10.0'
  warnings.warn(tmpl.format(**locals()))

Hi, Your pkgver seems to be broken:

==> Starting pkgver()...
==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: /usr/lib/python3.9/site-packages/setuptools/dist.py:484: UserWarning: Normalizing 'v4.10.0' to '4.10.0'
  warnings.warn(tmpl.format(**locals()))
4.10.0

Not sure why it is even needed on a non-VCS PKGBUILD.

@alive: There's nothing wrong with the developer's key. gnupg 2.2.29 now uses keyserver.ubuntu.com. Check your ~/.gnupg/gpg.conf.

Hi, because the SKS servers are down indefinitely, nobody new is able to import the 7427D25413635E1E39657B6B1007816766D390D7 key. Please host your public key on a different keyserver.