Re: [Fab-user] fab sudo() doesn't seem to work

[Jeff Forcier]

That's an odd error there; haven't seen it with Fabric before. I also
note you're on 64-bit -- I don't know about Christian but I don't
think I've tested Fabric on 64-bit at all. For what the tool does, I
can't imagine it'd make a difference, but I've seen stranger things.

Anyway, let's assume that's a red herring for now. Can you email me
your fabfile and a transcript of your entire shell session (i.e. from
the moment you type in 'fab <whatever>' through the crash)? That
should help me figure out what's going on, and I'll try to replicate
it on this end.

Sorry for the trouble!

-Jeff

On Tue, Oct 14, 2008 at 5:20 PM,  <address@hidden> wrote:
> I did set fab_hosts; I still see the prompt for
>
> Please specify host or hosts to connect to (comma-separated):
>
> ...which causes a crash even when I enter my servername manually:
>
> Traceback (most recent call last):
>   File "build/bdist.linux-x86_64/egg/fabric.py", line 1334, in main
>   File "build/bdist.linux-x86_64/egg/fabric.py", line 1303, in
> _execute_commands
>   File "build/bdist.linux-x86_64/egg/fabric.py", line 1104, in _connect
>   File "build/bdist.linux-x86_64/egg/fabric.py", line 971, in connect
>   File "build/bdist.linux-x86_64/egg/fabric.py", line 1009, in _do_connect
> TypeError: connect() got an unexpected keyword argument 'timeout'
>
> ...since in my call of set() I also need to specify the fab_port number and
> fab_user, both of which are different from my current login and standard ssh
> port.  Any ideas?
>
>
>
> On Tue, Oct 14, 2008 at 3:11 PM, Jeff Forcier <address@hidden> wrote:
>>
>> That branch is pretty different from 0.0.9 (it doesn't have an actual
>> release number yet since it's unofficial work). The 'hosts to connect
>> to' bit is because of changes made to how it connects to systems. It
>> should only be showing up if you didn't set 'fab_hosts' (i.e.
>> set(fab_hosts=['www.mysite.com'])).
>>
>> Having an empty fab_hosts would also cause the split() error -- I
>> obviously didn't put in enough error checking for that particular
>> feature yet (The prompting for specific hosts when it doesn't find
>> any).
>>
>> So, make sure fab_hosts is set, or manually specify them at the
>> prompt, and it should hopefully behave a little better.
>>
>> -Jeff
>>
>> On Tue, Oct 14, 2008 at 2:59 PM,  <address@hidden> wrote:
>> > OK, now when I do sudo python setup.py install, I see a message that
>> > Fabric
>> > 0.0.8 is installed.  When I try running my "fab tail_production"
>> > command, I
>> > see a message I did not see before with 0.0.9:
>> >
>> > Running tail_production...
>> > Please specify host or hosts to connect to (comma-separated):  <didn't
>> > see
>> > this before, hit return>
>> > Traceback (most recent call last):
>> >   File "build/bdist.linux-x86_64/egg/fabric.py", line 1334, in main
>> >   File "build/bdist.linux-x86_64/egg/fabric.py", line 1302, in
>> > _execute_commands
>> >   File "build/bdist.linux-x86_64/egg/fabric.py", line 1065, in
>> > _check_fab_hosts
>> > AttributeError: 'NoneType' object has no attribute 'split'
>> >
>> > ...was there a syntax change between 0.0.8 and 0.0.9?  Do I need to
>> > update
>> > my local git checkout somehow?   Thanks.
>> >
>> >
>> >
>> >
>> > On Mon, Oct 13, 2008 at 4:10 PM, Jeff Forcier <address@hidden>
>> > wrote:
>> >>
>> >> On Mon, Oct 13, 2008 at 3:56 PM,  <address@hidden> wrote:
>> >> > Hi Jeff - thanks for the code/tip, I tried using the branch,
>> >> > installed
>> >> > it,
>> >> > and yet I'm still seeing the same problem: seems to hang, have to hit
>> >> > CTRL-C, then belatedly see a password prompt.
>> >>
>> >> Yea, this is because my main/master branch is the same as regular
>> >> Fabric -- you weren't actually using the alternate branch (see below).
>> >>
>> >> > Note that when I did,
>> >> >
>> >> > git checkout execution
>> >> >
>> >> > ...per your instructions, I get an error:
>> >> >
>> >> > error: pathspec 'execution' did not match any file(s) known to git.
>> >> > Did you forget to 'git add'?
>> >>
>> >> I'm terribly sorry, I gave you bad instructions! (Too used to working
>> >> on an already-set-up repository...). You needed to do 'git checkout
>> >> origin/execution' instead of just 'git checkout execution'. That
>> >> should work (it'll warn you about it not being a local branch but that
>> >> shouldn't matter).
>> >>
>> >> Or you can do what Christian just said in his latest email -- that's
>> >> how I get my local setup so that I have two "local" branches instead
>> >> of just one. Since you're not planning on actually changing the code,
>> >> however, doing 'checkout origin/execution' may be quicker :)
>> >>
>> >> -Jeff
>> >
>> >
>
>