| === thumper is now known as thumper-afk | ||
| === thumper-afk is now known as thumper | ||
| kcj | Morning. | 15:41 |
|---|---|---|
| ibeardslee | morning | 19:24 |
| ajmitch | morning | 19:26 |
| ibeardslee | oh kernel update .. be back in a bit | 19:29 |
| === _thumper_ is now known as thumper | ||
| thumper | ok, stupid question time | 22:21 |
| thumper | as user tim on my system I have a PATH defined that includes some local bin directories | 22:22 |
| thumper | created an exec called "filetest" in one of these "~/go/bin" for those that are interested | 22:22 |
| thumper | sudo filetest fails with command not found | 22:22 |
| thumper | but yet | 22:22 |
| thumper | sudo echo $PATH shows the path as including it | 22:22 |
| thumper | so why doesn't sudo look in the PATH for the directories? | 22:23 |
| thumper | I think it is just looking in /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin | 22:23 |
| thumper | which is what I get if I do: 'sudo su -', 'echo $PATH' | 22:23 |
| ibeardslee | what happens with 'which filetest' ? | 22:23 |
| thumper | ibeardslee: locally? or with sudo? | 22:24 |
| ibeardslee | both | 22:24 |
| thumper | $ which filetest | 22:24 |
| thumper | /home/tim/go/bin/filetest | 22:24 |
| thumper | $ sudo which filetest | 22:24 |
| thumper | is empty | 22:24 |
| ajmitch_ | because you're using sudo, and you don't have it set to keep PATH | 22:24 |
| ajmitch_ | when you sudo echo $PATH it expands it before passing to sudo | 22:25 |
| thumper | ah | 22:25 |
| thumper | that makes sense | 22:25 |
| ajmitch_ | Defaults env_reset | 22:26 |
| ajmitch_ | Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" | 22:26 |
| * thumper copies filetest to /usr/local/bin to continue testing | 22:26 | |
| ajmitch_ | you could change /etc/sudoers if you want, but that's messy :) | 22:26 |
| thumper | nah | 22:26 |
| thumper | doesn't matter for the testing I'm doing | 22:26 |
| thumper | I'm wanting to confirm some uid checks and hunting for a file | 22:27 |
| olly | morning | 22:28 |
| olly | thumper: to see the PATH inside sudo, you could try: sudo printenv|grep PATH | 22:29 |
| thumper | olly: oh, ta | 22:30 |
| thumper | is printenv like env? | 22:30 |
| thumper | same thing | 22:30 |
| olly | it gives your fingers more exercise | 22:31 |
| * olly didn't know env also printed the env - only used it as a shell-portable way to set variables for a command | 22:31 | |
| ibeardslee | I notice that with all the X-Launchpad headers .. there isn't one that says what the bug number is | 23:19 |
| ajmitch_ | ibeardslee: probably considered redundant since the bug # is in the subject | 23:21 |
| ibeardslee | I'm having some fail at managing to extract that in my .procmailrc | 23:22 |
| ibeardslee | would probably have just as much trouble if it was part of another header | 23:22 |
| ajmitch_ | what are you wanting to do? | 23:22 |
| ibeardslee | filter bugs into separate folders per bug | 23:23 |
| ibeardslee | will evolution's search folders to deal with the other breakdowns as required | 23:23 |
| ajmitch_ | sounds a bit like overkill, but that's because I have too many bugs to see :) | 23:23 |
| ibeardslee | could get overkill down the track, but I'll worry about it then | 23:24 |
| ajmitch_ | I'm sure you could use a regular expression on the Subject: header to capture the bug # & use that | 23:27 |
| ibeardslee | yeap .. working on that .. actually using the reply-to header | 23:27 |
| ajmitch_ | ok | 23:27 |
| ibeardslee | .. but failing | 23:28 |
| thumper | ibeardslee: we don't normally have people wanting to filter on individual bugs | 23:28 |
| thumper | that way lies insanity | 23:29 |
| thumper | subject prefix is always r"\[Bug (\d+)\]" | 23:30 |
| thumper | surely you can use regex | 23:31 |
| ibeardslee | I thought I had a vague idea from copying the one that I found for dealing to mailing lists | 23:31 |
| thumper | ibeardslee: although I agree about using the reply-to header, more likely to be consistent | 23:35 |
| thumper | as someone can change the subject of the email simply by using email with a different subject and emailing the bug | 23:36 |
| ibeardslee | but the reply-to header can be changed with someone emailing me privately | 23:37 |
| ajmitch_ | why do you want separate folders per bug? | 23:38 |
| ajmitch_ | I could understand a folder per package, perhaps | 23:38 |
| ibeardslee | I'm in the process of rethinking that | 23:38 |
| ibeardslee | although with OpenERP a bunch of bugs with the same project | 23:39 |
| ibeardslee | hmmm | 23:39 |
| ajmitch_ | that's why mail clients have threading :) | 23:39 |
| * ibeardslee just moves all ^X-Launchpad-Bug: into the same folder while he ponders a bit more | 23:50 | |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!