§

> but I'm not using the F-Droid build, but the GH one, so I would benefit from this. Sorry I didn't notice that. The general idea is : android apps...

> it says above not to run makepkg from root account That's the 2nd error if I run `sudo yay -S sirikali` > have you tried running it from normal...

I simply installed the binary https://aur.archlinux.org/packages/sirikali-bin _unofficial_ version by [Clifton](https://aur.archlinux.org/account/cmulk). It works well ;)

Thanks, yes now it should work fine for users. Would be nice if it could do that automatically without such extra step. In my case it showed ``` error: failed...

Details ``` ==> WARNING: Skipping verification of source file PGP signatures. ==> Validating source files with sha256sums... SiriKali-1.7.0.tar.xz ... Passed SiriKali-1.7.0.tar.xz.asc ... Skipped :: (1/1) Parsing SRCINFO: sirikali gpg: error...

I understand bundled with SiriKali, users can now update them directly from it but IMO making these filesystem packages **opt-in** during the 1st launch and only then install with user...

backend = the `filesystem`? I'm using `cryfs`. _(the [pacman](https://archlinux.org/packages/extra/x86_64/cryfs/) package not from AUR)_

Now when I update it gives me this error ``` /home/my_name/.cache/yay/sirikali/PKGBUILD: line 27: unexpected EOF while looking for matching `'' ==> ERROR: Failed to source /home/my_name/.cache/yay/sirikali/PKGBUILD -> error making: sirikali-exit...

Thanks. But we do need a release tag on GitHub? ``` curl: (22) The requested URL returned error: 404 ==> ERROR: Failure while downloading https://github.com/mhogomchungu/sirikali/releases/download/1.7.2/SiriKali-1.7.2.tar.xz Aborting... ```

> Version 1.7.1 is released and the feature is now opt in and can be enabled through menu->settings->manage securefs and gocryptfs. What does it do? If I enable that option...