@Factorial This happens because go get
makes directories of downloaded packages read-only. This is outside of the control of this package.
You can rectify this with:
chmod -R u+w ~/.cache/yay/teleport && rm -rf ~/.cache/yay/teleport
Git Clone URL: | https://aur.archlinux.org/teleport.git (read-only, click to copy) |
---|---|
Package Base: | teleport |
Description: | Modern SSH server for teams managing distributed infrastructure |
Upstream URL: | https://github.com/gravitational/teleport |
Keywords: | ssh |
Licenses: | AGPLv3 |
Provides: | tctl, tsh |
Submitter: | mdeboer |
Maintainer: | fuhry |
Last Packager: | fuhry |
Votes: | 5 |
Popularity: | 0.000004 |
First Submitted: | 2021-03-21 18:58 (UTC) |
Last Updated: | 2024-09-26 20:44 (UTC) |
@Factorial This happens because go get
makes directories of downloaded packages read-only. This is outside of the control of this package.
You can rectify this with:
chmod -R u+w ~/.cache/yay/teleport && rm -rf ~/.cache/yay/teleport
After several months of always skipping upgrading this package, I now tried to upgrade to the latest version of this package (because the new Teleport server no longer supports old clients), but I've run into a new issue:
==> Validating source files with sha512sums...
teleport-16.1.0.tar.gz ... Passed
teleport-webassets-f48049a453348e0ee1ce2b998dffe5659455b398.tar.gz ... Passed
teleport.service ... Passed
teleport@.service ... Passed
teleport.install ... Passed
==> Removing existing $srcdir/ directory...
rm: cannot remove '/home/gabor/.cache/yay/teleport/src/go/pkg/mod/golang.org/x/oauth2@v0.20.0/example_test.go': Permission denied
rm: cannot remove '/home/gabor/.cache/yay/teleport/src/go/pkg/mod/golang.org/x/oauth2@v0.20.0/pkce.go': Permission denied
rm: cannot remove '/home/gabor/.cache/yay/teleport/src/go/pkg/mod/golang.org/x/oauth2@v0.20.0/heroku/heroku.go': Permission denied
rm: cannot remove '/home/gabor/.cache/yay/teleport/src/go/pkg/mod/golang.org/x/oauth2@v0.20.0/google/example_test.go': Permission denied
rm: cannot remove '/home/gabor/.cache/yay/teleport/src/go/pkg/mod/golang.org/x/oauth2@v0.20.0/google/appengine.go': Permission denied
rm: cannot remove '/home/gabor/.cache/yay/teleport/src/go/pkg/mod/golang.org/x/oauth2@v0.20.0/google/internal/impersonate/impersonate.go': Permission denied
rm: cannot remove '/home/gabor/.cache/yay/teleport/src/go/pkg/mod/golang.org/x/oauth2@v0.20.0/google/internal/externalaccountauthorizeduser/externalaccountauthorizeduser_test.go': Permission denied
rm: cannot remove '/home/gabor/.cache/yay/teleport/src/go/pkg/mod/golang.org/x/oauth2@v0.20.0/google/internal/externalaccountauthorizeduser/externalaccountauthorizeduser.go': Permission denied
rm: cannot remove '/home/gabor/.cache/yay/teleport/src/go/pkg/mod/golang.org/x/oauth2@v0.20.0/google/internal/stsexchange/sts_exchange_test.go': Permission denied
rm: cannot remove '/home/gabor/.cache/yay/teleport/src/go/pkg/mod/golang.org/x/oauth2@v0.20.0/google/internal/stsexchange/sts_exchange.go': Permission denied
And it goes on like this for many other files.
(I tried deleting /home/gabor/.cache/yay/teleport
and doing the whole procedure again, but it ran into the same error, so it's not due to something like an earlier sudo run of yay.)
What could be the problem here?
@gromit Thanks, in fact it seems that the license is tagged incorrectly here because this package compiles from source so the produced binaries have always been AGPLv3. The next push will reflect this.
@fuhry, just a heads up that teleport changed its license for the recent 16.0.0 release: https://goteleport.com/blog/teleport-community-license/
Companies or individuals are welcome to compile the source code under AGPLv3 terms.
@fuhry ah using a Docker container might actually be a good idea but yeah, like they say to find the rust version you have to look in the Makefile(s) but there is no mention of a rust version there (just the variable, never the definition).
But you seem to do a very good job on packaging this, I just find it frustrating and therefore decided to abandon this package myself.
@mdeboer can you share any logs of build issues you faced? With the recent changes I made to force it to build with rust 1.76, it is working for me.
I perform all of my builds in Docker containers using this script: https://gist.github.com/fuhry/688ed60f475e8fd0f8ec129a6c10eef1
It works for teleport, although I use a custom image (not archlinux:latest
) that has my local repository configured, which publishes libbpf-static as a binary so that makepkg --syncdeps
works.
I hereby disown the package as it is a total nightmare to build from source (they clearly want you to use the binaries).
I would recommend using teleport-bin instead.
I've had an error when upgrading my system with pacman -Syu
installing libbpf (1.3.0-1) breaks dependency 'libbpf=1.2.2-1' required by libbpf-static
I followed advice from here: https://www.reddit.com/r/archlinux/comments/157kw84/update_error_trying_to_understand_what_happened/
that is, I removed orphan packages. This removed libbpf-static. Then I performed the pacman -Syu
normally. Now I can't upgrade Teleport, because I'm getting the following error:
[gabor@ggwork ~]$ yay -Syu --devel --aur
:: Searching AUR for updates...
:: Checking development packages...
-> No AUR package found for libbpf=1.2.2-1
:: 4 dependencies will also be installed for this operation.
extra/gendesk -> 1.0.9-3
(make dependency of dropbox)
extra/go -> 2:1.21.5-1
(make dependency of teleport, teleport-client)
extra/yarn -> 1.22.21-1
(make dependency of teleport, teleport-client)
aur/libbpf-static -> 1.2.2-1
(make dependency of teleport, teleport-client)
:: 5 packages to upgrade/install.
5 aur/dropbox 175.4.5569-1 -> 186.4.6207-1
4 aur/dropbox-cli 2020.03.04-6 -> 2023.09.06-1
3 aur/jetbrains-toolbox 1.25.12569-1 -> 2.1.2.18853-1
2 aur/teleport 14.1.3-1 -> 14.2.2-1
1 aur/teleport-client 14.1.3-1 -> 14.2.2-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
-> Excluding packages may cause partial upgrades and break systems
==> 3 4
-> could not find all required packages: libbpf =1.2.2-1
Also, Teleport has stopped working:
[gabor@ggwork ~]$ tsh db connect <redacted>
psql: error: connection to server at "localhost" (::1), port 41807 failed: Connection refused
Is the server running on that host and accepting TCP/IP connections?
connection to server at "localhost" (127.0.0.1), port 41807 failed: SSL SYSCALL error: Success
free(): invalid pointer
ERROR: signal: aborted (core dumped)
Could you please advise me on how to resolve this situation?
Edit: In the meantime, I managed to upgrade Teleport by locally changing the pkgver of libbpf-static to 1.3.0, and then manually installing first libbpf-static, and then teleport. However, the above free(): invalid pointer
error is still happening.
The 12.0.4 update today adds some new build dependencies:
yarn
was an undeclared dependencylibbpf-static
is a new AUR package I've published which installs only the static library version of libbpf. This will track the version of libbpf in core and is designed to be installed alongside it.Hey, I'm now the co-maintainer of this package, and have pushed a few updates over the weekend:
teleport
and teleport-client
packages no longer replace each other. The teleport
package includes only the server portion, while teleport-client
provides tsh
and tctl
.update_version.sh
script which uses curl
and jq
to determine the latest Teleport release and webasssets commit through GitHub's API, modifies the PKGBUILD accordingly, re-generates checksums, and updates .SRCINFO
. This means it is much less effort for Maarten or myself to follow along with new releases.I started porting the first two items above to teleport-git
and teleport-client-git
but encountered some build issues. I will push once I can verify that it's building and running properly.
Please also note that at present, I don't have a test environment for the server package, so if that is broken in any capacity I would certainly appreciate notice of such.
Pinned Comments