Package Details: passwordsafe 1.09.0-1

Git Clone URL: (read-only, click to copy)
Package Base: passwordsafe
Description: Simple & Secure Password Management
Upstream URL:
Keywords: password pwsafe security yubikey
Licenses: Artistic2.0
Conflicts: passwordsafe-debian, pwsafe, pwsafe-gui
Submitter: Namarrgon
Maintainer: Namarrgon
Last Packager: Namarrgon
Votes: 27
Popularity: 0.014840
First Submitted: 2014-05-07 13:02
Last Updated: 2020-01-08 20:07

Pinned Comments

Namarrgon commented on 2020-01-07 15:56

Updates are usually delayed by the lack of signed tarballs.

Latest Comments

1 2 3 4 Next › Last »

pdpelf commented on 2020-01-08 09:14

i've contacted Rony and the signed tarball is at github

Namarrgon commented on 2020-01-07 15:56

Updates are usually delayed by the lack of signed tarballs.

pdpelf commented on 2020-01-07 15:43

hi Namarrgon, es gibt eine neue Version von PasswordSafe:

PasswordSafe Linux release 1.09.0

Gruß Eberhard

Namarrgon commented on 2019-07-29 11:54

Sorry for the long silence, my health was causing me grief but I'm mostly back up again.

@Blutkoete Thank you for the upstream contribution, it's greatly appreciated!

@grantdb I can't reproduce it. Can you try to build 1.08.2 in a clean chroot?

grantdb commented on 2019-07-28 22:47

Fails building with: make[2]: [src/core/CMakeFiles/core.dir/build.make:72: src/core/CMakeFiles/core.dir/AES.cpp.o] Error 1 make[1]: [CMakeFiles/Makefile2:311: src/core/CMakeFiles/core.dir/all] Error 2 make: *** [Makefile:163: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

Blutkoete commented on 2019-07-16 20:24

Hello Namarrgon,

I wrote a script for upstream that makes the process of verifying the content of the release archives easier for them and now we have signed tarballs/zips again!

Updating this AUR packages should now be possible again without needing to sacrifice the signature check on the sources.

Thank you for packaging passwordafe!

kgmoney commented on 2019-04-27 03:47

I'm unable to compile this package for some reason. I feel like it's something specific to my machine, but don't know what...I have installed the base-devel group. Here is the output I'm getting...

make[2]: [src/os/CMakeFiles/os.dir/build.make:141: src/os/CMakeFiles/os.dir/unix/file.cpp.o] Error 1 make[1]: [CMakeFiles/Makefile2:278: src/os/CMakeFiles/os.dir/all] Error 2 make[1]: Waiting for unfinished jobs.... make[2]: [src/core/CMakeFiles/core.dir/build.make:150: src/core/CMakeFiles/core.dir/ExpiredList.cpp.o] Error 1 make[2]: [src/core/CMakeFiles/core.dir/build.make:111: src/core/CMakeFiles/core.dir/Command.cpp.o] Error 1 make[2]: [src/core/CMakeFiles/core.dir/build.make:163: src/core/CMakeFiles/core.dir/ItemAtt.cpp.o] Error 1 make[2]: [src/core/CMakeFiles/core.dir/build.make:137: src/core/CMakeFiles/core.dir/CoreOtherDB.cpp.o] Error 1 make[2]: [src/core/CMakeFiles/core.dir/build.make:124: src/core/CMakeFiles/core.dir/CoreImpExp.cpp.o] Error 1 make[1]: [CMakeFiles/Makefile2:333: src/core/CMakeFiles/core.dir/all] Error 2 [ 21%] Linking CXX static library ../../lib/libgtest.a [ 21%] Built target gtest make: [Makefile:163: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build passwordsafe.

Namarrgon commented on 2018-10-17 00:34


The 'base-devel' group is an implicit dependency when building a package from a PKGBUILD. It would be wise to read the rest of the AUR page, too.

webx123 commented on 2018-10-17 00:00

I had that error on a pretty fresh manjaro installation :

=========== CMake Error: CMake was unable to find a build program corresponding to "Unix Makefiles". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool. CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage ===========

I've added 'make' to makedepends in PKGBUILD and the installation went great.

Namarrgon commented on 2018-10-15 10:34

That warning is caused by asserts that embed the source-file names. Some of these snuck past all the release/ndebug flags for some reason and i'll look into it.

If you are redistributing the package to others and fear leaking that information then you might want to build the package in a clean chroot. The scripts (e.g. extra-x86_64-build) from the devtools package make this trivial.

If you're building this for personal use then these are harmless.