Package Details: swaylock-effects 1.7.0.0-4

Git Clone URL: https://aur.archlinux.org/swaylock-effects.git (read-only, click to copy)
Package Base: swaylock-effects
Description: A fancier screen locker for Wayland.
Upstream URL: https://github.com/jirutka/swaylock-effects
Licenses: MIT
Conflicts: swaylock
Provides: swaylock
Submitter: itsme
Maintainer: itsme
Last Packager: itsme
Votes: 32
Popularity: 0.32
First Submitted: 2021-01-31 13:39 (UTC)
Last Updated: 2024-02-05 20:37 (UTC)

Required by (34)

Sources (1)

Latest Comments

1 2 Next › Last »

itsme commented on 2024-02-05 20:37 (UTC)

@psvenk added, thanks

psvenk commented on 2024-02-05 18:26 (UTC) (edited on 2024-02-05 18:29 (UTC) by psvenk)

@itsme I came here with the same issue as fenouil; I believe it can be solved by adding a line like this to the PKGBUILD (like the official swaylock package does):

backup=('etc/pam.d/swaylock')

More info: https://wiki.archlinux.org/title/Pacman/Pacnew_and_Pacsave#Package_backup_files

itsme commented on 2024-02-03 21:57 (UTC)

@loqusion added, thank you.

loqusion commented on 2024-02-03 00:56 (UTC)

There should be a line like this in the PKGBUILD (provides alone isn't enough):

conflicts=('swaylock')

Otherwise, you get these errors when trying to install with swaylock already on your system:

error: failed to commit transaction (conflicting files)
swaylock-effects: /etc/pam.d/swaylock exists in filesystem (owned by swaylock)
swaylock-effects: /usr/bin/swaylock exists in filesystem (owned by swaylock)
swaylock-effects: /usr/share/bash-completion/completions/swaylock exists in filesystem (owned by swaylock)
swaylock-effects: /usr/share/fish/vendor_completions.d/swaylock.fish exists in filesystem (owned by swaylock)
swaylock-effects: /usr/share/man/man1/swaylock.1.gz exists in filesystem (owned by swaylock)
swaylock-effects: /usr/share/zsh/site-functions/_swaylock exists in filesystem (owned by swaylock)
Errors occurred, no packages were upgraded.

itsme commented on 2023-12-20 16:22 (UTC)

@fenouil I haven't found any package-level solution to the problem, it's more of a bug.

This may be helpful: https://wiki.archlinux.org/title/Pacman#Skip_file_from_being_upgraded

fenouil commented on 2023-12-20 07:54 (UTC) (edited on 2023-12-20 07:58 (UTC) by fenouil)

Every time a new swaylock-effects package is installed, if there is a diff, the PAM config file /etc/pam.d/swaylock is renamed to /etc/pam.d/swaylock.save and a fresh /etc/pam.d/swaylock is installed in place. I'm not sure but I think it's done without warning. Therefore it not make use of .pacnew convention, so pacdiff tool doesn't "see" it.

itsme commented on 2023-09-26 22:07 (UTC)

@kunev added, thank you.

kunev commented on 2023-09-10 06:51 (UTC)

This also builds and runs on aarch64 with no issues, so it would be nice to arr that to arch in in the PKGBUILD.

Naeth commented on 2023-04-18 07:10 (UTC)

https://github.com/jirutka/swaylock-effects/releases/tag/v1.6.11 merges the fixes for sway 1.8 as well, so you could switch back to jirutka's fork.

boredland commented on 2023-01-11 08:15 (UTC) (edited on 2023-01-11 08:20 (UTC) by boredland)

And aside from mortie making a release, what was the reason to switch away from the 'jirutka' branch? wasn't the reason back then that 'jirutka' had the upstream swaylock changes, while mortie didn't?

edit: saw the release notes now: https://github.com/mortie/swaylock-effects/releases/tag/v1.6-4

1 2 Next › Last »