Arch Linux User Repository

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: keeweb 1.18.7-1

Package Actions

Git Clone URL:	https://aur.archlinux.org/keeweb.git (read-only, click to copy)
Package Base:	keeweb
Description:	Desktop password manager compatible with KeePass databases
Upstream URL:	https://keeweb.info
Keywords:	kdbx keepass password
Licenses:	MIT
Conflicts:	keeweb-desktop
Submitter:	repsac
Maintainer:	alessi0
Last Packager:	petercxy
Votes:	18
Popularity:	0.000000
First Submitted:	2016-09-26 07:43 (UTC)
Last Updated:	2021-08-13 10:50 (UTC)

Dependencies (8)

electron12 (electron12-bin^AUR)
org.freedesktop.secrets (keepassxc-git^AUR, gnome-keyring-git^AUR, pass-secrets-git^AUR, keepassxc-allow-aur-extension-origin^AUR, keepassxc-allow-aur-extension-origin-bin^AUR, pass-secret-service-bin^AUR, dssd^AUR, pass-secret-service-git^AUR, bitw-git^AUR, keepassxc-qt6^AUR, gnome-keyring, keepassxc, kwallet, kwallet5)
asar (make)
cmake (cmake-git^AUR) (make)
git (git-git^AUR, git-gl^AUR) (make)
libsass (make)
nodejs (nodejs-lts-fermium^AUR, nodejs-git^AUR, python-nodejs-wheel^AUR, nodejs-lts-hydrogen, nodejs-lts-iron) (make)
npm (corepacker^AUR, python-nodejs-wheel^AUR) (make)

Required by (0)

Sources (5)

Pinned Comments

petercxy commented on 2021-08-13 10:51 (UTC) (edited on 2021-08-13 10:52 (UTC) by petercxy)

This package has been adopted and keeweb-connect support has been fixed. You might need to disable & re-enable the browser connector support in the app in order to update the native messaging configurations.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

quangvnm commented on 2020-02-06 12:05 (UTC)

@surefire, thank you for this package. This line:

  export npm_config_nodedir=/usr

in PKGBUILD doesn't work well with machine where system's nodejs (currently v13) isn't used, e.g by using nvm (node version manager) in my case. The error happens during rebuild of node-sass (there is a conflict between system nodejs's common.gypi file and my current nodejs version in LTS 12.x's common.gypi). My fix is to comment this line in PKGBUILD, then, it works well, because node-gyp will detect the correct folder for configuration files. Maybe I could try to switch nvm to use system's nodejs before executing makepkg.

AlexWayfer commented on 2019-09-13 09:48 (UTC)

I can't install: https://gist.github.com/AlexWayfer/ffbe8df6d317333ae98755f157cb3728

dctxmei commented on 2019-09-13 02:23 (UTC)

@surefire Please add python2 to makedepends, otherwise the following error will occur when using extra-x86_64-build:

gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` failed Error: not found: python2

repsac commented on 2019-08-22 04:48 (UTC)

@exxor, libappindicator-gtk3 do not display anything in GNOME without gnome-shell-extension-appindicator. This will mislead other users.

exor commented on 2019-08-22 04:34 (UTC) (edited on 2019-08-22 04:35 (UTC) by exor)

Can you add libappindicator-gtk3 to optional dependencies to make electron.Tray display a tray icon under gnome?

I do not know if there needs to be a "conditional" dependency based on which dm is installed gnome3/gnome2/else...

repsac commented on 2019-02-04 10:00 (UTC)

@marmotz Please update your system before build. Required libsass 3.5.5 or greater

marmotz commented on 2019-02-04 09:37 (UTC)

I've got following error since last thursday:

Running "sass:dist" (sass) task
Fatal error: File to import not found or unreadable: ../node_modules/normalize.css/normalize.

Koterpillar commented on 2019-01-19 08:49 (UTC)

https://github.com/keeweb/keeweb/issues/1089#issuecomment-455759190

This has both my bug and the confirmation that it's due to Electron 4.

repsac commented on 2019-01-19 06:18 (UTC)

@Koterpillar, how do I reproduce this bug?

Koterpillar commented on 2019-01-19 04:44 (UTC)

The official distribution and package.lock now depend on Electron 4.0.1. The bug with the second window opening is not present on the official distribution - perhaps the dependency here should be upgraded, not downgraded.

« First ‹ Previous 1 2 3 4 5 6 Next › Last »