Package Details: telepresence 0.109-1

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.024427
First Submitted: 2017-07-20 09:25
Last Updated: 2021-05-06 05:59

Latest Comments

1 2 3 4 Next › Last »

Shibumi commented on 2021-06-09 11:50

Does not build in a clean environment:

==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found telepresence-0.109
==> WARNING: Skipping all source file integrity checks.
==> Extracting sources...
  -> Extracting telepresence-0.109 with bsdtar
==> Entering fakeroot environment...
==> Starting package()...
Installing Telepresence in /build/telepresence/pkg/telepresence/usr
Built /tmp/tmp.PWpNLM3dl0/dist/telepresence
Traceback (most recent call last):
  File "/build/telepresence/src/telepresence-0.109/packaging/build-sshuttle.py", line 77, in <module>
    main()
  File "/build/telepresence/src/telepresence-0.109/packaging/build-sshuttle.py", line 73, in main
    build_sshuttle(output)
  File "/build/telepresence/src/telepresence-0.109/packaging/build-sshuttle.py", line 28, in build_sshuttle
    check_call([
  File "/usr/lib/python3.9/subprocess.py", line 368, in check_call
    retcode = call(*popenargs, **kwargs)
  File "/usr/lib/python3.9/subprocess.py", line 349, in call
    with Popen(*popenargs, **kwargs) as p:
  File "/usr/lib/python3.9/subprocess.py", line 951, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.9/subprocess.py", line 1821, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'git'

jjjimenez commented on 2021-01-20 07:11

Getting an error trying to install it with Manjaro, 5.9.16 kernel.

Building telepresence...
==> Making package: telepresence 0.108-1 (Wed 20 Jan 2021 03:11:09 PM PST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found telepresence-0.108
==> Validating source files with sha256sums...
    telepresence-0.108 ... FAILED
==> ERROR: One or more files did not pass the validity check!
Failed to build telepresence

pjvds commented on 2020-12-18 12:04

Patch for the hash

diff --git a/PKGBUILD b/PKGBUILD
index dd03d38..2271bda 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -9,7 +9,7 @@ arch=('x86_64')
 license=('Apache')
 url='https://github.com/telepresenceio/telepresence'
 source=("$pkgname-$pkgver::https://github.com/telepresenceio/telepresence/archive/${pkgver}.tar.gz")
-sha256sums=('afc554a62c56acf5ab6a3ab44b9208ba5f893ed90a4ea4783ca269672a6aeed7')
+sha256sums=('1dca892b5db9773c8a60ee003db2010845341f6f9cf22ef1d94800dd0c935a78')
 makedepends=('git')
 depends=('conntrack-tools' 'fuse2' 'kubectl' 'socat' 'sshfs' 'torsocks' 'python' 'python-pip' 'python-setuptools')

pjvds commented on 2020-12-18 12:01

The hash still doesn't match

DrPhil commented on 2020-12-03 11:52

Hash does nor match.

klemmster commented on 2020-11-18 10:48

It's happening again. The hash doesn't match.

dbirks commented on 2020-09-14 11:53

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

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

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

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...