Package Details: keeweb 1.18.7-1

Git Clone URL: (read-only, click to copy)
Package Base: keeweb
Description: Desktop password manager compatible with KeePass databases
Upstream URL:
Keywords: kdbx keepass password
Licenses: MIT
Conflicts: keeweb-desktop
Submitter: surefire
Maintainer: petercxy
Last Packager: petercxy
Votes: 15
Popularity: 0.034967
First Submitted: 2016-09-26 07:43
Last Updated: 2021-08-13 10:50

Pinned Comments

petercxy commented on 2021-08-13 10:51

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 »

surefire commented on 2018-11-06 16:57

@jonher937, Sorry, fixed.

In the last revisions, there is nothing critical, in addition to increasing the speed of build by use libsass.

I also adopted keeweb-git. Updated it to the latest version using develop branch.

jonher937 commented on 2018-11-06 16:29

Looks like the sha1sum of package.json.patch.js is invalid

➜ keeweb git:(master) sha1sum package.json.patch.js 3cad1556a5a855a3ab5152f1b2cb175287bd8368 package.json.patch.js

➜ keeweb git:(master) makepkg query makepkg -cf
==> Making package: keeweb 1.6.3-3 (Tue 06 Nov 2018 05:27:59 PM CET) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found v1.6.3.tar.gz -> Found keeweb -> Found package.json.patch.js ==> Validating source files with sha1sums... v1.6.3.tar.gz ... Passed keeweb ... Passed package.json.patch.js ... FAILED

➜ keeweb git:(master) curl\?h\=keeweb | sha1sum


surefire commented on 2018-10-14 10:47

@alfredo.ardito, fixed

alfredo.ardito commented on 2018-10-14 08:57

Faild building with yay.

make: *** [ Release/] Error 1
make: Leaving directory '/home/username/.cache/yay/keeweb/src/keeweb-1.6.3/node_modules/node-sass/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/home/username/.cache/yay/keeweb/src/keeweb-1.6.3/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack at ChildProcess.emit (events.js:182:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
gyp ERR! System Linux 4.18.12-arch1-1-ARCH
gyp ERR! command "/usr/bin/node" "/home/username/.cache/yay/keeweb/src/keeweb-1.6.3/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /home/username/.cache/yay/keeweb/src/keeweb-1.6.3/node_modules/node-sass
gyp ERR! node -v v10.11.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
Build failed with error code: 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: keytar@4.0.3 (node_modules/keytar):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: keytar@4.0.3 install: node-gyp rebuild

npm ERR! errno 1
npm ERR! node-sass@4.5.3 postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@4.5.3 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/username/.npm/_logs/2018-10-14T08_33_59_442Z-debug.log
==> ERROR: A failure occurred in build().
Error making: keeweb

AlexWayfer commented on 2017-12-11 20:30

@surefire, I had the same output, but still no available executable. Reinstalling (including uninstalling) of asar package helped.

surefire commented on 2017-12-08 07:03

$ pacman -Ql asar | grep /usr/bin
asar /usr/bin/
asar /usr/bin/asar

AlexWayfer commented on 2017-12-05 18:40

$ pacman -Qs asar
local/asar 0.13.0-1
    Creating Electron app packages

But there is no executable asar.

surefire commented on 2017-12-03 13:53

@AlexWayfer, asar is a make dependency. Probably pacaur does not properly handle dependencies

AlexWayfer commented on 2017-12-03 10:56

/home/alex/.cache/pacaur/keeweb/PKGBUILD: line 66: asar: command not found

Trollwut commented on 2017-12-03 10:09

Ok, so which package to keep for the long run?