You are not logged in.
Pages: 1
When i try to installa somthing from AUR and modify the PKGBUILD it say:
Editor environmental variable not set. Using nano...
But it's set in my .bashrc:
export EDITOR="vim"
Yesterday it function, but when i update the system, doesn't more...
Offline
Hi!
A "quick and dirty" fix may be running aurbuild like
# EDITOR=vim aurbuild [...]
But setting your EDITOR variable permanently and for all users may
solve this problem better. Simply add line
export EDITOR=vim
to file /etc/profile
-miky
What happened to Arch's KISS? systemd sure is stupid but I must have missed the simple part ...
... and who is general Failure and why is he reading my harddisk?
Offline
no, seems a problem of aurbuild, also if i set EDITOR into /etc/profile or launch EDITOR=vim aurbuild etc.. say that any EDITOR variable was setted....
Last edited by brainwasher (2007-07-28 15:00:41)
Offline
Sorry for the out topic, but I think I am missing something important about AUR (and yes I did read the Wiki.)
Using the aur is not only about downloading the source tarball, unpacking it somewhere, fix the PKGBUILD if needed and using makepkg for having a new package, installing it with pacman -U?
If I want fixing the PKGBUILD I write vim PKGBUILD and... thats it.
When/How/Whom you can have such message?
Edit: I noticed you are from Italy. So do I,,,
Last edited by ezzetabi (2007-07-28 15:47:38)
Offline
maybe i haven't understand....
mhmh, when i do sudo aurbuild -s package....
Offline
This... shouldn't happen. aurbuild does the same thing to me, but I'm looking at the source right now and don't see where the bug could be. I'll run it through the debugger and see what comes up.
Offline
Okay, I've found the problem. The behavior of sudo has changed, it no longer keeps the environment by default. Either run sudo with the -E option (for "preserve Environment"), or use visudo to edit the sudoers file and set env_reset to false. Here's the relevant line:
Defaults !env_reset
There can only be one Defaults line, so if you already have one defined, add "!env_reset" to it, separated from the existing settings by a single comma, no space.
EDIT: It looks like you need to set the setenv option in sudoers in order for -E to be available to a user. My bad.
Last edited by skymt (2007-07-28 18:03:04)
Offline
Okay, I've found the problem. The behavior of sudo has changed, it no longer keeps the environment by default. Either run sudo with the -E option (for "preserve Environment"), or use visudo to edit the sudoers file and set env_reset to false. Here's the relevant line:
Defaults !env_reset
There can only be one Defaults line, so if you already have one defined, add "!env_reset" to it, separated from the existing settings by a single comma, no space.
EDIT: It looks like you need to set the setenv option in sudoers in order for -E to be available to a user. My bad.
Ok, it work, thank u very much
Offline
Pages: 1