Search Criteria
Package Details: telepresence 0.109-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/telepresence.git (read-only, click to copy) |
---|---|
Package Base: | telepresence |
Description: | Local development against a remote Kubernetes or OpenShift cluster |
Upstream URL: | https://github.com/telepresenceio/telepresence |
Keywords: | kubernetes telepresence |
Licenses: | Apache |
Submitter: | starkers |
Maintainer: | SuperBo |
Last Packager: | SuperBo |
Votes: | 7 |
Popularity: | 0.000000 |
First Submitted: | 2017-07-20 09:25 (UTC) |
Last Updated: | 2021-05-06 05:59 (UTC) |
Dependencies (9)
- conntrack-tools (conntrack-tools-gitAUR)
- fuse2
- kubectl (rancher-desktop-gitAUR, kbenv-binAUR, kuberlr-binAUR, rancher-desktopAUR, kubectl-binAUR)
- python (python37AUR, python311AUR, python310AUR)
- python-pip
- python-setuptools
- socat (socat-gitAUR)
- sshfs
- torsocks (torsocks-gitAUR)
Latest Comments
1 2 3 4 Next › Last »
Shibumi commented on 2021-06-09 11:50 (UTC) (edited on 2021-06-09 11:51 (UTC) by Shibumi)
Does not build in a clean environment:
jjjimenez commented on 2021-01-20 07:11 (UTC)
Getting an error trying to install it with Manjaro, 5.9.16 kernel.
pjvds commented on 2020-12-18 12:04 (UTC)
Patch for the hash
pjvds commented on 2020-12-18 12:01 (UTC)
The hash still doesn't match
DrPhil commented on 2020-12-03 11:52 (UTC)
Hash does nor match.
klemmster commented on 2020-11-18 10:48 (UTC)
It's happening again. The hash doesn't match.
dbirks commented on 2020-09-14 11:53 (UTC)
Thanks cuevaskoch, yeah I can confirm I'm getting that sha as well now. Just bumped to 0.108.
cuevaskoch commented on 2020-09-13 21:11 (UTC)
Looks like they've done it again, at least I am consistently getting a 0.107 sha256sum of
e2db257bf7f4f8b833912bcb2fe02ab42cc61429b61a0071dd8f61deb1001cb8
Additionally, looks like 0.108 is out
dbirks commented on 2020-05-26 13:34 (UTC)
Thanks for reporting the changed checksum. They must have re-released 0.105. I've pushed the change up.
russriguez commented on 2020-05-26 11:31 (UTC)
SRCINFO and PKGBUILD both seem to suggest the 105 sha256sum is
975a68dbf9d56625a9e1b617620a64ac5e8c23d4ac913c2fc0bc9c4e28af4d19
but when downloading the 105.tar.gz file and running sha256sum it gives me
00a2dd35dafd7361a97f7d7ff36349820bb828d58c4845e80faeaecee18a9770
just to check I did the same for release 104 and my hash matched the ones in the PKGBUILD and SRCINFO for 104, so I am assuming I've done the investigation correctly...
1 2 3 4 Next › Last »