Package Details: swaylock-fprintd-git r314.ffd639a-2

Git Clone URL: https://aur.archlinux.org/swaylock-fprintd-git.git (read-only, click to copy)
Package Base: swaylock-fprintd-git
Description: Screen locker for Wayland with integrated fingerprint support via fprintd
Upstream URL: https://github.com/SL-RU/swaylock-fprintd
Licenses: MIT
Conflicts: swaylock
Provides: swaylock
Submitter: lyra
Maintainer: xiota
Last Packager: xiota
Votes: 3
Popularity: 0.087020
First Submitted: 2023-01-30 11:12 (UTC)
Last Updated: 2024-08-19 22:14 (UTC)

Required by (33)

Sources (1)

Latest Comments

lostmia commented on 2024-06-19 08:32 (UTC) (edited on 2024-06-19 08:34 (UTC) by lostmia)

Since the split of glib2 into glib2 and glib2-devel some days ago, building the package might cause the following output if the latter is not installed: 

[...]
Run-time dependency gio-2.0 found: YES 2.80.3
Dependency gio-2.0 found: YES 2.80.3 (cached)
Program /usr/bin/gdbus-codegen found: NO

swaylock-fprintd/fingerprint/meson.build:12:29: ERROR: Dependency 'gio-2.0' tool variable 'gdbus_codegen' contains erroneous value: '/usr/bin/gdbus-codegen'

This is a distributor issue -- please report it to your gio-2.0 provider.

A full log can be found at /home/mia/.cache/yay/swaylock-fprintd-git/src/build/meson-logs/meson-log.txt
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: swaylock-fprintd-git-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
swaylock-fprintd-git - exit status 4

This is due to the /usr/bin/gdbus-codegen binary now being located in the glib2-devel package. Adding glib2-devel to the dependencies in the PKGBUILD fixed the issue for me.

galaux commented on 2024-04-01 18:46 (UTC)

python-packaging was required to build otherwise:

Found ninja-1.11.1 at /usr/bin/ninja
ninja: Entering directory `build'
[3/22] Generating gdbus header fingerprint/fprintd-dbus.h
FAILED: fingerprint/fprintd-dbus.h
/usr/bin/gdbus-codegen --c-generate-autocleanup all --interface-prefix net.reactivated.Fprint. --c-namespace FprintDBus --c-generate-object-manager --header --output fingerprint/fprintd-dbus.h /usr/share/dbus-1/interfaces/net.reactivated.Fprint.Manager.xml /usr/share/dbus-1/interfaces/net.reactivated.Fprint.Device.xml
Traceback (most recent call last):
  File "/usr/bin/gdbus-codegen", line 53, in <module>
    from codegen import codegen_main
  File "/usr/share/glib-2.0/codegen/codegen_main.py", line 30, in <module>
    from . import dbustypes
  File "/usr/share/glib-2.0/codegen/dbustypes.py", line 22, in <module>
    from . import utils
  File "/usr/share/glib-2.0/codegen/utils.py", line 22, in <module>
    import packaging.version
ModuleNotFoundError: No module named 'packaging'
[4/22] Generating gdbus source fingerprint/fprintd-dbus.c
FAILED: fingerprint/fprintd-dbus.c
/usr/bin/gdbus-codegen --c-generate-autocleanup all --interface-prefix net.reactivated.Fprint. --c-namespace FprintDBus --c-generate-object-manager --body --output fingerprint/fprintd-dbus.c /usr/share/dbus-1/interfaces/net.reactivated.Fprint.Manager.xml /usr/share/dbus-1/interfaces/net.reactivated.Fprint.Device.xml
Traceback (most recent call last):
  File "/usr/bin/gdbus-codegen", line 53, in <module>
    from codegen import codegen_main
  File "/usr/share/glib-2.0/codegen/codegen_main.py", line 30, in <module>
    from . import dbustypes
  File "/usr/share/glib-2.0/codegen/dbustypes.py", line 22, in <module>
    from . import utils
  File "/usr/share/glib-2.0/codegen/utils.py", line 22, in <module>
    import packaging.version
ModuleNotFoundError: No module named 'packaging'
[5/22] Generating swaylock.1 with a custom command (wrapped by meson to capture output, to feed input)
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
    Aborting...

lyra commented on 2023-05-25 11:28 (UTC)

Thank you all, I've fixes .SRCINFO!

tejase commented on 2023-05-16 22:12 (UTC)

@triarius You are spot on. I added epoch=1 to the PKGBUILD as you suggested and it corrected the behavior, although I believe that fixing it in .SRCINFO is the better fix. Then new installs will get a correct version number. So the best fix would be both adding epoch to the PKGBUILD and fixing the pkgver in .SRCINFO, as long as that would be an acceptable practice in the AUR.

triarius commented on 2023-05-15 09:51 (UTC)

@tejase The bug is in the .SRCINFO file. It has pkgver = r314.ffd639a-1 when it should have pkgver = r314.ffd639a. I suspect fixing this is not going to work, as r314.ffd639a-1-1 is a later version than r314.ffd639a-1. So a new epoch is required in the PKGBUILD to force package managers to recognise the correct version. You should be able to do this yourself to avoid your package manager from always trying to update it.

I think the .SRCINFO was hand rolled when it should be generated with makepkg --printsrcinfo > .SRCINFO, so I suggest that @lyra add epoch=1 to the PKGBUILD and run that command to fix the package.

Saphira commented on 2023-04-30 10:57 (UTC)

For some notebooks the fprintd-clients must be used because the fprintd doesnt work. I can also build, install and use these package with ignoring the fprintd dependency.

I also cant install the fprintd because its in conflict with the fprintd-clients.

So can you pls make the fprintd dependency as optional?

tejase commented on 2023-04-28 19:21 (UTC)

I believe there is a bug in this PKGBUILD. Every time I update my AUR packages via yay (yay -Sua, for example), it will clone and build this package even though git is still at the same commit. I believe it must be in the version string since it appends a '-1' every time like so: aur/swaylock-fprintd-git r314.ffd639a-1 -> r314.ffd639a-1-1

When I query pacman for the package, it reports the correct version number with a single '-1', even after I do an update. pacman -Q swaylock-fprintd-git swaylock-fprintd-git r314.ffd639a-1

It's not affecting functionality, the package works great, but it's just kind of annoying that it wants to update it every time I run some sort of system update. If you don't have time to take a look at, I might try to debug it and submit a merge request. Thanks!