Package Details: rofi-rbw-git 1.4.2.r3.g03630d0-1

Git Clone URL: https://aur.archlinux.org/rofi-rbw-git.git (read-only, click to copy)
Package Base: rofi-rbw-git
Description: Rofi frontend for Bitwarden
Upstream URL: https://github.com/fdw/rofi-rbw
Licenses: MIT
Conflicts: rofi-rbw
Provides: rofi-rbw
Submitter: MaxWoahverdrive
Maintainer: MaxWoahverdrive
Last Packager: MaxWoahverdrive
Votes: 2
Popularity: 0.064037
First Submitted: 2023-09-18 09:38 (UTC)
Last Updated: 2024-12-28 14:45 (UTC)

Dependencies (15)

Required by (0)

Sources (1)

Latest Comments

merdely commented on 2024-12-28 15:30 (UTC)

Thank you so much!

MaxWoahverdrive commented on 2024-12-28 14:47 (UTC)

I've updated the optdepends to reflect the new dependency on libnotify's notify-send and bumped the pkgver along with that change

merdely commented on 2024-12-28 13:51 (UTC)

There is a new feature that rofi-rbw uses notify-send to alert the user that the TOTP has been copied to the clipboard that is not in the version in the AUR

MaxWoahverdrive commented on 2024-12-24 08:43 (UTC)

@merdely VCS packages like this -git package do not need to be updated on the AUR for mere pkgver increments. (see https://wiki.archlinux.org/title/AUR_submission_guidelines#Publishing_new_package_content)

merdely commented on 2024-12-23 19:35 (UTC) (edited on 2024-12-23 19:36 (UTC) by merdely)

You could update to a more recent version from git:

diff --git a/PKGBUILD b/PKGBUILD
index 993fa65..eafe5ac 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -2,7 +2,7 @@

 _pkgname='rofi-rbw'
 pkgname="${_pkgname}-git"
-pkgver=1.2.0.r3.gce65e72
+pkgver=1.4.2.r3.g03630d0
 pkgrel=1
 pkgdesc='Rofi frontend for Bitwarden'
 arch=('x86_64')

Thanks

MaxWoahverdrive commented on 2023-09-30 11:01 (UTC)

Permission errors during install caused by having the non -git variant installed should be fixed

MaxWoahverdrive commented on 2023-09-28 10:06 (UTC)

I am aware of the permission issue when installing while rofi-rbw is still installed. the pip install to the staging directory attempts to remove the existing install when it shouldn't, since the conflict will be handled by the package manager. I'll look into a fix when I'm home on saturday