Package Details: psiphon-tunnel-core-git 1:2.0.14.r3354.08f530bd-3

Git Clone URL: https://aur.archlinux.org/psiphon-tunnel-core-git.git (read-only, click to copy)
Package Base: psiphon-tunnel-core-git
Description: Psiphon Tunnelling Proxy
Upstream URL: https://github.com/Psiphon-Labs/psiphon-tunnel-core
Keywords: proxy psiphon vpn
Licenses: GPL3
Submitter: Modelmat
Maintainer: Modelmat (gilcu3)
Last Packager: gilcu3
Votes: 1
Popularity: 0.000003
First Submitted: 2019-10-26 01:42
Last Updated: 2021-03-04 14:37

Latest Comments

ainola commented on 2021-03-10 00:45

That's research you'll have to embark upon youself. :)

Surely upstream has some issue tracker somewhere... or some sort of forum/mailing list.

gilcu3 commented on 2021-03-08 09:32

Pestering upstream is not possible in this case. They don't accept issues in their repo, so I assume when they have availability they will update their go version. Regarding taking directly their binary, yes, this is for sure possible. @ainola you mention the possibility of sourcing an old release of go from the aur, would this be possible without the user having to uninstall the current version?

ainola commented on 2021-03-05 06:32

The first order of business would be to pester upstream to make their software work with 1.16. If they refuse, you'll need to source an older release of Go on the AUR or make it yourself if absent.

The idea of package management in general is to coordinate packages together with a defined, cohesive system; Docker is a very unfit solution as it stomps all over Arch build systems with who-knows-what is defined in the Dockerfile.

If you just want this to be installable on Arch, I'd recommend creating psiphon-tunnel-core-bin-git and installing the pre-built binaries.

I hope that clarifies the situation.

gilcu3 commented on 2021-03-05 05:33

@ainola is it possible to use a different go version in a chroot environment? wouldn't this be more or less equivalent regarding computing resources to the docker approach?

ainola commented on 2021-03-05 05:12

Docker is definitely not going to fly here. I'd end up either reverting or deleting the package. Packages in the AUR need to be built from either the base system or a chroot environment.

gilcu3 commented on 2021-03-04 14:38

@ainola I thing I finished all your recomendations, thank you :) Now I found a bigger issue, it seems this package only works if compiled with go 1.14, as there is an embedded (and customized dependency, quic-go) that has not been updated and doesn't work with go 1.15+... So the only way I see to make it work is to revert to docker... what do you think?

ainola commented on 2021-03-04 05:27

That's better, but it could still use some more work. :)

A few things to improve:

  • You'll need to add "git" as a makedepends

  • Use sha256sums, not md5sums

  • The license is GPL3, not GPL

  • Echoing random messages is discouraged

  • I was unable to build this in a chroot environment - lots of dependencies are not declared.

  • LDFLAGS is being clobbered with all the environment variables set there. We need to preserve those flags that are set in /etc/makepkg.conf

You'll want to read the following three articles to better this package:

Good luck!

gilcu3 commented on 2021-03-03 07:55

@ainola I just fixed the go build. Can you confirm it works on your machine?

gilcu3 commented on 2021-03-03 07:08

@ainola Oh sorry, I didn't know docker was not advised here. I just used it because now it is the official build system for the ConsoleClient https://github.com/Psiphon-Labs/psiphon-tunnel-core/tree/master/ConsoleClient. I can try with Go when I get some time :)

ainola commented on 2021-03-03 07:03

gilcu3, Using docker is absolutely not okay as a build system. I am reverting this to before the changes were introduced. Please try again while paying attention to the Go packaging guidelines:

https://wiki.archlinux.org/index.php/Go_package_guidelines