I'm the server's admin, and only user. To my mind, it matters little which user installs it. If there were other users, however, I would be even more inclined to install as root so that they, too, could use zef. Any root/sudo user should be able to use it, in my opinion. It has been my experience, though, that when installing applications, the root user generally succeeds better as it will encounter fewer permissions-related issues.
Nevertheless, being willing to attempt your suggestion, I received the below results...
Cloning into 'zef'...
remote: Enumerating objects: 11711, done.
remote: Counting objects: 100% (1112/1112), done.
remote: Compressing objects: 100% (536/536), done.
remote: Total 11711 (delta 670), reused 946 (delta 558), pack-reused 1
+0599
Receiving objects: 100% (11711/11711), 2.38 MiB | 10.90 MiB/s, done.
Resolving deltas: 100% (7195/7195), done.
failed to create directory: /tmp/.zef/1703756967.189511/1703756975.189
+511.3413.866087216334
Any ideas?
(NOTE: I've edited my original post to add a link showing that "zef" was deliberately removed from Ubuntu's 22.04 repository. That's why all this manual installation is necessary...and complicated. I'm not sure if Raku's developers dropped the ball, owing to name-changes from Perl6, or if Ubuntu's developers were doing something nefarious, but it is what it is.)
| [reply]
[d/l] |
Sure, I'm just trying to find out whether the problem is with the expectations of zef and I expect the developers to work under a non-root user, which is why I'm trying to get you to replicate their situation more closely.
What is your working directory? The error message suggests that it is /tmp, and maybe /tmp has special permissions or a limited size. I suggested to install it below $HOME in a separate directory, but you know your system better and can maybe suggest a different directory that is not special.
| [reply]
[d/l]
[select] |
I installed in my home directory directly, as my personal user, per your suggestions. I neither made, nor entered, a /tmp directory. I have no idea why that appeared in the failure message.
| [reply] |
” I'm the server's admin, and only user...”
That's not good. Not good at all. It's actually a big mistake. But you can still change it. Create a user polyglot or whatever. And sudo is your friend. You probably also log in as root via SSH, yes? Not good either. Turn that off. Logging in with keys is not a bad idea either. My provider has been doing this recently. And in the company I was last at (and in all the others too) this was the usual procedure. And corion has already said it: Install such stuff in your home - or in that of any other user for this purpose.
«The Crux of the Biscuit is the Apostrophe»
| [reply] |
I login as my home user, then upgrade to root as necessary. The way the server is setup, no one is able to enter remotely as root (I think it's possible with console access--but any hacker with physical access cannot be stopped from basically whatever, anyhow).
Yes, I use SSH...don't virtually all server admins?
I have a few tricks up my sleeve for server security, though. I've only been successfully hacked once--many years ago when I was a bit wetter behind the ears. In that case, it was a security hole in PHP. I just don't bother using anything with PHP anymore (at least, not public-facing). Who needs PHP when perfectly able to program in Perl? :)
I use keys for some things, but consider them to be a security risk of a different sort, e.g. if someone steals my laptop that has my keys on it....well, there goes access to my servers, too, if the thief has tech savvy.
As for my Raku setup, I am wanting to use Raku for my public-facing CGI scripts. Putting it in my home dir makes little sense to me. Someone will have to be more detailed in explanation to help me grasp what sort of security risk I'd be mitigating by doing so...and why there would not be an equally negative risk to my /home/user materials. I note that Perl never needed to be installed in my home dir.
| [reply] |