Package Details: lokinet 0.9.11-5

Git Clone URL: (read-only, click to copy)
Package Base: lokinet
Description: Anonymous, decentralized and IP based overlay network for the internet.
Upstream URL:
Keywords: Anonymity Internet loki-network Network Oxen
Licenses: GPL3
Submitter: nekgem
Maintainer: nekgem2 (jagerman)
Last Packager: nekgem2
Votes: 10
Popularity: 0.012863
First Submitted: 2020-05-06 01:44 (UTC)
Last Updated: 2023-08-29 02:51 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4

nekgem2 commented on 2021-08-09 20:22 (UTC)

it could work with ngtcp2 but I couldn't get it to easily work and I wasn't sure if ngtcp2-notls-git providing ngtcp2 was good idea as things depending on ngtcp2 probably expect tls-enabled version as I suspect most of quic uses are tls-enabled.

whole ngtcp2-notls-git thing is probably unneeded now since ngtcp2-git uses gnutls and apparently that works so I guess I'll make it depend on ngtcp2. initially ngtcp2-git package used old draft branch and didn't built at all unless one had patched openssl which is why I forked it.

pix3l commented on 2021-07-18 09:10 (UTC)

Why it's dependant on ngtcp2-notls and not regular ngtcp2? It builds with regular ngtcp2 (tls enabled)

nekgem2 commented on 2021-05-04 12:28 (UTC)

@Tio upstream retagged and regenerated tarballs. Current pkgbuild matches current tarballs on github. If you have old ones laying around you'll have to delete them.

Tio commented on 2021-04-25 01:36 (UTC)

I get this error:

==> Validating source files with sha256sums...
    lokinet-v0.9.0.tar.xz ... FAILED
    lokinet-v0.9.0.tar.xz.sig ... Skipped
    lokinet.conf ... Passed
    lokinet.service ... Passed
    lokinet-vpn.service ... Passed
    lokinet-bootstrap.service ... Passed
    lokinet-default-config.service ... Passed
    lokinet-resume.service ... Passed
    lokinet.sysusers ... Passed
    lokinet.tmpfiles ... Passed
==> ERROR: One or more files did not pass the validity check!
Failed to build lokinet

nekgem2 commented on 2021-04-24 11:59 (UTC)

not really. ive removed it since i don't actually even know whether it would be packaged as oxenmq, liboxenmq, oxen-mq or whatever. correct way would be making separate package for it right now, but they don't bake proper source packages which include all submodules they reference so it's kinda pain.

jahway603 commented on 2021-04-19 20:57 (UTC)

Is conflicts=('oxen-mq') necessary in PKGBUILD? The package "oxen-mq" does not exist in the main Arch repo or in the AUR.