Package Details: i3lock-color 2.13.c.5-3

Git Clone URL: https://aur.archlinux.org/i3lock-color.git (read-only, click to copy)
Package Base: i3lock-color
Description: The world's most popular non-default computer lockscreen.
Upstream URL: https://github.com/Raymo111/i3lock-color
Keywords: i3 i3lock i3wm lock lockscreen
Licenses: MIT
Conflicts: i3lock, i3lock-color-git
Provides: i3lock, i3lock-color
Submitter: Alad
Maintainer: Raymo111 (wilssonmartee)
Last Packager: Raymo111
Votes: 64
Popularity: 0.89
First Submitted: 2020-10-18 21:53 (UTC)
Last Updated: 2024-08-29 00:57 (UTC)

Latest Comments

1 2 3 Next › Last »

Netboy3 commented on 2024-08-28 21:34 (UTC) (edited on 2024-08-29 15:21 (UTC) by Netboy3)

Please note that this package overwrites /etc/pam.d/i3lock. Arch recommends to flag any globally installed configuration files with backup. I had my PAM i3lock modified to include unlocking with Yubikey just to have it reverted by the latest update.

Here's a patch for this:

diff --git a/PKGBUILD b/PKGBUILD
index 09be115..375e748 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -12,6 +12,7 @@ depends=('xcb-util-image' 'pam' 'libev' 'cairo' 'libxkbcommon-x11'
          'libjpeg-turbo' 'xcb-util-xrm' 'pkgconf')
 provides=('i3lock' 'i3lock-color')
 conflicts=('i3lock' 'i3lock-color-git')
+backup=('etc/pam.d/i3lock')
 source=("${url}/archive/$pkgver.tar.gz")
 sha256sums=('46f15cbbf339873266e014f70b5e1ec02177f0295302b615a7bd85bef40d8ad2')

Raymo111 commented on 2024-08-27 20:48 (UTC)

Thanks @freedomd1v3, I added the fix to the PKGBUILD.

earlybird commented on 2024-08-27 06:16 (UTC)

could you fix the pkgbuild? Can not build it in chroot. No rule to make target 'all-configured'. Stop.

Laoki commented on 2024-07-31 00:30 (UTC)

@howdee Thank you!

howdee commented on 2024-07-29 10:15 (UTC)

@Laoki You can manually clone the repository and edit the PKGBUILD. You need to add the provided lines right before make in the build() function and then execute makepkg -si afterward. I still encountered the error message during the install but it worked, thanks a lot @freedomd1v3.

Laoki commented on 2024-07-29 01:52 (UTC)

@freedomd1v3 I encountered this error today when trying to build. Excuse my ignorance, but to where exactly should the lines you provided be added?

freedomd1v3 commented on 2024-07-25 15:19 (UTC) (edited on 2024-07-25 15:22 (UTC) by freedomd1v3)

Dear maintainers,

thank you for supporting this package. I'd like to report, that on the completely updated system, make is complaining about lack of recipe for target "all-configured". The same story goes with package "i3lock-color-git".

There is no such error when using "build.sh" script provided in the "i3lock-color" GitHub repository, but it appears again when using the autoreconf -fi, ./configure --enable-debug=no --disable-sanitizers and later make.

As a temporary workaround for those having this issue, it's possible to add the following lines to PKGBUILD after the Makefile is generated:

awk '!/all-configured/' Makefile > Makefile.new

rm Makefile

mv Makefile.new Makefile

programegg commented on 2022-11-13 16:31 (UTC) (edited on 2022-11-13 16:31 (UTC) by programegg)

@kolay.ne autoconf and automake are both in base-devel which is a prerequisite to use the AUR. As per the makepkg wiki any package belonging to base-devel does not need to be listed as a build-time dependency.

kolay.ne commented on 2022-11-13 13:34 (UTC)

The PKGBUILD at 53b6bbf08995 uses (but does not specify as make dependencies):

makedepends=('autoconf' 'automake')

sysfs commented on 2021-06-04 03:28 (UTC)

Thanks. Submitted notes to the maintainer of that package as 3.2.0 fixes it.

1 2 3 Next › Last »