Package Details: sirikali 1.5.1-1

Git Clone URL: https://aur.archlinux.org/sirikali.git (read-only, click to copy)
Package Base: sirikali
Description: A Qt/C++ GUI front end to sshfs, ecryptfs-simple, cryfs, gocryptfs, securefs, fscrypt and encfs
Upstream URL: https://mhogomchungu.github.io/sirikali/
Licenses: GPL
Conflicts: sirikali-git
Submitter: ConorIA
Maintainer: mhogomchungu
Last Packager: mhogomchungu
Votes: 31
Popularity: 1.30
First Submitted: 2016-12-26 21:50 (UTC)
Last Updated: 2023-07-12 13:49 (UTC)

Dependencies (16)

Required by (0)

Sources (2)

Pinned Comments

Latest Comments

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

kaszak696 commented on 2019-02-11 07:25 (UTC) (edited on 2019-02-11 07:35 (UTC) by kaszak696)

Installing lxqt_wallet and adding the cmake switch allows it to go further, but the build still fails with:

/bin/ld: cannot find -lsecretlib
/bin/ld: cannot find -lKF5::Wallet
/bin/ld: cannot find -lKF5::Notifications
/bin/ld: cannot find -llxqt-wallet-backend
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/sirikali.dir/build.make:1236: sirikali] Error 1
make[1]: *** [CMakeFiles/Makefile2:74: CMakeFiles/sirikali.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
==> ERROR: A failure occurred in build().
Aborting...

I don't get it, all of those libraries are installed, it should be able to access them just fine.

EDIT: After changing nothing, i tried to build it again and it succeeded. Weird.

mhogomchungu commented on 2019-02-11 04:11 (UTC)

SiriKali does not use anything dbus and i do not know why Qt-dbus is getting pulled as a dependency here.

Somebody else encountered the same problem and solved by using external lxqt-wallet package[1]. Try to do the same by running cmake with a config option of "-DINTERNAL_LXQT_WALLET=false"

[1] https://github.com/mhogomchungu/sirikali/issues/92#issuecomment-460330441

karcher commented on 2019-02-10 20:56 (UTC)

Hi. I'm getting this error during update:

-- Configuring done
CMake Error at CMakeLists.txt:354 (add_executable):
  Target "sirikali" links to target "Qt5::DBus" but the target was not found.
  Perhaps a find_package() call is missing for an IMPORTED target, or an
  ALIAS target is missing?


CMake Warning (dev) at src/3rdParty/lxqt_wallet/frontend/CMakeLists.txt:205 (add_library):
  Policy CMP0028 is not set: Double colon in target name means ALIAS or
  IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  Target "lxqt-wallet" links to target "Qt5::DBus" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Generating done
-- Build files have been written to: /home/nick/.cache/yay/sirikali/src/SiriKali-1.3.7/build
==> ERROR: A failure occurred in build().
    Aborting...
Error making: sirikali

Woodhousezb commented on 2018-06-27 07:00 (UTC)

At this moment I still get the error that some keys are unavailable when trying to install this through PAMAC

SiriKali-1.3.4.tar.xz ... FAILED (unknown public key 16E2E1ACC6F51242)

Installing the key as proposed by mhogomchungu is no resolve at this moment.

Tried this on a freshly installed anterrgos system and a manjaro system.

leoneill commented on 2018-02-26 11:38 (UTC)

@mhogomchungu, solved by downloading the new PKGBUILD. Thx!

mhogomchungu commented on 2018-02-26 10:51 (UTC)

@leoneill,

I think you are getting the problem because you are using older PKGBUILD file that uses the old .asc file.

Download a new PKGBUILD file and try again.

leoneill commented on 2018-02-26 10:41 (UTC)

Before the update, I ran: gpg --recv-keys 0x6855E493B5B2DF96E319BB6D16E2E1ACC6F51242

Unable to update due to invalid key: SiriKali-1.3.3.tar.xz ... FAILED (invalid public key E3AF84691424AD00E099003502FC64E8DEBF43A8) ==> ERROR: One or more PGP signatures could not be verified!

mhogomchungu commented on 2018-02-24 09:15 (UTC)

A new key that uses sha2 can be imported with the following command:

gpg --recv-keys 0x6855E493B5B2DF96E319BB6D16E2E1ACC6F51242

The new signature is named "SiriKali-1.3.3.tar.xz.sha2.asc" and is located at: https://github.com/mhogomchungu/sirikali/releases/download/1.3.3/SiriKali-1.3.3.tar.xz.sha2.asc

ConorIA commented on 2018-02-23 19:03 (UTC)

@mhogomchungu thanks for the further details. I'd suggest that users who can't accept the SHA-1 sig should use the PKGBUILD in the snapshot (https://goo.gl/UXTWvq) until you make a new release. Using the AUR is considered "advanced" usage for Arch et al., so I would expect users to be able to implement this workaround themselves. I will update this PKGBUILD when you've made a new release or if Arch also moves away from SHA-1 before a new release.

However, another option would be for you to create a new .asc signature on the old .tar.xz file, which I could swap in for the older signature temporarily. Is there something specific about your release process that prevents that from happening?

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